<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=ProgId content=Word.Document> <meta name=Generator content="Microsoft Word 10"> <meta name=Originator content="Microsoft Word 10"> <link rel=File-List href="cid:filelist.xml@01C2FCF9.0CCE2D10"> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="time"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/>  <style>  </style>  </head> <body lang=EN-US link=blue vlink=purple style='tab-interval:.5in'> <div class=Section1> Hi.<o:p></o:p> <o:p> </o:p> I use Nagios on a large scale network, but to introduce my problem, I will limit this down to just 2 hosts.<o:p></o:p> <o:p> </o:p> I have Host A, which is a parent of Host B. Both hosts have only one service defined to them, which is ping. In the host configuration, I use the notification options d,r. In the service configuration, I use the notification options w,c,r,u. I have nothing defined in my dependencies.cfg file.<o:p></o:p> <o:p> </o:p> If Host A and Host B go down, I only receive the HOST DOWN notification for Host A, as Host B is now UNREACHABLE (and I don’t have u set in host configuration). This is perfect!<o:p></o:p> <o:p> </o:p> However, the problem that I am seeing is when Host A and Host B come up, I receive the SERIVCE UP (ping) notifications for both hosts. Further more, if parent Host A is still down, and Host B comes up, I still receive the SERVICE UP (ping) notification for Host B.<o:p></o:p> <o:p> </o:p> The documentation states: Note: Notifications about host or service recoveries are only sent out if a notification was sent out for the original problem. It doesn't make sense to get a recovery notification for something you never knew was a problem.<o:p></o:p> <o:p> </o:p> I guess what I'm getting at is, why am I receiving the SERVICE UP's instead of the HOST UP's? Could this have something to do with the problem? Even so, I never get a notification of the <st1:place>PING</st1:place> service going down (since the service failure fell back on a host check), so I shouldn't have received the service up notification either?<o:p></o:p> <o:p> </o:p> In my situation, if a switch were to be offline for a good 10 minutes, once it came back up, I would get 100+ pages about services coming back up. eeeeek!<o:p></o:p> <o:p> </o:p> Anyone have any ideas on this? Any help would be greatly appreciated.<o:p></o:p> <o:p> </o:p> Using RedHat 8.0, Nagios 1.0<o:p></o:p> <o:p> </o:p> I've recompiled Nagios with --enable-DEBUG4 but did not find any information what would lead me to a solution. Regardless, it is posted below:<o:p></o:p> <o:p> </o:p> ###################################################<o:p></o:p> DEBUG4 LOG OF HOST A AND HOST B GOING DOWN <o:p></o:p> ###################################################<o:p></o:p> <o:p> </o:p> HOST NOTIFICATION ATTEMPT: Host 'hosta'<o:p></o:p> Current time: Sun Apr 6 <st1:time Hour="19" Minute="9">19:09:25</st1:time> 2003<o:p></o:p> HOST STATE CHANGE!<o:p></o:p> Current notification number: 1<o:p></o:p> Current Time: Sun Apr 6 <st1:time Hour="19" Minute="9">19:09:25</st1:time> 2003<o:p></o:p> Next acceptable notification time: Sun Apr 6 <st1:time Hour="20" Minute="9">20:09:25</st1:time> 2003<o:p></o:p> Notify user mike<o:p></o:p> Raw Command: ---- snip ----<o:p></o:p> Processed Command: ---- snip ----<o:p></o:p> APPROPRIATE CONTACTS HAVE BEEN NOTIFIED<o:p></o:p> <o:p> </o:p> HOST NOTIFICATION ATTEMPT: Host 'hostb'<o:p></o:p> Current time: Sun Apr 6 <st1:time Hour="19" Minute="13">19:13:15</st1:time> 2003<o:p></o:p> We shouldn't notify about UNREACHABLE status for this host!<o:p></o:p> Sending out a notification for this host is not viable at this time.<o:p></o:p> <o:p> </o:p> #################################################<o:p></o:p> DEBUG4 LOG OF HOST A AND HOST B COMING UP <o:p></o:p> #################################################<o:p></o:p> <o:p> </o:p> SERVICE NOTIFICATION ATTEMPT: Service 'PING' on host 'hosta'<o:p></o:p> Current time: Sun Apr 6 <st1:time Hour="19" Minute="14">19:14:55</st1:time> 2003<o:p></o:p> Current notification number: 1<o:p></o:p> Calculating next valid notification time...<o:p></o:p> Default interval: 240<o:p></o:p> Interval used for calculating next valid notification time: 240<o:p></o:p> Current Time: Sun Apr 6 <st1:time Hour="19" Minute="14">19:14:55</st1:time> 2003<o:p></o:p> Next acceptable notification time: Sun Apr 6 <st1:time Hour="23" Minute="14">23:14:55</st1:time> 2003<o:p></o:p> Service notification will NOT be escalated<o:p></o:p> Notify user mike<o:p></o:p> Raw Command: ---- snip ----<o:p></o:p> Processed Command: ---- snip ----<o:p></o:p> APPROPRIATE CONTACTS HAVE BEEN NOTIFIED<o:p></o:p> <o:p> </o:p> SERVICE NOTIFICATION ATTEMPT: Service 'PING' on host 'hostb'<o:p></o:p> Current time: Sun Apr 6 <st1:time Hour="19" Minute="17">19:17:45</st1:time> 2003<o:p></o:p> Current notification number: 1<o:p></o:p> Calculating next valid notification time...<o:p></o:p> Default interval: 240<o:p></o:p> Interval used for calculating next valid notification time: 240<o:p></o:p> Current Time: Sun Apr 6 <st1:time Hour="19" Minute="17">19:17:45</st1:time> 2003<o:p></o:p> Next acceptable notification time: Sun Apr 6 <st1:time Hour="23" Minute="17">23:17:45</st1:time> 2003<o:p></o:p> Service notification will NOT be escalated<o:p></o:p> Notify user mike<o:p></o:p> Raw Command: ---- snip ----<o:p></o:p> Processed Command: ---- snip ----<o:p></o:p> APPROPRIATE CONTACTS HAVE BEEN NOTIFIED<o:p></o:p> <o:p> </o:p> ################################################<o:p></o:p> DEBUG4 LOG OF HOST A DOWN AND HOST B COMING UP<o:p></o:p> ################################################<o:p></o:p> <o:p> </o:p> HOST NOTIFICATION ATTEMPT: Host 'hosta'<o:p></o:p> Current time: Sun Apr 6 <st1:time Hour="19" Minute="52">19:52:59</st1:time> 2003<o:p></o:p> Its not yet time to re-notify the contacts about this host problem...<o:p></o:p> Next acceptable notification time: Sun Apr 6 <st1:time Hour="20" Minute="46">20:46:43</st1:time> 2003<o:p></o:p> Sending out a notification for this host is not viable at this time.<o:p></o:p> <o:p> </o:p> SERVICE NOTIFICATION ATTEMPT: Service 'PING' on host 'hostb'<o:p></o:p> Current time: Sun Apr 6 <st1:time Hour="19" Minute="55">19:55:09</st1:time> 2003<o:p></o:p> Current notification number: 1<o:p></o:p> Calculating next valid notification time...<o:p></o:p> Default interval: 240<o:p></o:p> Interval used for calculating next valid notification time: 240<o:p></o:p> Current Time: Sun Apr 6 <st1:time Hour="19" Minute="55">19:55:09</st1:time> 2003<o:p></o:p> Next acceptable notification time: Sun Apr 6 <st1:time Hour="23" Minute="55">23:55:09</st1:time> 2003<o:p></o:p> Service notification will NOT be escalated<o:p></o:p> Notify user mike<o:p></o:p> Raw Command: ---- snip ----<o:p></o:p> Processed Command: ---- snip ----<o:p></o:p> APPROPRIATE CONTACTS HAVE BEEN NOTIFIED<o:p></o:p> <o:p> </o:p> <o:p> </o:p> ######## END OF DEBUG ##########<o:p></o:p> <o:p> </o:p> <o:p> </o:p> If any other information is needed, please let me know. Thanks in advance!<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Mike A. Davis<o:p></o:p> <o:p> </o:p> </div> </body> </html>