-
Notifications
You must be signed in to change notification settings - Fork 839
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
Blocked threads after more than a month of uninterrupted uptime #4904
Comments
After upgrading to
|
Sorry I seem to have missed this ping, I don't have any node explorer, I have a minimally installed Linux with nothing aside the essentials to run a besu/nimbus combo, the besu logs are pretty uneventful, literally nothing but the Here's how the restart appears right after the force restart due to blocked thread and subsequent recovery:
|
Hopefully this also helps, after restarting the node can never sync back until both the EL and CL are fully restarted (again):
|
@ahamlat, I’m still unsure about the issue in the OP but the good news is the latest issues turned out the be a result of block storage device issues with the hosting company, as a soon as this was sorted out my node is back to 99% effectiveness, closing. |
Description
After more than a month or so of uninterrupted uptime, besu ran into a myriad of blocked threads causing sync to fall behind greatly and never catch up.
After a manual service restart (which took a long time to initialize the exisiting DB), everything is back to normal.
LOG OUTPUT
(the same message loops forever)
Versions (Add all that apply)
besu --version
]java -version
]cat /etc/*release
]uname -a
]vmware -v
]N/A
docker version
]N/A
N/A
Additional Information (Add any of the following or anything else that may be relevant)
The text was updated successfully, but these errors were encountered: