Public bug reported:
The new default check_load definition in /etc/nagios/nrpe.cfg is way too
low for real-life. It seems the command definition changed between
Ubuntu 16.04 and 18.04 to use a -r option, but I'm finding this simply
causes false alarms the moment a nagios client is configured to respond
to check_load with nrpe. I'm having to go back through all the 18.04
clients I monitor and manually override the default values with sane
values placed in nrpe_local.cfg instead.
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/nrpe.cfg:command[check_load]=/usr/lib/nagios/plugins/check_load
-w 15,10,5 -c 30,25,20
New version:
/etc/nagios/nrpe.cfg:command[check_load]=/usr/lib/nagios/plugins/check_load
-r -w .15,.10,.05 -c .30,.25,.20
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.
** Affects: nagios-nrpe (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825043
Title:
The new check_load settings are too low
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1825043/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
