On 2 Oct 2009, at 13:51, Kurt Bechstein wrote:
From: [email protected] [mailto:[email protected]
] On Behalf Of Ton Voon
Sent: Thursday, October 01, 2009 2:14 PM
To: Opsview Users
Subject: Re: [opsview-users] Exception not being applied
On 1 Oct 2009, at 17:55, Kurt Bechstein wrote:
They do look correct there. Any other place that I should look?
Look in the services.cfg file in /usr/local/nagios/etc/, or the
objects.cache file in /usr/local/nagios/var. You have to identify
the right stanza - search for the service name and the host. Does
this match what you would expect?
Yes, these files match as far as what should be happening. For
instance I have a host that will get some pretty high load averages
due to heavy i/o usage and high i/o waits so I’ve bumped the warning
level to 20 and critical to 30. In services.cfg I have:
define service {
host_name tsm2.bgsu.edu
service_description Check Loadavg
check_command check_nrpe!-H $HOSTADDRESS$ -c
check_load -a '-w 20,20,20 -c 30,30,30'
However, I just got a warning for a load avg of 10 which was the old
value. The objects.cache file also contained the proper numbers in
it as well, yet I continue to get warnings on the previous values.
We haven't exposed a UI piece for this, but you can query the runtime
database to find out the exact command that is run. It is in the
nagios_servicechecks table. Something like
SELECT check_command,output FROM nagios_servicechecks where
service_object_id={X} ORDER BY start_time DESC LIMIT 5;
where X is the number from nagios_objects where name1='tsm2.bgsu.edut'
and name2='Check Loadavg'
The other possibility is that nrpe.cfg on the remote end is hard coded
to use 10,10,10, rather than using $ARG1$ for its value. You can
probably find this out by running on the opsview server
check_nrpe -H $HOSTADDRESS$ -c check_load -a '-w 20,20,20 -c 30,30,30'
to see if this works properly.
Ton
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users
