--------------010407050709020404060004
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Hey Darren, I got this as a response directed to me instead of the list.
This might help you understand the behavior you're getting.
-Russell
-------- Original Message --------
Subject: Re: [Nagios-devel] Re:initial scheduling problem
Date: Wed, 17 Jul 2002 16:40:11 -0500
From: Bill Huff
To: Russell Scibetti
References:
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/ ... heck_delay
I will give a shot at making it short and sweet. For initial
scheduling nagios will add the check interval for all services and
come up with a 'total check time'. It then divides that number
by the total number of services to be checked to come up with
the inter_check_delay. Once it determines the average check time
it then figures out how many checks it has to do a second to test
all of them in that average time. This all works great, if your
services all have similar check intervals. 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.
I ran into this problem when I had a check that was going
once every 6 hours and the rest were all going once every 1 or
2 minutes. It caused then initial checks to be spaced out over
about 30 minutes instead of the 2 that I would have expected.
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.
Hopefully this will be helpful. Take a look at the documentation
that I reference above and if you have any other questions feel
free to ask and I will try and make myself more clear.
--
Bill
On Wed, Jul 17, 2002 at 05:04:14PM -0400, Russell Scibetti wrote:
> I have tried to recreate your problem, and I can't. I added a new host and
> service definition and checked the scheduled check time, and it was
> scheduled for 2 minutes later (not 1/2 hr later). I have a stupid
> question. Do you actually wait 1/2 hour to see when the check occurs or do
> you just see that it says 1/2 hour away? Maybe the clock settings are a
> problem. You've probably already checked that, but I'm just throwing out
> ideas. It doesn't seem to be a bug though. Your problem doesn't occur for
> me.
>
> Other places to look maybe:
> nagios.cfg: inter_check_delay_method (s), service_interleave_factor
> settings (s), interval length (60)
>
> One other stupid question: You are setting the check_interval in terms of
> minutes, assuming that your interval length in nagios.cfg is set to 60,
> right? I'm not trying to be insulting, just spitting out random ideas.
>
> Hope something here helped.
>
> -Russell Scibetti
>
> Darren Gamble wrote:
>
> Good day,
>
> Thanks for your reply.
>
> i would have to say your configuration has a lot to do with
> this. if you start
> your services fresh without saving your data you would see
> the initial times
> change, I would suspect.
>
>
> If we have no data for a host, than the initial times change. That's not a
> big deal for me.
>
> Using the standard config files that come with the nagios
> distribution, the save
> initial state is on,
> this mea
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: bhuff@colltech.com