-
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
Fatal: Failed to register the Ethereum service: gap (#492149) in the chain between ancients and leveldb #22374
Comments
I am seeing the same error after a SIGSEGV crash on the previous run. The only difference is that I'm doing a full sync. Here is the log of the crash:
And here is the log I get whenever I try to run geth now:
I run geth using the following command:
My .ethereum directory is currently 15GB, but I could upload the whole thing somewhere if that makes it easier for you guys to debug this. |
@osizadmin can you provide some logs? Did you have a crash before the problem you describe? |
@TheEdgeOfRage the crash should be fixed in the recent release - but you will need to resync. Thanks for your log this was most helpful |
Hello there! We have something close to yours: Command: Version:
|
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have more relevant information or answers to our questions so that we can investigate further. |
Hey, Can someone help on the same issue? I am having the same error. I am running geth with --syncmode=full |
Same issue with geth version v.1.10.2
|
Should be fixed by @fjl upcoming ancients refactor, will reopen and close once that's merged |
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have more relevant information or answers to our questions so that we can investigate further. |
Bad Bot |
thanks @MariusVanDerWijden is there a way I can fix it right now by syncing from the error block I am seeing? Like I don't want to sync fully again. I may want to sync from the block I am seeing has error |
How can this be avoided? |
i have same issue. |
did anybody try to delete that corrupted .ldb file? |
This root cause of this issue should be fixed in Geth 1.10.4. Please try it. |
@fjl do we need to resync after upgrade? Is there a shorter way so don't have to resync since start. I tried starting the client again after upgrade and it gives me same error.
|
Yes, you need to resync to fix this issue. Sorry about that. But the sync should be pretty fast with v1.10.4. |
Got this issue after updating to 1.10.4 I'm running a validator, but it's okay cause I'm using Infura as backup. How do I resync geth? Delete the database and restart geth? |
The file explorer freezes when I try to select all files in the chaindata folder.
|
I ended up deleting the entire chaindata folder. I didn't want to do it before because I didn't if it had special permissions or not. Also, I wasn't using sudo geth removedb before. But using sudo didn't help anyway. |
Thanks for the response. All is working now. To correct something I said earlier, I originally said this happened after I upgraded to geth v1.10.4. This is incorrect. I only noticed the issue after I upgraded. Upon checking infura stats, my validator has been using infura since May 27th... while using the previous version of geth. I'm not gonna go into an in-depth analysis about what I think happened to my machine, because I don't think it's very useful to anyone (and parts of my analysis doens't really line up). But a week prior to May 27th, my internet went and I was troubleshooting why. (if it was my fault or my ISP fault). A chaindata file could've been corrupted while I was rebooting and moving the machine to diagnose the issue. Though this doesn't really make sense. Because internet was restored on May 22nd and my validator was running fine (with geth, not infura) from the 22nd to the 27th. But, at the end of the day, it doesn't matter to anyone what caused my issue. All that matters is that is is not an issue with geth v1.10.4 and that deleting the chaindata folder and letting geth resync is the solution. Thanks all and take care. |
This is happening with v1.10.4
to clarify: this is post upgrade to v1.10.4, not an empty ledger. |
Got this yet again after updating to geth 1.10.6 Fatal: Failed to register the Ethereum service: gap (#12793685) in the chain between ancients and leveldb |
Why is geth still filled with so many errors? can't finish syncing without 10 errors in the process |
Just got this after gracefully stopping and restarting the 1.10.8 |
I'm getting a similar error. Syncing to the mainnet on Rocketpool. eth1_1 | INFO [10-13|14:24:43.809] Maximum peer count ETH=50 LES=0 total=50 |
Same on 1.10.12-unstable-476fb565-20211105, but to be fair I probably shouldn't be using sshfs |
Still same issue after v.1.10.4. Right now we have 1.10.8 |
Still not fixed
|
Version v.1.10.19 problem still here, after 1 week of geth start and resync.
|
I'm getting this error: Verison 1.10.23-stable Happens pretty frequently when trying to sync geth. Happens when my USB fails, which is connecting my SSD to my machine, and I reconnect/reboot. |
Getting this on a Geth v1.10.23 after an unclean shutdown 🤬 |
hitting this also , v1.10.23 |
can confirm still happening with v.10.26 |
This could possibly be related to a bug in the 'freezer repair' procedure. For anyone encountering this issue, please let us know if your geth printed any of the following log messages:
|
While investigating #22374, I noticed that the Sync operation of the freezer does not take the table lock. It also doesn't call sync for all files if there is an error with one of them. I doubt this will fix anything, but didn't want to drop the fix on the floor either.
While investigating ethereum#22374, I noticed that the Sync operation of the freezer does not take the table lock. It also doesn't call sync for all files if there is an error with one of them. I doubt this will fix anything, but didn't want to drop the fix on the floor either. (cherry picked from commit 193f350)
While investigating ethereum#22374, I noticed that the Sync operation of the freezer does not take the table lock. It also doesn't call sync for all files if there is an error with one of them. I doubt this will fix anything, but didn't want to drop the fix on the floor either. (cherry picked from commit 193f350)
Fatal: Failed to register the Ethereum service: gap (#986975) in the chain between ancients and leveldb |
Fatal: Failed to register the Ethereum service: gap (#5436187) in the chain between ancients and leveldb release geth v1.10.26 stable Just restart my full geth node |
@edsonayllon the I don't understand what the bug report is. Other than printing an error and refusing to start, what do you expect geth to do?
|
While investigating ethereum#22374, I noticed that the Sync operation of the freezer does not take the table lock. It also doesn't call sync for all files if there is an error with one of them. I doubt this will fix anything, but didn't want to drop the fix on the floor either.
This issue has been stale for a long time now. We have new mechanisms to recover a gap between ancients and state now, so this should not happen anymore. If it still happens to you, please open a new issue. Thanks to everyone for commenting and sharing their logs with us! |
System information
Geth version: 1.9.25-e7872729
Error : Fatal: Failed to register the Ethereum service: gap (#492149) in the chain between ancients and leveldb
We have faced the above error while start the geth in fast syncmode.
The text was updated successfully, but these errors were encountered: