Closed dallonby closed 7 months ago
This is a known issue caused by writing to static files twice. We fixed it in beta.3 that was just released. Please try the following steps to recover your node:
reth stage drop headers
and reth stage drop bodies
Describe the bug
Upon restarting reth following upgrading B1 to B2 I received the following error message:
Error: internal database error occurred: write operation CursorInsert failed for key "11fa02ba2c8a25eefadbf303304aa2c8c2b740bbb363189fd4f324a277be6eb4" in table "HeaderNumbers": key/data pair already exists (-30799)
Caused by: write operation CursorInsert failed for key "11fa02ba2c8a25eefadbf303304aa2c8c2b740bbb363189fd4f324a277be6eb4" in table "HeaderNumbers": key/data pair already exists (-30799)
Location: /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/task/poll.rs:255:39
Steps to reproduce
Started reth node
Node logs
Platform(s)
Linux (x86)
What version/commit are you on?
reth Version: 0.2.0-beta.2 Commit SHA: 10aeeb02f Build Timestamp: 2024-03-13T07:19:50.526437588Z Build Features: jemalloc Build Profile: release
What database version are you on?
Current database version: 2 Local database version: 2
What type of node are you running?
Full via --full flag
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
RUSTFLAGS="-C target-cpu=native" cargo build --profile maxperf --features jemalloc,asm-keccak
Code of Conduct