Since upgrading from 2.0 to 2.7 nagios has continued to notify us of events even when the event has been acknowleged and when notification has been disabled. The contents of the status.dat for the service are:<br><br>service {
<br>        host_name=cbnel17b<br>        service_description=Disk - /tmp<br>        modified_attributes=1<br>        check_command=check_unix_disk!10%!5%!/tmp<br>        event_handler=<br>        has_been_checked=1<br>        should_be_scheduled=1
<br>        check_execution_time=0.793<br>        check_latency=70.262<br>        check_type=0<br>        current_state=2<br>        last_hard_state=2<br>        current_attempt=3<br>        max_attempts=3<br>        state_type=1
<br>        last_state_change=1172629279<br>        last_hard_state_change=1172629537<br>        last_time_ok=1172629147<br>        last_time_warning=0<br>        last_time_unknown=0<br>        last_time_critical=1172630731
<br>        plugin_output=DISK CRITICAL - free space: /tmp 54 MB (3%):<br>        performance_data=/tmp=54MB;1813;1914;0;2015<br>        last_check=1172630731<br>        next_check=1172630791<br>        current_notification_number=1
<br>        last_notification=1172629539<br>        next_notification=1172629839<br>        no_more_notifications=0<br>        notifications_enabled=0<br>        active_checks_enabled=1<br>        passive_checks_enabled=1
<br>        event_handler_enabled=1<br>        problem_has_been_acknowledged=1<br>        acknowledgement_type=2<br>        flap_detection_enabled=1<br>        failure_prediction_enabled=1<br>        process_performance_data=1
<br>        obsess_over_service=1<br>        last_update=1172630852<br>        is_flapping=0<br>        percent_state_change=5.07<br>        scheduled_downtime_depth=0<br>        }<br><br>Can anyone see why nagios would continue to send notifications given the above state information?
<br><br>Thanks,<br>  Andrew<br><br>