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
[shinken 2.4] pollers eating CPU doing nothing at all #1798
Comments
What kind of load is it ? Is it user/system CPU, or I/O wait ? I had problems under LXC where the master daemons processes, which should only fork a single child, forked so many children processes that it overloaded the underlying host. Is it a similar symptom ? |
It is CPU load and I said I had the same problem under VMWare virtual machines. Also, there are no such fork since I have 0 check configured as there is no host nor services configured. So, no, it's not the same symptom. |
same issue observed for us. Having a look at the source code, we've seen that all temporisation functions have been removed from the source code, so that the poller, when it has nothing to do, loop forever to get something to do. here is the code in diff mode.
|
So this is a nrpebooster issue ? |
I close as it's a booster nrpe module issue (I should never wrote this module, endless bug entropy source...) |
Hi,
I have a big problem with Shinken 2.4 eating CPU for nothing. I manage the configuration with Ansible, so I was able to do an brand new install from scratch, on Debian Jessie, with Shinken 2.4, in LXC containers with Kernel 4.3.3.
I had the same problem with Debian Jessie virtual machines under VMWare.
The problem is that all active pollers are eating 100%CPU, leading to a load of 15 on a 2cpu/4thread intel i3. But there is no host and no service at all in any realm. I was about to insert some host/service configuration but I saw that, and I think having programs eating CPU while they have nothing to do could be a bug.
May I submit you my full configuration & setup with shinken 2.4:
FR
,BE
andDE
, members of theAll
realm.Here is part of the architecture diagram:
Here are two realms, with 6 machines. There are still 1 machine missing for the third and last realm:
The idea here is to alway have a scheduler/poller doing his job for DE and BE realms, and having a Broker/Reactionner/Receiver and Master available on DE and BE, with BE as "preferred" master.
The other realm, missing on the diagram, is somewhat standalone: poller/scheduler dedicated to it, no spare, has it's own B/R/R if no one is available in DE or BE.
If i'm not clear, tell me, I'll do my best.
I submit you the full configuration:
The text was updated successfully, but these errors were encountered: