-
Notifications
You must be signed in to change notification settings - Fork 870
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
Full sync gets stuck at sender recovery #7644
Labels
A-staged-sync
Related to staged sync (pipelines and stages)
C-bug
An unexpected or incorrect behavior
S-stale
This issue/PR is stale and will close with no further activity
Comments
Update: This seems to happen also at later stages. Again, a restart fixes the issue temporarily.
|
This issue is stale because it has been open for 21 days with no activity. |
This issue was closed because it has been inactive for 7 days since being marked as stale. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-staged-sync
Related to staged sync (pipelines and stages)
C-bug
An unexpected or incorrect behavior
S-stale
This issue/PR is stale and will close with no further activity
Describe the bug
When syncing a new
full
node, reth gets stuck at theSenderRecovery
stage witheta=unknown
. Restarting the node fixes the issue, and the sync continues.Steps to reproduce
Unknown
Node logs
Platform(s)
Linux (x86)
What version/commit are you on?
(using the official docker image)
reth Version: 0.2.0-beta.5
Commit SHA: 54f75cd
Build Timestamp: 2024-04-03T16:25:25.825621855Z
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?
Full via --full flag
What prune config do you use, if any?
None
If you've built Reth from source, provide the full command you used
Using the official docker image
Code of Conduct
The text was updated successfully, but these errors were encountered: