Stopped Syncing at Block 17867060

[0xJchen]

Describe the bug

The execution client stop syncing.

RETH reports:

WARN consensus::engine: Invalid block error on new payload invalid_hash=0xce16ea7caceeb3bc8078574dce2d2e66c801d68571ed4736e35c2352ecbad5b6 invalid_number=17867060 error=Consensus(BodyStateRootDiff { got: 0x486a5dd4a78d9d2066f5df5d6f7647d01007c42f019d78a3a5ccc6729660c276, expected: 0xd7b64a3667e0dc87cc03a6a13afbcfa09fba7f66be2291a0157df2b5ae8b6a57 })

Steps to reproduce

Tried RETH with both version with SHA 40230e74f41685340b144ec2fcf2dd0bf3da0e14 (latest commit) and v0.1.0-alpha.4 (latest release).

Lighthouse version v4.3.0-dfcb336

Node logs

RETH reports:

2023-08-08T02:37:50.597197Z  INFO Unwinding{stage=Headers}: sync::pipeline: Stage unwound stage=Headers unwind_to=17867059 progress=17867059 done=true
2023-08-08T02:37:50.598447Z  WARN consensus::engine: Bad block detected in unwind invalid_hash=0x979894182bcd57c338f62b4e80b43c074caaa6372c77f682fa61a199289c7d58 invalid_number=17867207                        2023-08-08T02:37:50.598472Z  WARN consensus::engine: Bad block with hash hash=0x979894182bcd57c338f62b4e80b43c074caaa6372c77f682fa61a199289c7d58 header=Header { parent_hash: 0x2704581750c2735eaf283846151d5bdb47757a782bc926a714a31bdcffc877ab, ommers_hash: 0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347, beneficiary: 0x1f9090aae28b8a3dceadf281b0f12828e676c326, state_root: 0x749a5c210229aa9814bc8baa69f79c3c62db77ec2e9be5777ab7fe22c0201768, transactions_root: 0x56011454b36278151a40673406d55f640785379454dcee8143c08b912af01ff6, receipts_root: 0xc54b21aebcc407d7490e44effc78a3ec515e8f75209cf03e88e4c95d8bbe8c0a, withdrawals_root: Some(0x5591e8b9cdb831fbde105b42a45d1e16da73062397f8d7218fec1b49547228cd), logs_bloom: 0x49e188034d2802b0da4010a0a00102a042b012823c2124000019208cc6be0a26280981dc9080002840309fa881f009561a4584039ea62e410666c018003b2c0dc8c05ccb549189282c064e4a5128a930810701048064084114302c468a674142da61834a9282c10999d09162c8438c450112000118298da097088850600d340c080286d28e48190407680b18c2ba2182c10444018d816418442d034711940c28ce8729499aa1600a889250e310100c028c3c54c8c8302bd2203189a302090e315000000250121ca00a0378012e47b4c408450182522caa1c4922110e6065a040047068d80102048077c537a064859236842a11595f0809e62037b88100251c81, difficulty: 0x0000000000000000000000000000000000000000000000000000000000000000_U256, number: 17867207, gas_limit: 30000000, gas_used: 9663013, timestamp: 1691461463, mix_hash: 0x0ae36e9b464006aaaa14ab7470bee6bf41c093a20197026b56bc66618b0cb726, nonce: 0, base_fee_per_gas: Some(13203233095), blob_gas_used: None, excess_blob_gas: None, extra_data: Bytes(0x7273796e632d6275696c6465722e78797a) }

Lighthouse reports:

WARN Invalid parent chain                    last_peer: 16Uiu2HAm5aLeyBti84VxfATs7HEphHfBr4dt7whQE6M9vtEyhJM6, outcome: ParentExecutionPayloadInvalid { parent_root: 0x7c3caff37faece882c7701b70d5b7da94f18879327da04e2d0c0dfe174d6ae06 }, score_adjustment: Mid Tolerance Error, service: sync

CRIT Head execution payload is invalid       execution_block_hash: 0xa8059faac18ed339213f9bcbb2b85de58c526002ec1f490ca2b887fe2afcb7b3, msg: this scenario may be unrecoverable, service: slot_notifier


ERRO Error whist recomputing head            error: ForkChoiceError(ProtoArrayStringError("find_head failed: InvalidBestNode(InvalidBestNodeInfo { current_slot: Slot(7053067), start_root: 0xe8937868e73c7f75a33908bcb9ea0516d55b17cc5348c19a1fcbfc3a65b81a42, justified_checkpoint: Checkpoint { epoch: Epoch(220407), root: 0xe8937868e73c7f75a33908bcb9ea0516d55b17cc5348c19a1fcbfc3a65b81a42 }, finalized_checkpoint: Checkpoint { epoch: Epoch(220406), root: 0x1e2f6d8369428e232c3288948e634eaec3fc1f58e09e3f00b40ba93dce2af965 }, head_root: 0xe8937868e73c7f75a33908bcb9ea0516d55b17cc5348c19a1fcbfc3a65b81a42, head_justified_checkpoint: Checkpoint { epoch: Epoch(220406), root: 0x1e2f6d8369428e232c3288948e634eaec3fc1f58e09e3f00b40ba93dce2af965 }, head_finalized_checkpoint: Checkpoint { epoch: Epoch(220405), root: 0xd87d50999be5ec29e9d40da587e2a643768d89ce190c763eb62bc7c3ba1321e9 } })")), service: beacon 

Platform(s)

Linux (x86)

What version/commit are you on?

0.1.0-alpha.4

What database version are you on?

Current database version: 1

If you've built Reth from source, provide the full command you used

cargo install --locked --path bin/reth --bin reth

Code of Conduct

• I agree to follow the Code of Conduct

[moose-code]

+1 expereienced the same issue on same block. Stuck on 17867059.

Thanks for the quick fix

[hsyodyssey]

encountered the same issue. Fixed by remove all reth data and restart.