Dear list, as I manage a number of servers, which are quite remotely placed, via nrpe it often happens that one or the other service(s) of the watched servers will show errors due to network insuffency.
Examples: - "SSL Handshake not completed ..." - "No response after ... seconds ..." So this service will fall into the state SOFT 1 - But after the next query the service is OK again. So I get many warnings/criticals which are not real problems of the machines. My question: Is there a possibility to change the state of a service not at the first fault (SOFT 1) but after the second fault (SOFT 2) - because then it will more likely be a real problem ... Or is there a possibility that I can configure nagios in that way that there has to be a second fault query of the same service before the state fo the service will fall from OK into SOFT 1 - and the status will change? Any hints? ThanX, Martin ----------------------------------------------------------------- Dipl.-Ing. Martin Schichl SC&C Software, Communication & Consulting GmbH & Co KEG EDV - Internet - PR - Events Reininghausstr. 13, A-8020 Graz Tel. +43/(0)316/90 85 00, Fax +43/(0)316/90 85 00 -90 Mobil: +43/676/840 439 100 [EMAIL PROTECTED], http://scc.co.at PGP-Key: https://keyserver2.pgp.com/vkd/DownloadKey.event?keyid=0xFDE06BE3FC7D0DB A ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.f-secure.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Nagios-users mailing list Nagios-users@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
