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.

Sign up for GitHub

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

Jump to bottom

"Unable to find beacon header at height..." appears when CL stopped for longer time #6891

Open

kamilchodola opened this issue Apr 2, 2024 · 0 comments

Assignees

Contributor

kamilchodola commented Apr 2, 2024

Steps to Reproduce
In order to replicate the behavior, please provide a detailed list of steps:

Sync mainnet node
When all synced, stop CL for longer time (1h)
Restart CL
When node restarted, "Unable to find beacon header at height X. This is unexpected, forcing a new beacon sync." appears at least once or more.

Desktop (please complete the following information):
Please provide the following information regarding your setup:

Operating System: Linux
Version: 1.26.0-rc
Installation Method: Sedge
Consensus Client: Lighthouse

Logs
export-8dc52f11ff67e49.csv

flcl42 self-assigned this

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