check_load gone crazy

Mike Chesnut mikec at aggregateknowledge.com
Wed Sep 8 21:03:06 CEST 2010


> What transport mechanism are you using to run check_load on the remote systems? It is not 'network aware' and so the check_load binary must be installed on each remote machine and run on that machine via some transport (check_nrpe, check_by_ssh, etc). It seems to me that you are not running it on the remote machines but are instead monitoring the load of your nagios machine multiple times. Can you show a couple example service{} and corresponding command{} definitions if you are unsure?

Wow, good catch.  With the standard disclaimers about inheriting this 
Nagios configuration aside, it was indeed using the local check_load (on 
the Nagios server) and trying to run it against every single host being 
monitored, which obviously isn't what I wanted.

I'm changing it to run check_load via check_nrpe now.  Thanks for the help!

Mike

------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:

Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Nagios-users mailing list
Nagios-users at 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





More information about the Users mailing list