Reload question
Larry Naves
lnaves at asc.edu
Fri Jul 22 15:10:18 CEST 2005
> -----Original Message-----
> From: Chris Wilson [mailto:chris at aidworld.org]
> Sent: Friday, July 22, 2005 3:54 AM
> To: Subhendu Ghosh
> Cc: Larry Naves; Nagios Users
> Subject: Re: [Nagios-users] Reload question
>
> Hi all,
>
> > > 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.
>
> > 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.
>
> It seems to me that it would be a good idea for Nagios to
> schedule service checks in order of oldest "last check"
> first, newest last. This would mean that if host 9999 hadn't
> been checked on the last nagios run, it would be checked
> quickly after a nagios restart.
>
> Even better, when adding new host definitions, they would be
> checked immediately, minimising the amount of time they spend
> in "pending"
> state. Very useful when testing new host definitions :-)
>
> Cheers, Chris.
> --
> (aidworld) chris wilson | chief engineer (chris at aidworld.org)
>
> --
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.323 / Virus Database: 267.9.2/54 - Release Date:
> 7/21/2005
>
>
I agree with Chris. I wish that at least the last host/service checked would
be stored somewhere (i.e. state retention) and the checks would take up
there when nagios was reloaded but an immediate check of new hosts and
services would also be nice.
For now I will just set a db field's bit to 1 when a change is made that
would require a reload and just check it through cron every X amount of time
resetting it to 0 when read. The only other way around this, that I can
think of, would be for me to keep up with the last host/service checked and
then after a reload perform a force schedule of the next XXX hosts. How bad
would this be on nagios? Would the force check of say 850 hosts (all
services w/ average of 4 services per host) be?
Larry Wayne Naves, Jr. "Jay"
Systems Analyst
Computer Sciences Corporation /
Alabama Supercomputer Authority
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.9.2/54 - Release Date: 7/21/2005
-------------------------------------------------------
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
More information about the Users
mailing list