<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1"> <TITLE>Service time out immediately sets hard state?</TITLE> </HEAD> <BODY>  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 </BODY> </HTML>