SIGSEGV while syncing using official snapshot

[ssnickolay]

s=2025-01-10T03:01:19.871202345Z level=info target=reth_node_events::node message="Block added to canonical chain" number=22334849 hash=0x6f4452839465bf5c40caa7b3434f67b605a3ca8472d33a4d5fb49f326b020615 peers=18 txs=215 gas="37.77 Mgas" gas_throughput="9957.75 Ggas/second" full=21.0% base_fee=0.01gwei blobs=0 excess_blobs=0 elapsed=3.793µs
ts=2025-01-10T03:01:19.884423969Z level=info target=reth_node_events::node message="Canonical chain committed" number=22334849 hash=0x6f4452839465bf5c40caa7b3434f67b605a3ca8472d33a4d5fb49f326b020615 elapsed=875.829µs
ts=2025-01-10T03:01:20.28595519Z level=info target=reth_payload_builder::service message="New payload job created" id=0x035dad41ec1494b2 parent=0x6f4452839465bf5c40caa7b3434f67b605a3ca8472d33a4d5fb49f326b020615
error: reth interrupted by SIGSEGV, printing backtrace

./op-reth(+0x2130bd7)[0x635da9cf1bd7]
/lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x76f511990520]
./op-reth(+0x23f94e0)[0x635da9fba4e0]
./op-reth(+0x23f6aed)[0x635da9fb7aed]
./op-reth(+0x23fe743)[0x635da9fbf743]
./op-reth(+0xda8c12)[0x635da8969c12]
./op-reth(+0xd972a1)[0x635da89582a1]
./op-reth(+0x2379b36)[0x635da9f3ab36]
./op-reth(+0x2378b3b)[0x635da9f39b3b]
./op-reth(+0x25df78a)[0x635daa1a078a]
./op-reth(+0x25df4c5)[0x635daa1a04c5]
./op-reth(+0x25afe9b)[0x635daa170e9b]
/lib/x86_64-linux-gnu/libc.so.6(+0x94ac3)[0x76f5119e2ac3]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x44)[0x76f511a73a04]

note: we would appreciate a report at https://github.com/paradigmxyz/reth

Hey there! I tried 3 times to sync reth with different snapshots (at least different archive names);

The steps are simple:

1. Download official reth snapshot
2. Unzip
3. Run both nodes (using docker)

Reth works several hours and then falls with the same error; After restarting docker containers the node starts to build its own chain (empty blocks with not mainnet hashes). Any ideas?

[ssnickolay]

It seems related to https://github.com/paradigmxyz/reth/issues/9942

[Onaysat]

😎

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.