On Fri, 2010-11-19 at 11:20 -0500, Chris Beattie wrote:
This time I'm trying a nearly-stock nagios.cfg file. The one I've
been
using predates Nagios 3.0. Though it's been updated some, it doesn't
contain all the more-recent settings.
I was out of town for a bit.
This is still
On Tue, 2010-11-16 at 22:52 +0100, Andreas Ericsson wrote:
That one was in 3.2.2 too though. Could you try un-commenting the lines
mentioned there and see if that helps?
It looks like something weird is still happening after making that
change. I checked some more hosts and the retry_interval
On Tue, 2010-11-16 at 22:52 +0100, Andreas Ericsson wrote:
http://git.op5.org/git/?p=nagios.git;a=commitdiff;h=1149d275011d7c4d8631b44dbba30ebdb4d7e83f
That one was in 3.2.2 too though. Could you try un-commenting the lines
mentioned there and see if that helps? I won't revert that patch,
On 11/17/2010 03:55 PM, Chris Beattie wrote:
On Tue, 2010-11-16 at 22:52 +0100, Andreas Ericsson wrote:
http://git.op5.org/git/?p=nagios.git;a=commitdiff;h=1149d275011d7c4d8631b44dbba30ebdb4d7e83f
That one was in 3.2.2 too though. Could you try un-commenting the lines
mentioned there and
I noticed something curious. It looks like Nagios 3.2.3 is making
on-demand host checks faster than the retry_interval should allow. The
interval_length is set to 60 and the retry_interval is set to 1. Nagios
and the plugins were compiled from source on CentOS 5.5 x64.
I'm not sure if this
On 11/16/2010 09:59 PM, Chris Beattie wrote:
I noticed something curious. It looks like Nagios 3.2.3 is making
on-demand host checks faster than the retry_interval should allow. The
interval_length is set to 60 and the retry_interval is set to 1. Nagios
and the plugins were compiled from
