New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Failure to fall back to a previous file when ledger-state file fails to parse #483

Closed

erikd opened this issue Jan 15, 2021 · 0 comments

Contributor

erikd commented Jan 15, 2021 •

edited

Reproducing:

Fully sync the node to the current chain tip.
Stop the db-sync process
Corrupt the latest ledger-state file (eg echo blah > ledger-state/mainnet/19120862.lstate)
Restart the db-sync process

Restarting current fails with something like:

ErrorPolicyLocalNodeError
  ( ApplicationExceptionTrace
    ( FatalError
      { fatalErrorMessage = "DecoderErrorDeserialiseFailure \"Ledger state file\" (DeserialiseFailure 0 \"expected list len\")"
      }
    ))

~~I am pretty certain I tested this when I added support for ledger-state, so this looks like a regression.~~

I was pretty sure I tested this, but after debugging it a bit I am less sure.

The text was updated successfully, but these errors were encountered:

erikd closed this as completed in

0db9898

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment