-
Notifications
You must be signed in to change notification settings - Fork 40
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.
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
Solution for the busted snapshots #234
Comments
An error occurred while executing this command.
|
Use the latest commit? Make integration use the latest commit. |
@blxdyx yes, The tools are all the latest commit. |
Try use the latest snapshot to resync |
I can confirm this is working as expected. My node was stuck on block 29.9 million for quite some time from a scratch sync. I went back to block ~29.5 and sync'd from there as I had messed around with resetting headers a few times and some other things. Incase anyone needs this, here's a useful command to find the snapshot files above 29.5 million (can also pipe to exec rm {} \ to delete):
|
Description
The history data in the ./data/snapshots meet some error.
How to fix
Or just download the latest snapshot and use the latest commit resync(Spend more time).
Expected behaviour
After finish the steps, it will fix the busted snapshots.
The text was updated successfully, but these errors were encountered: