reth icon indicating copy to clipboard operation
reth copied to clipboard

Published 20 hours ago • verified publisher icon paradigmxyz

Cannot seem to sync reth

Open 0xcircuitbreaker opened this issue 6 months ago • 0 comments
trafficstars

Describe the bug

I have been attempting to sync reth as a archive node and in the early stages of either 2 or 3 it always seems ot fail with the error code 30418, I am unsure of what to do to get past this error, it seems to be a write operation issue but I have a dedicated drive just for reth. Could be the issue is that i am running this on windows? Should i move to WSL for the reth node?

2025-04-24T06:36:45.077900Z ERROR Stage encountered a fatal error: internal database error occurred: write operation CursorAppend failed for key "00000000943dfb14" in table TransactionSenders: the given key value is mismatched to the current cursor position (-30418) stage=SenderRecovery
2025-04-24T06:36:45.084130Z ERROR backfill sync failed err=internal database error occurred: write operation CursorAppend failed for key "00000000943dfb14" in table TransactionSenders: the given key value is mismatched to the current cursor position (-30418)
2025-04-24T06:36:45.084663Z ERROR Fatal error in consensus engine
2025-04-24T06:36:45.098825Z ERROR shutting down due to error
Error: Fatal error in consensus engine

Location:
    R:\reth\crates\node\builder\src\launch\engine.rs:341:43

Steps to reproduce

Steps I took to build and run reth

clone from github

checkout latest tag - 1.3.12

cargo build --release

then i run reth with the following command

.\target\release\reth.exe node `
  --datadir R:\chaindb_reth `
  --log.file.directory R:\chaindb_reth\logs `
  --chain mainnet `
  --port 30303 `
  --discovery.port 30303 `
  --http `
  --http.addr 127.0.0.1 `
  --http.port 8545 `
  --ws `
  --ws.addr 127.0.0.1 `
  --ws.port 8546 `
  --http.api eth,net,web3,debug,trace,txpool,rpc `
  --metrics 127.0.0.1:6060 `
  --authrpc.addr 127.0.0.1 `
  --authrpc.port 8551 `
  --authrpc.jwtsecret R:\reth_prysm\jwt.hex `
  --db.exclusive true

I have what are normally default ports assigned as i have other nodes operating and want to ensure i have all ports assigned properly so i visually have them set in the commands to make it easier to remember what port is being used by which node.

Node logs

2025-04-24T06:36:42.208217Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Sending batch for processing tx_range=2486149506..2486249506
2025-04-24T06:36:42.208367Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Appending recovered senders to the database tx_range=2486149506..2486249506
2025-04-24T06:36:42.491045Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Finished recovering senders batch tx_range=2486149506..2486249506
2025-04-24T06:36:42.491066Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Sending batch for processing tx_range=2486249506..2486349506
2025-04-24T06:36:42.491208Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Appending recovered senders to the database tx_range=2486249506..2486349506
2025-04-24T06:36:42.852931Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Finished recovering senders batch tx_range=2486249506..2486349506
2025-04-24T06:36:42.852951Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Sending batch for processing tx_range=2486349506..2486449506
2025-04-24T06:36:42.853099Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Appending recovered senders to the database tx_range=2486349506..2486449506
2025-04-24T06:36:43.192508Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Finished recovering senders batch tx_range=2486349506..2486449506
2025-04-24T06:36:43.192532Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Sending batch for processing tx_range=2486449506..2486549506
2025-04-24T06:36:43.192704Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Appending recovered senders to the database tx_range=2486449506..2486549506
2025-04-24T06:36:43.537411Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Finished recovering senders batch tx_range=2486449506..2486549506
2025-04-24T06:36:43.537432Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Sending batch for processing tx_range=2486549506..2486649506
2025-04-24T06:36:43.537595Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Appending recovered senders to the database tx_range=2486549506..2486649506
2025-04-24T06:36:43.808720Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Finished recovering senders batch tx_range=2486549506..2486649506
2025-04-24T06:36:43.808739Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Sending batch for processing tx_range=2486649506..2486749506
2025-04-24T06:36:43.808875Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Appending recovered senders to the database tx_range=2486649506..2486749506
2025-04-24T06:36:44.166125Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Finished recovering senders batch tx_range=2486649506..2486749506
2025-04-24T06:36:44.166144Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Sending batch for processing tx_range=2486749506..2486849506
2025-04-24T06:36:44.166262Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Appending recovered senders to the database tx_range=2486749506..2486849506
2025-04-24T06:36:44.428899Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Finished recovering senders batch tx_range=2486749506..2486849506
2025-04-24T06:36:44.428914Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Sending batch for processing tx_range=2486849506..2486949506
2025-04-24T06:36:44.429022Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Appending recovered senders to the database tx_range=2486849506..2486949506
2025-04-24T06:36:44.742955Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Finished recovering senders batch tx_range=2486849506..2486949506
2025-04-24T06:36:44.742977Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Sending batch for processing tx_range=2486949506..2487049506
2025-04-24T06:36:44.743089Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Appending recovered senders to the database tx_range=2486949506..2487049506
2025-04-24T06:36:44.972380Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Finished recovering senders batch tx_range=2486949506..2487049506
2025-04-24T06:36:44.972399Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Sending batch for processing tx_range=2487049506..2487149506
2025-04-24T06:36:44.972533Z DEBUG ChainOrchestrator::poll: sync::stages::sender_recovery: Appending recovered senders to the database tx_range=2487049506..2487149506
2025-04-24T06:36:45.082256Z ERROR ChainOrchestrator::poll: sync::pipeline: Stage encountered a fatal error: internal database error occurred: write operation CursorAppend failed for key "00000000943dfb14" in table TransactionSenders: the given key value is mismatched to the current cursor position (-30418) stage=SenderRecovery
2025-04-24T06:36:45.084245Z ERROR ChainOrchestrator::poll: reth_engine_tree::chain: backfill sync failed err=internal database error occurred: write operation CursorAppend failed for key "00000000943dfb14" in table TransactionSenders: the given key value is mismatched to the current cursor position (-30418)
2025-04-24T06:36:45.084427Z DEBUG reth::cli: Event: FatalError
2025-04-24T06:36:45.084722Z ERROR reth::cli: Fatal error in consensus engine
2025-04-24T06:36:45.099102Z ERROR reth::cli: shutting down due to error

Platform(s)

Windows (x86)

Container Type

Not running in a container

What version/commit are you on?

PS R:\reth> rustc --version rustc 1.86.0 (05f9846f8 2025-03-31) PS R:\reth> git branch

  • (HEAD detached at v1.3.12) main PS R:\reth> ./target/release/reth --version reth Version: 1.3.12 Commit SHA: 6f8e7258f4733279080e4bd8345ce50538a40d6e Build Timestamp: 2025-04-23T16:01:30.618895600Z Build Features: jemalloc Build Profile: release PS R:\reth>

What database version are you on?

./target/release/reth db version 2025-04-24T12:47:28.968087Z INFO Initialized tracing, debug log directory: C:\Users\Atlas\AppData\Local\reth\logs\mainnet Error: Datadir does not exist: "C:\Users\Atlas\AppData\Roaming\reth\mainnet"

Location: R:\reth\crates\cli\commands\src\db\mod.rs:76:9 PS R:\reth>

Which chain / network are you on?

ETH Mainnet

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

cargo build --release

Code of Conduct

  • [x] I agree to follow the Code of Conduct

0xcircuitbreaker avatar Apr 24 '25 12:04 0xcircuitbreaker