I am also finding that disabling a service does show that it's disabled in the
interface, but alas the checks are made. Plus the summary screens show a
giant "P", indicating Passive Checks? I have double checked what I did, and
this is 100% reproducable.
Once again, disabling notifications indefintely seems to work just fine. Acks
work just fine as well.
Help please!
--
-bk
Quoting Brandon Knitter :
> Nagios 1.0b5
>
> [sorry for the double listing, haven't figured out where to post bugs like
> this]
>
> I am trying to "Delay next service notification" throught he CGI interface
> and
> through an external submissing via the nagios.cmd named pipe. The logs are
> showing that indeed the command is coming in, yet I just keep getting
> notified.
>
> Anyone else seeing this? I am going to try 1.0b6, but the change logs don't
>
> indicate a fix for this.
>
> I have tried this on a service with a "1" interval, and figured maybe it was
>
> due to that being too small, so I tried with a "2" interval. The intervals
> were set for checks as well as notifications. My interval is the default 60
>
> seconds. My state did not change during the delay period, I left the service
>
> in a PROBLEM state for about 2-3 intervals before trying to delay. This is
> 100% reproducable. DISABLE works great!
>
> Anyone else able to reproduce this?
>
> Thanks,
>
> --
> -bk
>
>
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Nagios-devel mailing list
> Nagios-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/lis ... gios-devel
>
>
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: knitterb@blandsite.org