<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> thanks, i was looking for this in services.cfg instead of nagios.cfg Would be nice if you could disable this per service instead of acrossed the board like this, but this will do. Thanks again. define service{ name master-template active_checks_enabled 1 passive_checks_enabled 1 parallelize_check 1 check_freshness 0 obsess_over_service 0 notifications_enabled 1 event_handler_enabled 1 process_perf_data 1 retain_status_information 1 retain_nonstatus_information 1 is_volatile 0 normal_check_interval 5 retry_check_interval 1 max_check_attempts 3 flap_detection_enabled 0 check_period 24x7 notification_period 24x7 notification_interval 15 notification_options w,c,r register 0 } carole verdon wrote: <blockquote cite="mid40C06890.8020900@cict.fr" type="cite"> <title></title> It's because the <a href="http://lerins.cict.fr/nagios/docs/configmain.html#check_service_freshness">check_service_freshness</a><a> option is set to 1. </a> You have more information on : <a class="moz-txt-link-freetext" href="http://nagios.sourceforge.net/docs/1_0/freshness.html">http://nagios.sourceforge.net/docs/1_0/freshness.html</a> What Happens When A Service Check Result Becomes "Stale" If the check results of a service are found to be "stale" (as described above), Nagios will force an active check of the service by executing the command specified by the check_command option in the service definition. It is important to note that an active service check which is being forced because the service was detected as being "stale" gets executed even if active service checks are disabled on a program-wide or service-specific basis. Carole. Spencer Horn wrote: <blockquote type="cite" cite="mid40C058EA.1000004@lssi.net">This is happening every night at midnight. What causes a check to go stale? this monitor is set to check and notify only between 10am and 11:30am clearly midnight is outside of this time frame. the check seems to go stale at midnight forcing a check, forcing a false alarm, any ideas? [1086321944] Warning: The results of service 'NDAFeed_Build_Monitor' on host 'bldr' are stale by 59 seconds (threshold=360 seconds). I'm forcing an immediate check of the service. [1086321949] SERVICE ALERT: bldr;NDAFeed_Build_Monitor;CRITICAL;SOFT;1;NDAFeed Build Monitor Status (Fri Jun 4 00:05:46 2004 bldr /lssi/bin/nda/ndabuild_monitor.pl) NDAFeed Build logfile (/log/buildnda.pl.log) is old [1086322004] Warning: The results of service 'NDAFeed_Release_Monitor' on host 'bldr' are stale by 58 seconds (threshold=360 seconds). I'm forcing an immediate check of the service. [1086322008] SERVICE ALERT: bldr;NDAFeed_Release_Monitor;CRITICAL;SOFT;1;NDAFeed Release Monitor Status (Fri Jun 4 00:06:45 2004 bldr /lssi/bin/nda/ndarelease_monitor.pl) The files for these customers have NOT been released: Excell BTS Logic Ameritech Bell South Metro One Nortel ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. <blockquote type="cite">From Windows to Linux, servers to mobile, InstallShield X is the one </blockquote> installation-authoring solution that does it all. Learn more and evaluate today! <a class="moz-txt-link-freetext" href="http://www.installshield.com/Dev2Dev/0504">http://www.installshield.com/Dev2Dev/0504</a> _______________________________________________ Nagios-users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </blockquote> </blockquote> </body> </html>