Re: [Nagios-devel] Initial Scheduling Problem explanation

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
Guest

Re: [Nagios-devel] Initial Scheduling Problem explanation

Post by Guest »

Good day,

Thanks for forwarding me this message, Russell, and thanks Bill, for taking
the time to help a user.

> Russell, I am surprised that someone hasn't answered this by now,
> so let me give it a shot. With a service_interleave_factor of
> 's', that means that Nagios will us its smart method to schedule
> 'initial' service checks. How it does this is pretty well
> documented here:


http://nagios.sourceforge.net/docs/1_0/ ... check_dela
y

That's how I have it set up, and I did certainly read that portion of the
document to make sure it wasn't my User Error (TM).

> However, if you do
> something like have one service that checks once every 2 hours,
> it totally blows the average and will cause Nagios to space out
> the initial service check schedule over a much wider time then
> it should. Do you have any checks that are being tested much
> less frequently then the rest? That could be causing what you
> are seeing.

That is not only the case, but I reported in my original message that it was
most likely the cause of the bug, as that's when I started to see the
problem.

> However, if you have 'retain_state_information' set to a 1 and
> you simply add 1 new service and the same thing happens, then I
> would say that that would be a bug, since Nagios shouldn't have
> to schedule all of the services initial checks, only the new
> one,
> so it should be almost immediate.

I do have retain_state_information set to '1', yes. Thus, all of the
existing services are polled fine after a restart (assuming they have been
polled at least once), it's only the initial check of new services that has
the problem. Hence the subject. =)

So it _is_ a bug, then. Could someone address it, please? =)

Additionally, if the issues are separate (which they may not be, I don't
know the internals of the program that well) could Nagios be changed to
initially schedule services properly if the state of all of the services IS
new?

I'd like to add some checks to Nagios to make sure certain daily reports are
completed properly, these would be run once a day and would compound this
problem. I'm holding off on that for now, obviously. =)

Thanks again for everyone's time,

============================
Darren Gamble
Planner, Regional Services
Shaw Cablesystems GP
630 - 3rd Avenue SW
Calgary, Alberta, Canada
T2P 4L4
(403) 781-4948






This post was automatically imported from historical nagios-devel mailing list archives
Original poster: Darren.Gamble@sjrb.ca
Locked