-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
index out of range at HexPatriciaHashed. unfoldBranchNode on Eth Mainnet Fresh sync #13716
Comments
can you start with --downloader.verify? |
@awskii you can run this on your machine and reproduce |
Getting what seems to be the same issue on a new eth node sync. I also tried with the --downloader.verify arg and it still produced the same problem. I also after experiencing this checked out v3.0.0-beta1@0b94461 and rebuilt. This resulted in the same outcome, I'm now wondering if I have to completely delete the 1TB of stuff that's been downloaded to make this work. Any other things to try?
|
Switch to latest “main” |
same behavior |
Then: But I would advise: re-sync. |
System information
Erigon version:
git_branch=main git_tag=v3.0.0-beta1-107-gc948a59 git_commit=c948a59ced202cd12d59c96e8293fc7e0c13490f
OS & Version: Linux
Commit hash: c948a59
Erigon Command (with flags/config):
Consensus Layer: Caplin (internal by default)
Chain/Network: Ethereum Mainnet
Expected behaviour
fresh sync should finish without issues
Actual behaviour
Steps to reproduce the behaviour
Run a fresh sync from scratch on eth mainnet
The text was updated successfully, but these errors were encountered: