Service time out immediately sets hard state?

[Andrew Laden]

Heya

Running Nagios 2.0b6.

I have a service check that runs fine most of the time, but occasionally
(about once a day)  the check takes too long to run, and hits the
Service check timeout limit.

It appears that hitting this limit is treated as an immediate hard
error, even though I have max_check_attempts for the service equal to 5.
I would prefer it to be a soft error, so that I can retry withouth
sending out notification et al. Is this possible?

 One item that may be affecting the issue is that the service was in a
hard warning state at the time. I believe that this should not make a
difference, as a service in a hard warning that gets a critical return
goes into a soft critical normally. I think this is just a special
property of the service check timeout trigger.

I don't want to increase the service check timeout limit, because I
don't want to affect the other 99% of the services that are fine.

Thanks
-Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20060711/d57617df/attachment.html>
-------------- next part --------------

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
-------------- next part --------------
_______________________________________________
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