<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <style>  </style> </head> <body lang="EN-US" link="blue" vlink="purple" style=""> <div class="WordSection1"> I have upgraded to Nagios Core 3.4.1 last week. There are a couple of issues I noticed. 1. notification for service check failures are being sent when the host is in downtime. 2. downtime are not being remove when it is expired. For issue #1, here is what I did to test. schedule downtime for host dsmgtbal800 and make service TEST_SERVICE critical to see if a notification will be sent. Here is the syslog entry for submitting the downtime. Jul 16 09:19:16 dsmgtbal800 nagios: EXTERNAL COMMAND: SCHEDULE_HOST_DOWNTIME;dsmgtbal800;1342444731;1342445451;1;0;7200;chung;testing notification Here is the hostdowntime entry in status.dat. hostdowntime { host_name=dsmgtbal800 downtime_id=13047 entry_time=1342444756 start_time=1342444731 end_time=1342445451 triggered_by=0 fixed=1 duration=720 is_in_effect=1 author=chung comment=testing notification } Here are the debug file entries with debug_level=32. [1342444913.262290] [032.0] [pid=721] ** Service Notification Attempt ** Host: 'dsmgtbal800', Service: 'TEST_SERVICE', Type: 0, Options: 0, Current Stat e: 2, Last Notification: Wed Dec 31 19:00:00 1969 [1342444913.262371] [032.0] [pid=721] Notification viability test passed. [1342444913.262378] [032.1] [pid=721] Current notification number: 1 (incremented) [1342444913.262384] [032.2] [pid=721] Creating list of contacts to be notified. [1342444913.262437] [032.1] [pid=721] Service notification will NOT be escalated. [1342444913.262451] [032.1] [pid=721] Adding normal contacts for service to notification list. [1342444913.262459] [032.2] [pid=721] ** Checking service notification viability for contact 'chung-email'... [1342444913.262474] [032.2] [pid=721] ** Service notification viability for contact 'chung-email' PASSED. [1342444913.262481] [032.2] [pid=721] Adding contact 'chung-email' to notification list. [1342444913.262526] [032.2] [pid=721] ** Notifying contact 'chung-email' For issue #2, the host downtime entry in status.dat is still there after the downtime expired. Anyone else having these issues? </div> <hr> IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses. </body> </html>