gnosischain/documentation

bug: Checkpoint sync url error causing fail to start beacon node

zengzengzenghuy opened this issue · 2 comments

zengzengzenghuy commented

What

When running beacon node, the following checkpoint sync urls return error, causing the beacon node failed to start.

Checkpoint sync url

  1. "https://checkpoint.gnosischain.com/": CRIT Failed to start beacon node reason: Checkpoint block at slot 8353568 is not aligned to epoch start. Please supply an aligned checkpoint with block.slot % 32 == 0
  2. "https://checkpoint.gnosis.gateway.fm/": CRIT Failed to start beacon node reason: Error fetching finalized block from remote: ServerMessage(ErrorMessage { code: 500, message: "not found", stacktraces: [] })
  3. "https://checkpoint-sync-gnosis.dappnode.io/": no error

Client:
Lighthouse v4.0.1

Refs

filoozom commented

The Gateway and DAppNode endpoints work for me, the Gnosis doesn't. I've reported this to DevOps, we're looking into it.

This issue might be a better fit for https://github.com/gnosischain/issues, as it's not really a documentation issue but a bug, what do you think?

zengzengzenghuy commented

yes I agree. Closing the issue here and moving discussion to gnosischain/issues#16. Thanks @filoozom