Reload question

[Subhendu Ghosh]

On Thu, 21 Jul 2005, Larry Naves wrote:

> I have read through the docs and am missing the answers I am looking for. I
> know that a RELOAD "Sends a SIGHUP to the Nagios process, causing it to
> flush its current configuration data, reread the configuration files, and
> start monitoring again". I have noticied that whenever I perform a reload
> all the host and service checks get rescheduled starting with host 1. Is
> this the case or am I missing something? I have both
> retain_state_information=1 and use_retained_program_state=1 and my
> scheduling queue shows that nagios started over with hosts 1XX - 9XX every
> time. Is there a way to maintiain the scheduling queue throughout program
> restarts? If not does any body have a work around? I just don't want to ever
> see a scenario where nagios always gets reloaded before the 9999 host is
> checked for a long period of time during busy days where my coworkers are
> changing and reloading nagios.
>
> Nagios 1.2 w/MySQL
> MySQL 3.23
> CentOS 3.4
>
> Thanks in advance,
>
> Larry Wayne Naves, Jr. "Jay"
> Systems Analyst
> Computer Sciences Corporation /
> Alabama Supercomputer Authority
>
>

reload does cause the scheuling queue to be re-initialized.  Nagios does 
not know if you have added or deleted services and hosts or just changed 
definitions.

you may want to create policies that Nagios will only be reloaded 
once/twice a day.

-- 
-sg


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
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