Open mxmauro opened 4 months ago
@mxmauro Could tell the version or commit hash it happened at? Sounds like there are few issues:
34000000
has not reset fast catchup state properly.Hi @algorandskiy , the last commit I tested was c8407abca80f4682aac43a5ccc8cd524051f4f63
.
And I agree about a filure on fast catchup process does not reset the state properly.
Trying to setup a starting point close to some block I need, started a node catchup with a random block number:
goal node catchup 34000000#OYD7DMAWH3V3LDB66STPSIKIHPEQKCRJ6QSCRZR6L4CNYVSLFFTQ -d data
Got this, something I expected:
Cannot contact Algorand node: HTTP 408 Request Timeout: unable to start catchpoint service for requested catchpoint 34000000#OYD7DMAWH3V3LDB66STPSIKIHPEQKCRJ6QSCRZR6L4CNYVSLFFTQ: aborting catchup Start(): checkLedgerDownload(): catchpoint '34000000#OYD7DMAWH3V3LDB66STPSIKIHPEQKCRJ6QSCRZR6L4CNYVSLFFTQ' unavailable from peers: no ledger available for given round
So tried with a new round:
goal node catchup 33000000#OYD7DMAWH3V3LDB66STPSIKIHPEQKCRJ6QSCRZR6L4CNYVSLFFTQ -d data
First unexpected response because the catchup start failed.
So tried to abort:
goal node catchup --abort -d data
And
algod
crashed:Seems the call to cs.abortCtxFunc panic'ed because it is
nil
Your environment
Well, using Windows binaries but this is not related to the OS.
Expected behaviour
Despite the crash, I don't expected to have to abort a catchpoint that couldn't start.