Howdy all,
We have 2 machines here with nagios installed.
The 1st stopped working (not probing services and machines) after the
upgrade from 2.11 to 2.12, however after changing the conf files so that
an unassigned contact was assigned to a group, It started working fine.
Considering that it was listed as a 'warning' in the log files I was
surprised to find that it had stopped probing. Just wondering if anyone
else had seen that before. (freeBSD 5.5)
The second server(FBSD 5.4) hasn't been resolved as yet. It doesn't
probe anything at all like the first server, however it doesn't have any
warnings come up or anything out of whack that I can see within the conf
files. I've recompiled everything on the box with no diff.
From the logs:
The logs don't say anything other than
[1213758202] Nagios 2.12 starting... (PID=77539)
[1213758202] LOG VERSION: 2.0
[1213758202] Finished daemonizing... (New PID=77540)
[1213758318] Caught SIGTERM, shutting down...
The sigterm saves any data (ie the next prob time which has already
passed) and then turns nagios into an unkillable zombie.
If anyone could give any advice or have any ideas, that would be muchly
appreciated.
TIA
cheers
cya
Andrew
--
Network Administrator / Manager
Webzone Internet
1st Floor (Oakley Street Entrance)
167 Grote Street
Adelaide SA, 5000
Phone 1300 303 932
Fax 08 8221 6204
Email [EMAIL PROTECTED]
[EMAIL PROTECTED]
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
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
