Nagios Support Forum

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9D322.CEFDE5A9
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Greetings All,=20

I'm working through an upgrade from Nagios 1 to 3.0.6. I've had several
situations where I've scheduled downtime for a host *after* it was
already in Nagios as DOWN and when it comes up it alerted (even though
it was in scheduled downtime) or in my most recent case the host was up
but a bunch of the service checks I'd added went critical because they
use the NSClient++ agent which was not loaded yet. In this case after a
bunch of the service checks had alerted as CRITICAL, I put the host in
scheduled downtime (verified it by the web interface) and then I
installed the nsclient++ agent. After it was installed I told Nagios to
recheck all services on the host to validate the install and I got
alerts for the recoveries of the service checks. I posted for this
before on the users mailing list
(http://article.gmane.org/gmane.network. ... user/61750), thinking
there was a possible delay between the web ui and the engine when
scheduling downtime, but now I'm wondering if it's a problem with the
logic such that when a host or service is already in a down/critical
state upon recovery it does not check for scheduled downtime before
sending recovery alerts? Could this be, please advise.

Thanks for your help,=20

-greg



------_=_NextPart_001_01C9D322.CEFDE5A9
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable






Scheduled downtime not recognized after DOWN/CRITICAL =
state???




Greetings All,


I'm working through an upgrade from =
Nagios 1 to 3.0.6.  I've had several situations where I've =
scheduled downtime for a host *after* it was already in Nagios as DOWN =
and when it comes up it alerted (even though it was in scheduled =
downtime) or in my most recent case the host was up but a bunch of the =
service checks I'd added went critical because they use the NSClient++ =
agent which was not loaded yet.  In this case after a bunch of the =
service checks had alerted as CRITICAL, I put the host in scheduled =
downtime (verified it by the web interface) and then I installed the =
nsclient++ agent.  After it was installed I told Nagios to recheck =
all services on the host to validate the install and I got alerts for =
the recoveries of the service checks.  I posted for this before on =
the users mailing list (http://article.gmane.org/gmane.network. ... user/61750), thinking there was a =
possible delay between the web ui and the engine when scheduling =
downtime, but now I'm wondering if it's a problem with the logic such =
that when a host or service is already in a down/critical state upon =
recovery it does not check for scheduled downtime before sending =
recovery alerts?  Could this be, please advise.

Thanks for your help,


-greg





------_=_NextPart_001_01C9D322.CEFDE5A9--





This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]