Lighthouse syncing stuck

Before filing a new topic, please provide the following information.

Core DAppNode Packages versions

  • bind.dnp.dappnode.eth: 0.2.6
  • core.dnp.dappnode.eth: 0.2.58
  • dappmanager.dnp.dappnode.eth: 0.2.53, branch: develop, commit: 45ec898e
  • https.dnp.dappnode.eth: 0.1.3
  • ipfs.dnp.dappnode.eth: 0.2.18
  • wifi.dnp.dappnode.eth: 0.2.8
  • wireguard.dnp.dappnode.eth: 0.1.1

System info

  • dockerComposeVersion: 1.25.5
  • dockerServerVersion: 20.10.6
  • dockerCliVersion: 20.10.6
  • os: debian
  • versionCodename: bullseye
  • architecture: amd64
  • kernel: 5.10.0-11-amd64
  • Disk usage: 21%

Hello,

My Lighthouse beacon node gets stuck at 94% sync. I tried Prysm, same thing. It gets stuck at block 4700012. I tried syncing from scratch and checkpoint fast sync too., same result. All packages are up to date.

Thank you

Log:

Oct 22 15:33:01.148 WARN Error whilst processing payload status error: Api { error: ServerMessage { code: -32601, message: “the method engine_newPayloadV1 does not exist/is not available” } }, service: exec
Oct 22 15:33:05.001 INFO Syncing est_time: --, distance: 269051 slots (5 weeks 2 days), peers: 81, service: slot_notifier
Oct 22 15:33:05.001 WARN Syncing deposit contract block cache est_blocks_remaining: initializing deposits, service: slot_notifier
Oct 22 15:33:05.001 ERRO Execution engine call failed error: ServerMessage { code: -32601, message: “the method engine_exchangeTransitionConfigurationV1 does not exist/is not available” }, service: exec
Oct 22 15:33:05.001 ERRO Unable to get transition config error: Api { error: ServerMessage { code: -32601, message: “the method engine_exchangeTransitionConfigurationV1 does not exist/is not available” } }, service: exec
Oct 22 15:33:05.001 ERRO Not ready for merge hint: try updating Lighthouse and/or the execution layer, info: Could not confirm the transition configuration with the execution endpoint: “EngineError(Api { error: ServerMessage { code: -32601, message: “the method engine_exchangeTransitionConfigurationV1 does not exist/is not available” } })”, service: slot_notifier
Oct 22 15:33:05.266 ERRO Execution engine call failed error: ServerMessage { code: -32601, message: “the method engine_newPayloadV1 does not exist/is not available” }, service: exec

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.