reth
reth copied to clipboard
Published
20 hours ago •
paradigmxyz
paradigmxyz
Interupted sync fails with "Failed to decompress: Frame requires too much memory for decoding"
Describe the bug
I've interrupted the sync with CTR+C at stage 3 . After the restart reth crashes when syncing.
Steps to reproduce
- Start reth
- Wait for Stage 3 SenderRecovery
- Interupt the node
- Try to start the node again
Node logs
2024-04-03T19:23:57.465276Z INFO Static File Producer finished targets=StaticFileTargets { he
aders: None, receipts: None, transactions: None } elapsed=11.2µs
2024-04-03T19:23:57.465275Z INFO Target block already reached checkpoint=19575708 target=Hash
(0x63119abf616589d9335341885f5c0df5ed467fb4615972a5655986337da6f151)
2024-04-03T19:23:57.465286Z INFO Preparing stage pipeline_stages=1/12 stage=Headers checkpoin
t=19575708 target=None
2024-04-03T19:23:57.465297Z INFO Executing stage pipeline_stages=1/12 stage=Headers checkpoin
t=19575708 target=None
2024-04-03T19:23:57.465373Z INFO Stage finished executing pipeline_stages=1/12 stage=Headers
checkpoint=19575708 target=None stage_progress=100.00%
2024-04-03T19:23:57.465422Z INFO Preparing stage pipeline_stages=2/12 stage=Bodies checkpoint
=19575708 target=19575708
2024-04-03T19:23:57.465430Z INFO Executing stage pipeline_stages=2/12 stage=Bodies checkpoint
=19575708 target=19575708
2024-04-03T19:23:57.465436Z INFO Stage finished executing pipeline_stages=2/12 stage=Bodies c
heckpoint=19575708 target=19575708 stage_progress=100.00%
2024-04-03T19:23:57.465440Z INFO Preparing stage pipeline_stages=3/12 stage=SenderRecovery ch
eckpoint=14005579 target=19575708
2024-04-03T19:23:57.465444Z INFO Executing stage pipeline_stages=3/12 stage=SenderRecovery ch
eckpoint=14005579 target=19575708
2024-04-03T19:23:57.465498Z INFO Recovering senders tx_range=1435028529..1440028634
2024-04-03T19:24:00.453645Z INFO Status connected_peers=0 freelist=8 stage=SenderRecovery che
ckpoint=14005579 target=19575708
thread '<unnamed>' panicked at crates/primitives/src/compression/mod.rs:58:17:
Failed to decompress: Frame requires too much memory for decoding
stack backtrace:
0: rust_begin_unwind
1: core::panicking::panic_fmt
2: reth_primitives::compression::ReusableDecompressor::decompress
3: <reth_primitives::transaction::TransactionSignedNoHash as reth_codecs::Compact>::from_co
mpact
4: <rayon_core::job::HeapJob<BODY> as rayon_core::job::Job>::execute
5: rayon_core::registry::WorkerThread::wait_until_cold
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Rayon: detected unexpected panic; aborting
fish: Job 1, 'RUST_LOG=info ./reth node \' terminated by signal --authrpc.jwtsecret /secrets/
j… ( --port 30306 \)
fish: Job --discovery.port 30305 \, ' --authrpc.port 8552 \' terminated by signal --datadir
/home/gorbak25/RETH/… (SIGABRT)
fish: Job Abort, '' terminated by signal ()
gorbak25@setup1 ~/RETH [SIGABRT]>
Platform(s)
Linux (x86)
What version/commit are you on?
reth Version: 0.2.0-beta.4 Commit SHA: c04dbe6 Build Timestamp: 2024-03-26T19:23:59.507124566Z Build Features: jemalloc Build Profile: maxperf
What database version are you on?
Current database version: 2 Local database version: 2
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
No response
Code of Conduct
- [X] I agree to follow the Code of Conduct
To be clear the node in question has more than 100 GB of free ram available.
This issue is stale because it has been open for 21 days with no activity.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This was the only mention of this issue I've seen. Feel free to reopen if it happens again
