You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Recently we've been seeing errors like this on Mainnet nodes, in this case libp2p-01 on linux-07.ih-eu-mda1.nimbus.mainnet:
{"lvl":"FAT","ts":"2024-03-11 11:20:37.394+00:00","msg":"Era summaries don't lead up to backfill, database or era files corrupt?","bid":"c78a68b6:8518954"}
A previous instance of this happening was with unstable-02 on linux-03.ih-eu-mda1.nimbus.mainnet:
{"lvl":"FAT","ts":"2024-03-08 08:11:18.637+00:00","msg":"Era summaries don't lead up to backfill, database or era files corrupt?","bid":"bd80c153:8503305"}
Which was purged and allowed to resync. The libp2p-01 was left in a broken state for debugging.
Additional context
The unstable-02 was running v24.2.2-3b4b1c-stateofus when issue was discovered(probably).
The libp2p-02 was running v24.2.2-1fef38-stateofus when issue was discovered.
No issues were identified by verifyEra command.
The text was updated successfully, but these errors were encountered:
Add support for using era file for the initial checkpoint block.
This should also avoid an error when the beacon node is restarted
before the backfill process has made any progress (#6059).
Add support for using era file for the initial checkpoint block.
This should also avoid an error when the beacon node is restarted
before the backfill process has made any progress (#6059).
Describe the bug
Recently we've been seeing errors like this on Mainnet nodes, in this case
libp2p-01
onlinux-07.ih-eu-mda1.nimbus.mainnet
:A previous instance of this happening was with
unstable-02
onlinux-03.ih-eu-mda1.nimbus.mainnet
:Which was purged and allowed to resync. The
libp2p-01
was left in a broken state for debugging.Additional context
The
unstable-02
was runningv24.2.2-3b4b1c-stateofus
when issue was discovered(probably).The
libp2p-02
was runningv24.2.2-1fef38-stateofus
when issue was discovered.No issues were identified by
verifyEra
command.The text was updated successfully, but these errors were encountered: