-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stuck at SenderRecovery #7858
Comments
a joyful has seemingly kicked it.. and allowed it to continue.. |
here are the logs right before things stopped progressing... fwiw 2024-04-24T20:01:08.442017Z DEBUG sync::stages::sender_recovery: Finished recovering senders batch tx_range=1333025538..1333125538 |
you can try to postpone pruning #7500 (comment). I would also turn of the rpc server for initial sync. @mrabino1 |
This issue is stale because it has been open for 21 days with no activity. |
did syncing work out for you in the end @mrabino1 ? |
y. i will close. looking forward this being out of beta ! |
Describe the bug
see logs below. seemingly stuck at SenderRecovery
Steps to reproduce
install beta.6 .. sync full from start.. wait
Node logs
Platform(s)
Linux (x86)
What version/commit are you on?
beta.6
What database version are you on?
beta.6
Which chain / network are you on?
mainnet
What type of node are you running?
Full via --full flag
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
The text was updated successfully, but these errors were encountered: