Skip to content
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

syncing stuck on sepolia after upgrading v1.13.11 #28899

Closed
windycrypto opened this issue Jan 31, 2024 · 9 comments
Closed

syncing stuck on sepolia after upgrading v1.13.11 #28899

windycrypto opened this issue Jan 31, 2024 · 9 comments

Comments

@windycrypto
Copy link
Contributor

beacon chain reports

beacon  | time="2024-01-31 05:52:17" level=warning msg="Execution client is not syncing" prefix=powchain
beacon  | time="2024-01-31 05:52:31" level=warning msg="Execution client is not syncing" prefix=powchain

while execution said:

geth  | INFO [01-31|05:43:07.007] Looking for peers                        peercount=2 tried=55 static=0
geth  | WARN [01-31|05:43:15.063] Beacon client online, but no consensus updates received in a while. Please fix your beacon client to follow the chain!

geth: v1.13.11
beacon prysm: v4.2.1

@rjl493456442
Copy link
Member

Beacon client online, but no consensus updates received in a while

Looks like there is no event sent from consensus client. Geth needs to be driven by these events for syncing.

@Brindrajsinh-Chauhan
Copy link

Seeing similar issue, the node is not moving ahead with the synchronization process
See these logs for a almost 24 hours. Finalized is moving up but not sure if it should take this long to start syncing back.

INFO [01-31|14:37:48.940] Forkchoice requested sync to new head    number=5,191,293 hash=578707..081dd7 finalized=5,191,207
INFO [01-31|14:38:00.524] Forkchoice requested sync to new head    number=5,191,294 hash=16ba39..6ca73a finalized=5,191,207

@windycrypto
Copy link
Contributor Author

Beacon client online, but no consensus updates received in a while

Looks like there is no event sent from consensus client. Geth needs to be driven by these events for syncing.

it's a bit confusing that beacon client also claims Execution client is not syncing, seems both are complaining the other one's problem

@ArturDolzan
Copy link

Same issue

@darinvhs
Copy link

darinvhs commented Feb 8, 2024

I'm encountering the same issue

  • Beacon: Nimbus - amd64-v24.2.0

@ivan-pohosov
Copy link

Some updates?

@rjl493456442
Copy link
Member

Restart the consensus client could probably help

@holiman
Copy link
Contributor

holiman commented Feb 22, 2024

Geth is at the mercy of the beacon client here. Not much EL can do without directions from CL, so we're going to have to blame them :)

@holiman holiman closed this as completed Feb 22, 2024
@lil0uuu
Copy link

lil0uuu commented Mar 27, 2024

I'm also encountering this issue. This keeps happening (daily) recently

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants