Service detail page refresh, stale checks
Tracy R Reed
treed at ultraviolet.org
Fri Jun 2 03:00:04 CEST 2006
Patrick Morris wrote:
> It does. Have you checked that there is only one copy of Nagios running?
>
Er...no, I hadn't thought of that.
sh-2.05b# ps -ef |grep -i nagios.cfg
nagios 26178 19728 0 00:28 pts/1 00:01:21
/usr/local/nagios/bin/nagios /usr/local/nagios/etc/nagios.cfg
nagios 5551 1 0 15:41 ? 00:00:08
/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios 2442 1 0 17:48 ? 00:00:00
/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios 2459 1 0 17:48 ? 00:00:00
/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios 2467 1 0 17:48 pts/1 00:00:00
/usr/local/nagios/bin/nagios /usr/local/nagios/etc/nagios.cfg
Does nagios normally spawn extra copies of itself? Some of these have a
ppid of 1 and another has a ppid of 19728. So I may have multiple copies
running. I just killed them all and restarted nagios. Does it not use
some sort of locking to try to avoid this?
> There are replacement GUIs, but I've never tried any of them. Recent
> browsers all seem to deal with "Reload" in a way that makes sense to me.
>
Ok, I won't worry about this if it turns out that I had multiple copies
running.
> Why does it claim to be failing? There should be an error message
> associated with the failure. How is your service configured? Are you
> sure it's passing the same command you're passing?
>
It says "Connection refused". In the service definition I have:
check_command check-cfengine
and in the checkcommands definition I have:
command_name check-cfengine
command_line $USER1$/check_tcp -H $HOSTADDRESS$ -p 5308
I let this run for a while:
while true; do ps -ef | grep -i check_tcp | grep -v grep; sleep 1; done
and it caught this:
nagios 8240 8239 0 18:08 ? 00:00:00 sh -c
/usr/local/nagios/libexec/check_tcp -H 192.168.0.1 -p 5308
nagios 9351 9350 0 18:11 ? 00:00:00
/usr/local/nagios/libexec/check_TCP -H 192.168.2.38 -p 5308
So it looks like it is running what I intended. If I do it manually from
the same machine nagios is running on:
sh-2.05b# ../libexec/check_tcp -H 192.168.1.36 -p 5308 TCP OK - 0.009
second response time on port
5308|time=0.008505s;0.000000;0.000000;0.000000;10.000000
--
Tracy R Reed http://ultraviolet.org
A: Because we read from top to bottom, left to right
Q: Why should I start my reply below the quoted text
_______________________________________________
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