Nagios Support Forum

Got it.. THanks.. You can close the pose..

I have issues with nagios -> event handler call for the 3rd time doesnt happen before the service reacheds CRITICAL HARD state this is wat happents 1. event handler call with CRITICAL SOFT 1 - success but service is till doen 2. event handler call with CRITICAL SOFT 2 - call is success but app is do...

I was able to make the current attempt to 1 . when we delete the retention.dat and restart nagios,then the current attempt is reset ti 1 irrespective of plugin output.

Thanks for the help. you can close this thread.

Thanks tgriep and mcapra for your response.. I will try that volatile option and post the reply tomorrow. one more issue i noted is ,nagios result in too many defunct process.. Process started by nagios ------ us32860s4000d0a:/u/gls/middleware/tools/nagios/var> psg nagios gls 14718 4497 0 11:20 ? 00...

Let me explain the issue clearly : i have java service say xxx. THis service is monitored for every 2 minutes (normal_check_interval) .. Network is down for sometime due to some outage. after 4 tries (max_check_attempts = 4) ,the service reached the CRITICAL HARD state. so therafter this will be sen...

if the status of service is critical SOFT
-> if service attempt is maximum retry ,we try to stop and start the issue process and NOT nagios

main problem is : service check reaches critical hard state . current attempt reaches max_retry value. then state becomes 2. even after the java service becomes up after some network failure,subsequent validation doesnt happen since Service state is hard even after nagios restart. worker try to run ...

command.cfg ----------------- # 'check_http' command definition define command{ command_name check_http command_line $USER1$/check_http -I $HOSTADDRESS$ $ARG1$ } # 'check-host-alive' command definition define command{ command_name check-host-alive command_line $USER1$/check_ping -H $HOSTADDRESS$ -w ...

removed