Problem with Host Clusters

Harper Mann hmann at itgroundwork.com
Tue Sep 21 18:25:37 CEST 2004


Double check that all the nagios processes stop on a stop.  If a straggler
remains, you need to kill it.  

 

It's generally best to start and restart nagios with "/etc/init.d/nagios
stop/start" or "service nagios start/stop".  This is set up for the proper
ownership and verifies nagios will start on a reboot (if chkconfig is on.).

 

Regards,

 

- Harper

 

Harper Mann

Groundwork Open Source Solutions

510-599-2075 (cell)

 

  _____  

From: nagios-users-admin at lists.sourceforge.net
[mailto:nagios-users-admin at lists.sourceforge.net] On Behalf Of Joel Dunifon
Sent: Tuesday, September 21, 2004 6:55 AM
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] Problem with Host Clusters

 

    I'm having an intermittent problem with the host-clusters functionality
in nagios 1.2.  I have about 24 hosts in a cluster, and everything works
great, with one occasional exception.  It seems as though every once and
awhile when I add or remove an entry to the group, I'll start getting the
following:

 

 (Return code of 139 is out of bounds)  

 

    The individual host that I've added returns an 'ok' status and
everything looks fine, so I'm assuming this is some sort of config / status
file read error or something.  I've never been able to resolve this problem
without reloading nagios.  The last time was after I removed an entry, this
time I added an entry.  Re-adding the entry in the prior situation and
removing the entry this time do not resolve the problem.  I also tried
removing the entry, stopping nagios, deleting
/usr/local/nagios/var/status.sav, and restarting nagios (to clear all host /
service states and give the host-cluster a fresh log to look at).  This
doesn't seem to work either.

 

    I can't seem to think of anything else to try.  Anyone have any ideas?

 

Thank you,

 

Joel Dunifon

Network Specialist

WatchTV / WatchNet

1-800-589-3837

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20040921/8e9e7ed2/attachment.html>


More information about the Users mailing list