Hi Eric, As you can see in the description, your service is configured to check for every 1 minutes... You can try to change normal_check_interval to 10 and retry_check_interval to 1. Nagios will check the service in every 10 minutes and if something fails, it will retry to check in every 1 minute.
Best regards Cts, 2008-10-18 tarihinde 21:13 -0600 saatinde, J. Eric Steidley yazdı: [...] > define service { > name critical-service > service_description Service Checks every 1 minute > is_volatile 1 ; True > max_check_attempts 3 > normal_check_interval 1 > retry_check_interval 1 > active_checks_enabled 1 ; True > passive_checks_enabled 1 ; True > check_period 24x7 > parallelize_check 0 ; False > obsess_over_service 0 ; False > check_freshness 0 ; False > freshness_threshold 361 > event_handler_enabled 1 ; True > low_flap_threshold 0 > high_flap_threshold 0 > flap_detection_enabled 1 ; True > process_perf_data 1 ; True > retain_status_information 1 ; True > retain_nonstatus_information 1 ; True > notification_interval 10 > notification_period 24x7 > notification_options c,r ; CRITICAL, Recovery > notifications_enabled 1 ; True > contact_groups cv-critical > register 0 ; False > } -- Gürkan Aslan Senior Developer Komturk Iletisim Ltd. Sti Phone: +90 212 275 88 99 ext 125 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ 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