RE: Nagios Updated a host but old host is still pinged

> From: "Gilbert T. Gutierrez, Jr." <plug@phxinternet.net>
> To: <plug-discuss@lists.plug.phoenix.az.us>
> Subject: RE: Nagios Updated a host but old host is still pinged
> Date: Fri, 27 May 2005 16:21:04 -0700
> Reply-To: plug-discuss@lists.plug.phoenix.az.us
>
> When you stop the service, and you run a process status (ps) with the
> appropriate options to display all running processes, do you see any nagios
> processes? I have had a problem in the past when running nagios on a
> FreeBSD box that sometimes not all copies of the program were killed when I
> stopped it. This caused me the same type of issue that you are describing
> now.
>
> Gilbert


After editing the configuration files and while Nagios is still running,
you can verify the configuration files by running:

nagios -v nagios.cfg

(using full paths to nagios and your config file if necessary)

Then you can fix up any config errors while Nagios is still running.

then you can reload Nagios's configuration by sending Nagios a sigup...
We just use the init.d startup script as such:

/etc/rc.d/init.d/nagios reload

This has several benefits - one, Nagios never really is restarted - so
it will still be working while you are working on your config files -
if you make an error, get distracted and go away, you'll still have
Nagios running and checking pre-existing hosts/services - two, every
start/stop puts entries in the log files that it was restarted -
if you make enough changes (like we do) you'll end up putting lots of
noise in the log files, and three - you don't have to worry about
running ps to see if the old copy has stopped before starting Nagios
up again.

:-)

Darin





---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss