-
Notifications
You must be signed in to change notification settings - Fork 897
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
22.10.0-RC2 got "stuck" during snap sync #4553
Comments
Once it got through snap sync after restart, it's quite unhappy:
|
Starting over, this time with debug logs |
I strongly suspect this is a bonsai consistency issue and will be resolved by using bonsai snapshots #4531 |
The good news is I can reproduce this. I'll get you (extensive 😅 ) debug logs. Do you expect 4531 to help with a sync that has stalled, or is that "fresh sync only" territory? |
Closing this, as bonsai snapshots may have solved it. |
Description
22.10.0-RC2 stopped importing blocks. Logs seen on 10-24 09:00:
And nothing after. CPU looked "idle" at that time. That is 11 hours of no progress.
After restarting Besu, it resumed:
I don't have debug logs, unfortunately. This issue is meant to just note that Besu can stall during sync.
Sync is on a dedicated server, 6 cores, 32 GiB RAM, Samsung PM9A3 NVMe SSD, Debian 11 OS and docker-ce.
The text was updated successfully, but these errors were encountered: