-
Notifications
You must be signed in to change notification settings - Fork 20.4k
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
invalid merkle root issues persists even after reboot #23863
Comments
Did you node crash before? Were you still generating the snapshot? Answering my question above, seems you indeed were still generating the snapshot and did crash. So, my guess is that the snapshot is fried. We did fix an issue in the last release 2 weeks ago, unsure if you were running with that or an older version when the problem happened. Either way, what you can try to do is "nuke" Geth's snapshot acceleration structure and have Geth regenerate it (will be fast-ish until it reaches the current progress). To do that, you should stop Geth and run |
wow, this all issue instills so much hope and faith into ethereum, the developers here clearly know exactly what they're doing and this is definitely not a half-baked project by a bunch of people who are constantly breaking core features by just gaze alone like some sort of techno-medusa whose mere proximity guarantees catastrophic failure. |
I'm getting a similar issue here on 1.10.15 (it actually started on 1.10.14). I have tried to
On start, the node does report some old unclean shutdowns, but the nearest one was 4 weeks ago... Any idea how to fix it without removing the whole db? |
It's a bit hard to guess what could have happened back then. We did fix an extremely unlikely snapshot corruption case that could happen during initial sync, but I doubt you were hitting this. Either way, there's not much information to go on now, so gonna close this, but would be interesting if this appears again with a node snap synced with a fresher version of Geth. |
I've been running on mainnet for several weeks and all of a sudden I get this issue with invalid merkle root. I'm really hosed with my Geth client and need some help. I saw this prior post (#23531) and rebooted to see if it helps. Nada!
System information
Your Smartnode is currently using the Ethereum Mainnet.
Rocket Pool client version: 1.0.0-pre4
Rocket Pool service version: 1.0.0-pre4
Selected Eth 1.0 client: Geth (ethereum/client-go:v1.10.11)
Selected Eth 2.0 client: Prysm (prysmaticlabs/prysm-beacon-chain:HEAD-a80b1c-debug)
Geth version: 1.10.11
OS & Version: Ubuntu 20.04
Steps to reproduce the behaviour
Run Geth 1.10.11
Logs
The text was updated successfully, but these errors were encountered: