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
{{ message }}
This repository has been archived by the owner on Feb 6, 2025. It is now read-only.
Node 1
�[2m2025-01-12T19:09:57.393095Z�[0m �[32m INFO�[0m Executing stage
�[3mpipeline_stages�[0m�[2m=�[0m2/12 �[3mstage�[0m�[2m=�[0mBodies �[3mcheckpoint�[0m�[2m=�[0m39575998 �[3mtarget�[0m�[2m=�[0m47327677
�[2m2025-01-12T19:09:57.395685Z�[0m �[31mERROR�[0m Fatal error in consensus engine
�[2m2025-01-12T19:09:57.395604Z�[0m �[31mERROR�[0m Stage encountered a fatal error: database integrity error occurred: trying to append data to Sidecars as block #39575999 but expected block #40000000 �[3mstage�[0m�[2m=�[0mBodies
�[2m2025-01-12T19:09:57.395654Z�[0m �[31mERROR�[0m backfill sync failed �[3merr�[0m�[2m=�[0mdatabase integrity error occurred: trying to append data to Sidecars as block #39575999 but expected block #40000000
Location: /reth/crates/node/builder/src/launch/engine.rs:444:43
Node 2 (same sequence of logs but different block numbers)
�[2m2025-01-12T19:11:41.859669Z�[0m �[31mERROR�[0m Stage encountered a fatal error: database integrity error occurred: trying to append data to Sidecars as block #39575811 but expected block #43500000 �[3mstage�[0m�[2m=�[0mBodies
Platform(s)
Linux (x86)
What version/commit are you on?
v1.1.0
What database version are you on?
Whatever comes with v1.1.0, no modifications made
Which chain / network are you on?
bsc-testnet (chapel)
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
No response
Code of Conduct
I agree to follow the Code of Conduct
The text was updated successfully, but these errors were encountered:
Describe the bug
I attempted to sync two bsc-testnet nodes from scratch. After about a day of syncing, both nodes are now crashlooping due to fatal database errors.
Steps to reproduce
Run where --chain=bsc-testnet
Node logs
Platform(s)
Linux (x86)
What version/commit are you on?
v1.1.0
What database version are you on?
Whatever comes with v1.1.0, no modifications made
Which chain / network are you on?
bsc-testnet (chapel)
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: