Hard en soft states: problem, maybe bug.

[Johan Braeken]

On Thursday 14 July 2005 12:28, Chris Wilson wrote:
> Hi Johan,
>
> I have seen the same thing happen sometimes. Do you use passive service
> checks by any chance? I reported it as a problem with avail.cgi a few
> weeks ago, but I guess it's really an internal Nagios state change bug,
> not avail.cgi.

No, I'm not using passive checks.
It happened with the standard ping plugin.

> Restarting Nagios should return the service to a hard state, not a good
> workaround, but better than nothing :-)

Unfortunately it didn't.
I temporarily changed the plugin parameters so I got a hard warning.
After changing back and a hard OK was received, everything was like it should 
again.


Cheers,

Johan.

>
> Cheers, Chris.
>
> On Thu, 2005-07-14 at 10:12, Johan Braeken wrote:
> > Hello all,
> >
> > I have the following problem, which might be a bug in the handling of
> > states. I don't know if this is already known as I'm quite new to
> > Nagios...
> >
> >
> > I had a service (ping) which went through the following states:
> >
> > Warning: Hard state
> > Critical: Soft state
> > OK: Soft state
> >
> > Although this service displays as OK in de service detail, all my
> > availability reports keep saying it is still in "warning" state.
> > So, it looks like the hard warning state wasn't "undone".
> >
> > How can I solve this?
> >
> >
> > Cheers,

-- 
Johan Braeken
http://www.knudde.be


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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