<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Hello list users. Maybe one of you can help me with this question. I defined a very simple check_http command as listed below:<o:p></o:p> <o:p> </o:p> define command{<o:p></o:p> command_name check_qa_http<o:p></o:p> command_line $USER1$/check_http -H $HOSTADDRESS$ -S<o:p></o:p> }<o:p></o:p> <o:p> </o:p> The matching entry in the services.cfg file is:<o:p></o:p> <o:p> </o:p> define service{<o:p></o:p> use generic-service<o:p></o:p> host_name qa.myhost.com<o:p></o:p> service_description HTTP<o:p></o:p> is_volatile 0<o:p></o:p> check_period 24x7<o:p></o:p> max_check_attempts 3<o:p></o:p> normal_check_interval 5<o:p></o:p> retry_check_interval 1<o:p></o:p> contact_groups admins<o:p></o:p> notification_interval 120<o:p></o:p> notification_period 24x7<o:p></o:p> notification_options w,u,c,r<o:p></o:p> check_command check_qa_http<o:p></o:p> }<o:p></o:p> <o:p> </o:p> And in the hosts.cfg file, the entry that defines qa.myhost.com is:<o:p></o:p> <o:p> </o:p> define host{<o:p></o:p> host_name qa.myhost.com<o:p></o:p> alias qa.myhost.com<o:p></o:p> address 172.x.x.x<o:p></o:p> check_command check-host-alive<o:p></o:p> max_check_attempts 10<o:p></o:p> notification_interval 120<o:p></o:p> notification_period 24x7<o:p></o:p> notification_options d,r<o:p></o:p> contact_groups admins<o:p></o:p> }<o:p></o:p> <o:p> </o:p> Now my problem. About 10 days ago we took this server that hosts qa.myhost.com offline to do some maintenance. I never told nagios to ignore the warnings or errors that the monitor for qa.myhost.com was throwing. After two days of showing that qa.myhost.com was “critical”, the server came back on line, but nagios still shows the monitor for qa.myhost.com as being “critical”. If I run the check_http command from the command line, it comes back fine. <o:p></o:p> <o:p> </o:p> [root@eqnymon01:/usr/local/nagios/libexec:93]$ ./check_http -H qa.myhost.com -S<o:p></o:p> HTTP OK HTTP/1.1 200 OK - 5160 bytes in 0.053 seconds |time=0.053020s;;;0.000000 size=5160B;;;0<o:p></o:p> <o:p> </o:p> So if this command comes back OK, why does nagios still read “critical”, and how can I reset nagios? Starting and stopping the nagios process didn’t do it. Can someone please help? Thanks.<o:p></o:p> <o:p> </o:p> Mike R<o:p></o:p> </div> </body> </html>