I have Nagios 3.3.1, and current load trips critical on some machines all the time, however the load numbers do not look very high.
This is the service definition I use for all machines, and it works on about 3/4ths of them: define service{ use local-service host_name TEMPLATE-HOSTNAME service_description Current Load check_command check_by_ssh!22!/usr/local/nagios/libexec/check_load!5.0,4.0,3.0!10.0,6.0,4.0 notifications_enabled 1 max_check_attempts 3 check_interval 5 retry_interval 3 check_period 24x7 notification_interval 15 notification_period 24x7 notification_options w,c,r contact_groups admins register 1 } On remote machines, I install the nagios plugins tarball, but not the nagios tarball. As I say this works on 3/4 of the machines, and doesn't always fail on the machines it traditionally fails on. Example output to the front-end: Current Load Notifications for this service have been disabled CRITICAL 09-12-2012 09:57:03 4d 23h 42m 14s 3/3 CRITICAL - load average: 0.00, 0.01, 0.05 The /usr/local/nagios folder on the remote machines is chown -R nagios:nagios Other check_by_ssh plugins are working on the machines where this one is failing. It is a mystery. -- Wolf Halton This Apt Has Super Cow Powers - http://sourcefreedom.com Open-Source Software in Libraries - http://FOSS4Lib.org Advancing Libraries Together - http://LYRASIS.org Apache Open Office Developer wolfhal...@apache.org ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null