<div dir="ltr">Hi, I have a local script to backup my Nagios-machine, which writes its status directly in nagios.cmd. This works fine, but after about 3 minutes after the OK it switches back to CRITICAL. The service is passive and the freshness_threshold is set to 26h. Why does it complain after 3 minutes? Cheers Klaus define service{ name backup-job ; The 'name' of this service template active_checks_enabled 0 ; Active service checks are enabled passive_checks_enabled 1 ; Passive service checks are enabled/accepted parallelize_check 1 ; Active service checks should be parallelized (disabling this can lead to major performance problems) obsess_over_service 1 ; We should obsess over this service (if necessary) check_freshness 1 ; Default is to NOT check service 'freshness' notifications_enabled 1 ; Service notifications are enabled freshness_threshold 93600 ;26h event_handler_enabled 1 ; Service event handler is enabled flap_detection_enabled 1 ; Flap detection is enabled failure_prediction_enabled 1 ; Failure prediction is enabled process_perf_data 1 ; Process performance data retain_status_information 1 ; Retain status information across program restarts retain_nonstatus_information 1 ; Retain non-status information across program restarts notification_interval 0 ; Only send notifications on status change by default. is_volatile 0 check_period 24x7 normal_check_interval 5 retry_check_interval 1 max_check_attempts 4 notification_period 24x7 notification_options w,u,c,r contact_groups admins register 0 & nbsp; ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE! } define service{ use backup-job host_name rcc-nagios service_description Backup Status check_command nagios-backup-failed check_freshness 1 max_check_attempts 1 active_checks_enabled 0 passive_checks_enabled 1 } -- First Official Internetdenier </div>