-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Erigon stuck on shutdown #9119
Comments
I had the same problem on v2.55.1, but the developer replied that it was solved (hopelessly) and finally I was able to reach a normal shutdown using |
I had the same problem on v2.55.1 |
This seems to be another regression from #8661 that went unnoticed. |
battlmonstr
added a commit
that referenced
this issue
Jan 10, 2024
mh0lt
pushed a commit
that referenced
this issue
Jan 11, 2024
battlmonstr
added a commit
that referenced
this issue
Jan 11, 2024
yperbasis
added a commit
that referenced
this issue
Jan 11, 2024
racytech
pushed a commit
to racytech/erigon
that referenced
this issue
Jan 12, 2024
…ontech#9119) (erigontech#9195) The handler had race conditions in the candidates processing goroutine.
wmitsuda
added a commit
that referenced
this issue
Jan 19, 2024
commit 0c7300e Author: Willian Mitsuda <[email protected]> Date: Fri Jan 12 20:05:43 2024 -0300 Squashed work from ots2-alpha4 commit c9216ce Author: battlmonstr <[email protected]> Date: Thu Jan 11 17:13:46 2024 +0100 p2p/discv4: revert gotreply handler change from #8661 (#9119) (#9195) (#9210) Co-authored-by: yperbasis <[email protected]> commit d079008 Author: Andrew Ashikhmin <[email protected]> Date: Mon Jan 8 17:44:30 2024 +0100 release: Amoy bootnodes (#9166) Cherry pick #9158 --------- Co-authored-by: Arpit Temani <[email protected]> commit a49fcb8 Author: Andrew Ashikhmin <[email protected]> Date: Fri Jan 5 13:03:28 2024 +0100 release params: remove dev from version (#9143)
Should be fixed in v2.57.0 thanks to @battlmonstr. Please re-open if that's not the case. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following log is from e35 branch from a few days ago commit, but I've noticed something similar on releases branches (although not sure if it is the same scenario).
anyway, posting stack trace from what I found out since this one is short:
The text was updated successfully, but these errors were encountered: