Hi all,
giving 1.35.0 a try on mainnet on a development machine. getting “Invalid snapshot DiskSnapshot” then cardano-node hangs. ideas? was syncing and running fine for about 12hours, then this
Jun 28 09:09:26 dev1 cardano-node[776112]: [dev1:cardano.node.ChainDB:Info:15] [2022-06-27 21:09:26.86 UTC] Started opening Chain DB
Jun 28 09:09:26 dev1 cardano-node[776112]: [dev1:cardano.node.ChainDB:Info:15] [2022-06-27 21:09:26.86 UTC] Started opening Immutable DB
Jun 28 09:09:27 dev1 cardano-node[776112]: [dev1:cardano.node.ChainDB:Info:15] [2022-06-27 21:09:27.00 UTC] Validating chunk no. 2997 out of 2997. Progress: 99.97%
Jun 28 09:09:28 dev1 cardano-node[776112]: [dev1:cardano.node.ChainDB:Info:15] [2022-06-27 21:09:28.10 UTC] Validated chunk no. 2997 out of 2997. Progress: 100.00%
Jun 28 09:09:28 dev1 cardano-node[776112]: [dev1:cardano.node.ChainDB:Info:15] [2022-06-27 21:09:28.11 UTC] Found a valid last location at chunk 2997 with tip 6dde18909f3fa2b66b3ffb74e64ff587a2e6b651be807edeb5835e4891331950@64748421.
Jun 28 09:09:28 dev1 cardano-node[776112]: [dev1:cardano.node.ChainDB:Info:15] [2022-06-27 21:09:28.11 UTC] Opened imm db with immutable tip at 6dde18909f3fa2b66b3ffb74e64ff587a2e6b651be807edeb5835e4891331950 at slot 64748421 and chunk 2997
Jun 28 09:09:28 dev1 cardano-node[776112]: [dev1:cardano.node.ChainDB:Info:15] [2022-06-27 21:09:28.11 UTC] Started opening Volatile DB
Jun 28 09:09:35 dev1 cardano-node[776112]: [dev1:cardano.node.ChainDB:Info:15] [2022-06-27 21:09:35.17 UTC] Opened vol db
Jun 28 09:09:35 dev1 cardano-node[776112]: [dev1:cardano.node.ChainDB:Info:15] [2022-06-27 21:09:35.17 UTC] Started opening Ledger DB
Jun 28 09:10:23 dev1 cardano-node[776112]: [dev1:cardano.node.ChainDB:Error:15] [2022-06-27 21:10:23.37 UTC] Invalid snapshot DiskSnapshot {dsNumber = 64748421, dsSuffix = Nothing}InitFailureRead (ReadFailed (DeserialiseFailure 397070315 "end of input"))
Seems like the node just hangs though, as in it doesnt look like its talking to anything and just stops.
ive started a re-sync and will report back. Im wondering if its an issue with the replay of the ledger after 1.35.0 was run for the first time on an existing db
Make sure you copy the latest immutable and volatile databases from an up-to-date running 1.34.x node, otherwise the snapshot will probably be too new!
Had the same issue. The solution is wait. It will begin finishing the synch just like @jeremyisme says. I’m running an EVO 970, decent cpu with a pretty slow internet speed (50mbps on a good day) (I’m putting specs here to see if you’re getting some hardware effect increasing wait time
and it took maybe 3 minutes to get passed the error and continue synching.
Yes, got the same issue upon restarting node using version 1.35.7. After about 5 minute wait, the startup process continued. So, just waiting did the trick for me.
Here is the snippet from the logs after getting past the error.