Host vs. Service Notifications

[Mike A. Davis]

Hi.
 
I use Nagios on a large scale network, but to introduce my problem, I
will limit this down to just 2 hosts.
 
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.
 
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!
 
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.
 
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.
 
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 PING service going
down (since the service failure fell back on a host check), so I
shouldn't have received the service up notification either?
 
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!
 
Anyone have any ideas on this?  Any help would be greatly appreciated.
 
Using RedHat 8.0, Nagios 1.0
 
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:
 
###################################################
DEBUG4 LOG OF HOST A AND HOST B GOING DOWN 
###################################################
 
HOST NOTIFICATION ATTEMPT: Host 'hosta'
        Current time: Sun Apr  6 19:09:25 2003
        HOST STATE CHANGE!
        Current notification number: 1
        Current Time: Sun Apr  6 19:09:25 2003
        Next acceptable notification time: Sun Apr  6 20:09:25 2003
        Notify user mike
        Raw Command:    ---- snip ----
        Processed Command:   ---- snip ----
        APPROPRIATE CONTACTS HAVE BEEN NOTIFIED
 
HOST NOTIFICATION ATTEMPT: Host 'hostb'
        Current time: Sun Apr  6 19:13:15 2003
        We shouldn't notify about UNREACHABLE status for this host!
        Sending out a notification for this host is not viable at this
time.
 
#################################################
DEBUG4 LOG OF HOST A AND HOST B COMING UP 
#################################################
 
SERVICE NOTIFICATION ATTEMPT: Service 'PING' on host 'hosta'
        Current time: Sun Apr  6 19:14:55 2003
        Current notification number: 1
        Calculating next valid notification time...
                Default interval: 240
        Interval used for calculating next valid notification time: 240
        Current Time: Sun Apr  6 19:14:55 2003
        Next acceptable notification time: Sun Apr  6 23:14:55 2003
        Service notification will NOT be escalated
        Notify user mike
        Raw Command:   ---- snip ----
        Processed Command:   ---- snip ----
        APPROPRIATE CONTACTS HAVE BEEN NOTIFIED
 
SERVICE NOTIFICATION ATTEMPT: Service 'PING' on host 'hostb'
        Current time: Sun Apr  6 19:17:45 2003
        Current notification number: 1
        Calculating next valid notification time...
                Default interval: 240
        Interval used for calculating next valid notification time: 240
        Current Time: Sun Apr  6 19:17:45 2003
        Next acceptable notification time: Sun Apr  6 23:17:45 2003
        Service notification will NOT be escalated
        Notify user mike
        Raw Command:  ---- snip ----
        Processed Command:  ---- snip ----
        APPROPRIATE CONTACTS HAVE BEEN NOTIFIED
 
################################################
DEBUG4 LOG OF HOST A DOWN AND HOST B COMING UP
################################################
 
HOST NOTIFICATION ATTEMPT: Host 'hosta'
        Current time: Sun Apr  6 19:52:59 2003
        Its not yet time to re-notify the contacts about this host
problem...
        Next acceptable notification time: Sun Apr  6 20:46:43 2003
        Sending out a notification for this host is not viable at this
time.
 
SERVICE NOTIFICATION ATTEMPT: Service 'PING' on host 'hostb'
        Current time: Sun Apr  6 19:55:09 2003
        Current notification number: 1
        Calculating next valid notification time...
                Default interval: 240
        Interval used for calculating next valid notification time: 240
        Current Time: Sun Apr  6 19:55:09 2003
        Next acceptable notification time: Sun Apr  6 23:55:09 2003
        Service notification will NOT be escalated
        Notify user mike
        Raw Command:  ---- snip ----
        Processed Command:  ---- snip ----
        APPROPRIATE CONTACTS HAVE BEEN NOTIFIED
 
 
########  END OF DEBUG  ##########
 
 
If any other information is needed, please let me know.  Thanks in
advance!
 
 
Mike A. Davis
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20030407/b6181449/attachment.html>