The new check_load settings are too low
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nagios-nrpe (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
The new default check_load definition in /etc/nagios/
I don't know if the -r option simply isn't working as expected, or if the default values now used are just too low. A newly-built 18.04 is running BitDefender that that alone is causing non-stop warnings and criticals from nagios now, because now it's warning at 15% of available CPU.
Old version:
/etc/nagios/
New version:
/etc/nagios/
You want a host to have its cpu load up to match the number of cores it has, so you'd want these up around 1, at minimum, for 100% busy, not 15% of busy. That's just silly.
Thank you for taking the time to report this bug and helping to make Ubuntu better.
It looks like this default originates from upstream's sample configuration here: https:/ /github. com/NagiosEnter prises/ nrpe/blob/ master/ sample- config/ nrpe.cfg. in#L299, and https:/ /github. com/NagiosEnter prises/ nrpe/issues/ 171 and https:/ /github. com/NagiosEnter prises/ nrpe/pull/ 205 references it. Will that fix your problem? If so, I suggest discussion upstream to try and get that pull request landed first.
Importance: Medium since a workaround is available (local override in /etc/nagios/ nrpe_local. cfg as described in the bug description).