-
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
Two bugs since Dencun (low peers + threads not finishing) #7094
Comments
correct - low peers issue is being tracked under issue #6805 . The second issue - a few questions
|
@RogerHKW We were actually tracking the second issue internally as well. |
Thanks to both of you. Consensus and validator: Teku. Memory usage: the amount of memory that Besu uses does not change, it is the same after reboot as during the exponential phase preceding the complete freeze. Garbage collector: is there a simple way to track it? I tried Besu log: I will share the part of the file that you need in several hours (tonight in my time zone). |
@RogerHKW We can get GC metrics from the GC logs, but we already collect GC metrics with Prometheus. Do you have Besu Full Grafana dashboard ? |
I apologize for the delay. I got pulled out of my beloved nerdy activities yesterday by some human being. So, I read your installation manual for Grafana. It seems that I need a screen on the validator to watch the charts. It's a machine without a screen, I access it with SSH only. A solution could consist in opening the port of Grafana but I am afraid that I would lower the security of the machine. By the way, I installed more than 36 hours ago the new version of Besu that you published 2 days ago and it is running smoothly so far. Regarding the log of Besu, here it is. I start this extract at 5:29, before the first error is thrown at 5:31:21.
|
Hi there - thanks for the feedback! Closing for now as of the latest release 24.5.1 fixes. We will continue to work on peering over the next few releases as well. |
Related fix : #7076 |
Dear Besu team,
Since Dencun, Besu suffers from 2 bugs on my setup.
The first problem is a quite low number of peers for the first ~24 hours after restarting (that is the time it takes to slowly reach my objective of 75 peers). It is even below 10 peers for 2/3 hours, which is not healthy.
I saw in another report that you are aware and are investigating.
The second problem is very different and I didn't see it reported. It also started when Dencun launched. Therefore, it might have the same root cause as the first one, or maybe one of them is the cause of the other? I hope this will help you.
So, the second problem is that every 36 hours or so, Besu throws errors in the log because "a thread took too long to run". These errors accumulate so the node starts to miss some attestations and the CPU usage grows exponentially, which ends up in a total freeze of the computer in less than 2 hours.
I restart the computer and the bug comes again about 36 hours later.
If it helps:
The text was updated successfully, but these errors were encountered: