thread tokio-runtime-worker panicked at failed to recover signer

[yorickdowne]

Describe the bug

Non-fatal, starting Reth alpha.7 fresh on Goerli, there's a thread panic, see log.

Panic does happen again on restart, this seems reproducible

Steps to reproduce

Start syncing Goerli fresh.

Node logs

eth-goerli-execution-1  | 2023-08-22T03:35:36.945638Z  INFO reth::cli: RPC HTTP server started url=0.0.0.0:8545
eth-goerli-execution-1  | 2023-08-22T03:35:36.945639Z  INFO reth::cli: RPC WS server started url=0.0.0.0:8546
eth-goerli-execution-1  | 2023-08-22T03:35:36.945647Z  INFO reth::cli: Starting consensus engine
eth-goerli-execution-1  | 2023-08-22T03:35:41.102554Z  INFO net: Session established remote_addr=34.124.144.176:36442 client_version=besu/v23.4.4/linux-x86_64/openjdk-java-17 peer_id=0xf72de3e203addd8e95c3ec71694681c952ebdd6035582304c87a5a479c3b0b7c8c56fac3fdae2efb7fc0fa4bc98cfe6b30f5061893fbd3a3d3e90a7f38223b10 total_active=1
eth-goerli-execution-1  | 2023-08-22T03:35:41.313771Z  INFO net: Session established remote_addr=3.110.106.145:30303 client_version=Nethermind/v1.19.2+42ba08b7/linux-x64/dotnet7.0.5 peer_id=0x312762150bb06ea1029a2020f3484089c4e285069062a372058151b40e1168df19bf2700b6d219dd07f46a60bbeec746e7be554dcb1141247fb528c0939291ea total_active=2
eth-goerli-execution-1  | 2023-08-22T03:35:59.077200Z  INFO net: Session established remote_addr=3.110.106.145:30303 client_version=Nethermind/v1.19.2+42ba08b7/linux-x64/dotnet7.0.5 peer_id=0x312762150bb06ea1029a2020f3484089c4e285069062a372058151b40e1168df19bf2700b6d219dd07f46a60bbeec746e7be554dcb1141247fb528c0939291ea total_active=2
eth-goerli-execution-1  | 2023-08-22T03:35:59.295512Z  INFO net: Session established remote_addr=64.71.153.55:30303 client_version=Geth/nomtestnetsentry1.cosmos.holdings/v1.11.6-stable-ea9e62ca/linux-amd64/go1.20.3 peer_id=0xd8c544ae819ce70b130d12d665859acf61e988336f399d1f3f07508fde64ce5d84d88a9cad36c39677907d76b0300940c1654cc20dca697eb01afd6f23be97ad total_active=3
eth-goerli-execution-1  | thread 'tokio-runtime-worker' panicked at 'failed to recover signer', crates/revm/revm-primitives/src/env.rs:81:39
eth-goerli-execution-1  | note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
eth-goerli-execution-1  | 2023-08-22T03:36:06.945344Z  INFO reth::cli: Status connected_peers=2 latest_block=0
eth-goerli-execution-1  | 2023-08-22T03:36:36.944581Z  INFO reth::cli: Status connected_peers=1 latest_block=0
eth-goerli-execution-1  | 2023-08-22T03:36:37.111625Z  INFO net: Session established remote_addr=64.71.153.55:30303 client_version=Geth/nomtestnetsentry1.cosmos.holdings/v1.11.6-stable-ea9e62ca/linux-amd64/go1.20.3 peer_id=0xd8c544ae819ce70b130d12d665859acf61e988336f399d1f3f07508fde64ce5d84d88a9cad36c39677907d76b0300940c1654cc20dca697eb01afd6f23be97ad total_active=2

Platform(s)

Linux (x86)

What version/commit are you on?

reth Version: 0.1.0-alpha.7 Commit SHA: 34b68de Build Timestamp: 2023-08-21T18:01:43.415617324Z Build Features: default,jemalloc Build Profile: maxperf

What database version are you on?

Current database version: 1
Local database is uninitialized

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

RUSTFLAGS='-C target-cpu=native' cargo build --profile maxperf --features jemalloc

Code of Conduct

• I agree to follow the Code of Conduct

[mattsse]

this looks like a goerli bug,
cc @Rjected looks clique related

[github-actions]

This issue is stale because it has been open for 21 days with no activity.

[Rjected]

Going to run a goerli node on the latest main now - will see if I run into this issue

[mattsse]

I believe we fixed this #6916