-
Notifications
You must be signed in to change notification settings - Fork 20.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
CRIT Failed to truncate extra state histories err=EOF #28105
Comments
The error seems to be with the |
Do you still have the corrupted database which can reproduce this issue? Or do you keep the ancient folder by any chance? |
My hunch is the state ancientstore is somehow corrupted by losing some data chunk, but it's really hard to say without enough debug information. I will try to expose more error messages and hopefully it can be reproduced. |
Sorry, I did not keep that. My node is now resyncing. But Im happy to do it again and tried to reproduce after synced. |
Would be nice to use this patch to reproduce, with a bit debug information, thank you! |
Please keep a bit logs before shutdown as well, easier to know what's the previous status. |
I ve reproduced this ,and will kept the broken db as you may need more infos @rjl493456442 |
Can you please e.g. |
The thing I have discovered via the log is: a) The index file is zero size after restart, which truncates the head data file respectively
b) The |
Yesterday I did a resync with "--state.scheme=path" and now my GETH won't start, with this error. What do I do?? |
@ryny24 can you share a bit more logs? You also reboot the machine without stopping geth? |
I did not reboot unless there was a power issue I'm not aware of, this machine is off-site, I only stopped GETH after the constant restart phone alerts woke up my wife lol. Here is the last of the log before it tries again.
|
Here is my state folder. I hope this is enough for now, I'm going back to bed.
|
Oh yes, it looks there was a power issue that caused GETH to shutdown unclean. Can I just delete the ancient only and just resync that? |
What's the OS you are using? |
Can you |
Debian GNU/Linux 11 (bullseye) |
The the parent folder of ancient/state would be chaindata, correct? There are 110,975 items in chaindata. I'll share a google doc instead of flooding this thread. Thank you. |
I tried to remove the ancient by doing "geth removedb" and selecting N for state, then Y. But I'm still getting the same error. |
I am sorry, I referred to |
Sorry, I removed everything and started a full sync. |
Could you please attempt to reproduce the issue once more using this specific branch: #28115? Based on the log you've provided, my suspicion is that the last item in the index file might be corrupted. Unfortunately, I'm unable to replicate it locally. I'm looking to gather more information, although I am not sure if it's available for you. |
Sure, I would like to resynced again and tried to reproduce the issue once more. No worries |
@SimonSMH1015 Can you repro it? |
Not yet. Trying reproduce it on goerli might be a little long. I shall test this again on Sepolia at the same time |
Hi all, Checked my system reboot logs, looks like my server rebooted 12 hours ago while asleep. Woke up to this error. Let me know if there is any troubleshooting I can do to help solve this issue. |
@rjl493456442 Also ran https://github.com/rjl493456442/go-ethereum/tree/add-freezer-errormsg branch. |
Thank you for the information. The thing can be confirmed is that the index file of freezer is corrupted:
I am not sure why it can happen, but leave the comment here for further investigation. |
@rjl493456442 is there any way to recover the database or is this a mandatory resync? Also if you need any further testing let me know and I can keep the node in this state. Just switched in Erigon in the meantime. |
I've got the same after a power outage. Resyncing now. |
Same issue here. |
Also getting the same error after moving to 1.13.4 (Pebble DB):
|
just to confirm, you also have the poweroff issue to unclean shutdown Geth right? What's the version you use before the poweroff? |
@rjl493456442 I hit the same error with a new synced node from scratch running v1.13.2 stable with:
It happened due to unclean shutdown of the node, without stopping I haven't done anything to the node and can give you full root access if you want to debug. Add your SSH keys to Github and I can send you SSH details if interested. |
i've just experienced the same thing on an unclean shutdown (server reset) on the latest stable. |
@nonsense Yes please, it will be helpful! |
Should be fixed by #28483(will make a release very soon), close it now. Feel free to reopen this issue or another new one in case it's not resolved. Appreciate for the reports from you guys. |
For some reason my machine suddenly turned off and geth won't start.
|
@rjl493456442 my ubuntu server rebooted again, same error on Upgraded to Now getting this error on trying to recover the old db.
Does Thanks for your help! |
1.13.5 can recover from some crashes, as long as the data is still there. But if the crash restarted with the 1.13.4 or older code, the data might have already been wiped, making recovery not possible unfortunately. |
@karalabe thank you for the quick reply! |
System information
Geth version:
geth 1.13.0
CL client & version: e.g. [email protected]
OS & Version: Linux
Expected behaviour
After looking the new feature provided by version 1.13.0, I updated my node. I leaved only the ancient blocks and restarted my geth with
--state.scheme=path
. It tookl me around 6 hour to resynced blocks and generated snapshot.To test the Semi-instant shutdowns, I forced shutdown my server without closing geth. Then I got the Error after I lauched the geth :-)
Now I have to synced form 0 as leave the ancient block data still leading to this problem.
The text was updated successfully, but these errors were encountered: