syncing stuck on sepolia after upgrading v1.13.11

ethereum / go-ethereum

Go implementation of the Ethereum protocol

https://geth.ethereum.org

GNU Lesser General Public License v3.0

47.28k stars 20.01k forks source link

syncing stuck on sepolia after upgrading v1.13.11 #28899

Closed cryptocifer closed 7 months ago

cryptocifer commented 8 months ago

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 commented 8 months ago

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 commented 8 months ago

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

cryptocifer commented 8 months ago

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