<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> Hi all,<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Sorry for the lengthy email but is it possible to force a service or a host into an OK state manually?<o:p></o:p> <o:p> </o:p> Basically what I have going on is, using the check_logfiles add-on I check several application logs for specific errors, however if an error is detected the service will go into a critical state and then on following check (if no errors are found) will issue an “OK” state. What I want is for Nagios to only issue a critical state and remain in this state. This will force someone to actually look at problem and not wait for it to automatically send a recovery alert. Once the log has been investigated, then the user should force the OK state. I’ve looked into the “Disable active checks of this service” as well as “Acknowledge this service problem” but I find that these 2 do not satisfy completely what I’m looking for.<o:p></o:p> <o:p> </o:p> Disable active checks of this service – This keeps the service in a critical state but the downside is that it can only be done manually (I need the service to remain critical from the initial check). Also, this stops notifications from going out.<o:p></o:p> Acknowledge this service problem – This also has to be done manually. Also, this does not keep the service in a critical state, upon the next service check; it will revert to an OK if no errors are found on the log since the last check).<o:p></o:p> <o:p> </o:p> </div> </body> </html>