-
Notifications
You must be signed in to change notification settings - Fork 20.5k
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
Restart Loss Data #25860
Comments
Can you post the logs after restart here? I think your node is recovering by re-insert the lost blocks and should be recovered |
@rjl493456442 |
Geth/v1.10.25-stable-69568c55/linux-amd64/go1.18.5 Same on my side, GETH dies, no crash error whatsoever, and when is restarted it goes back several days My main concern is geth dying... It happened to also on friday and it took 7hours to resync. Im running a extremely powerful machine. today seems to resync faster
|
Has just finished resynchronizing. It took 1hour more or less. When the resync has reached the point where geth crashed i got this logs:
|
@fernandezpaco |
Geth has to recover the lost block by re-importing them. And it can take some time depends on how many blocks have been lost. Close the ticket since everything is expected. |
Well geth crashing two times in four days is not as expected i guess... |
@fernandezpaco any crash is definitely unexpected. Would be appreciate you can open another ticket with the crash logs so that we can investigate a bit. |
@fernandezpaco I just upgraded to v1.11.5 and unfortunately did an unclean exit of geth, now when I run I got:
Which you got to, do I have to sync from scratch now :/ ? more log lines around it:
|
I am using geth v1.10.25 and teku/v22.9.0
I don't know why geth was killed, there is no exit error, when I try to restart the service, geth starts to synchronize from around 15564000, why is so much data lost? Does anyone have the same problem as me?
And the synchronization speed is very slow, the total memory of my machine is 984G, and the available 234G
The text was updated successfully, but these errors were encountered: