-
Notifications
You must be signed in to change notification settings - Fork 814
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
Besu v23.7.1 does not synchronize with goerli #5837
Comments
Hi there - thanks for the report. Can you provide logs from Teku as well? |
did you do a checkpoint sync with teku ? I see 8137 remaining blocks. if your CL is not close to the head the besu sync will not work because we need to have a recent pivot block |
Trying to reproduce this issue, I was able to sync Besu on Goerli with no issues with version 23.7.1. |
close due to CL problem --> try a fresh checkpoint sync with Teku and see if this is able to resolve the issue. |
Hey, Sorry I didn't see your messages. I think the problem came from the CL not being able to resync, but I haven't repeated the error since. When I upgraded Besu to |
Description
I wanted to sync Goerli network with Besu
v23.7.1
, unfortunately the sync blocked 3 times on the block0x928201
(9601537).Steps to Reproduce (Bug)
v23.7.1
Expected behavior: Node syncing well
Actual behavior: Sync blocked at height 9601537 without any error.
Frequency: Everytime with
v23.7.1
, tried with,X_CHECKPOINT
andX_SNAP
.Logs (if a bug)
We can see, Besu will download the pivot block 9601537 (
Downloading world state from peers for pivot block 9601537
).And the RPC is not synced, the RPC return the same block height:
Versions (Add all that apply)
v23.7.1
17.0.7
v23.6.1
Additional Information (Add any of the following or anything else that may be relevant)
I'd also like to point out that version
23.7.1
is marked as a release on Github. However in the Besu version23.7.1-dev-2bced4eb
. What is the truth?The text was updated successfully, but these errors were encountered: