-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stevens, Michael wrote: | Although the changelog for rc3 did not suggest that this host stuck in | downtime issue was going to be fixed, I went ahead and installed 3.0rc3. | Following the steps below still results in a host stuck in scheduled | downtime. | | Although you won't see the steps to create this problem every day, this | seems a fairly serious issue to me. Once the host gets 'stuck', email | is no longer sent about any problems Nagios sees for the effected host.
The order in which you did perform the test is: ~ 1. Host goes down ~ 2. Schedule variable down time ~ 3. Bring host back up Does this also occur if you do it the way it was intended? ~ 1. Schedule variable down time ~ 2. Bring host down ~ 3. Bring hust back up It is my perception that a scheduled downtime event is still waiting for the host to go down. After the host goes down you should just acknowledge the down host to stop notifications nd not use a scheduled down time because it obviously was not scheduled (from the perspective of Nagios). Hugo. - -- [EMAIL PROTECTED] http://hugo.vanderkooij.org/ PGP/GPG? Use: http://hugo.vanderkooij.org/0x58F19981.asc A: Yes. >Q: Are you sure? >>A: Because it reverses the logical flow of conversation. >>>Q: Why is top posting frowned upon? Bored? Click on http://spamornot.org/ and rate those images. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHxQAcBvzDRVjxmYERAp4xAJ0UlagUcBlrl7GNPKwx3A5KTFsvjgCePMGi csD7BrbUnRpwjVcGRLNbaks= =Jhv4 -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Nagios-users mailing list [email protected] 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
