Service notifications when host is down

[Ben Whaley]

 > The only time I ever had this problem was because my notification
 > commands were broken.  Nagios uses different notification commands for

Well, I'm definitely using some custom notification scripts but I don't 
think that is the problem. Notifications work fine. The problem is that 
I'm getting notifications from service checks that return CRITICAL when 
I shouldn't - the host is down.

Any other thoughts on this issue folks? Sounds like several people are 
running into the same behavior.

Ben

Sean Dilda wrote:
> On Wed, 2004-04-21 at 19:20, Quanah Gibson-Mount wrote:
> 
>>Quoting Ben Whaley <Benjamin.Whaley at colorado.edu>:
>>
>>
>>> > I though of setting a 'ping' service check on the host, and making 
>>>all other
>>> > checks dependent on it, but that seems to me to be more of a 
>>>workaround than
>>> > a solution, and it doesn't fully solve the scheduled downtime
>>>problem.
>>>
>>>Yes, we had the same idea. I am currently using some other, similar work
>>>
>>>arounds to solve problems that Nagios doesn't have a solution for but 
>>>they have introduced more problems than they've fixed.
>>>
>>>What's strange about this particular case, however, is that Nagios 
>>>*usually* catches it. For example, in the following sequence, the host 
>>>down alert was generated before the service checks, thus avoiding the 
>>>unnecessary notification:
>>
>>The consistent problem we have seen with Nagios is that once a host goes 
>>down, it only ever emits a single host down alert, and does not keep paging 
>>that the host is down (it correctly does not keep paging that the services 
>>for the host are down).  Despite querying the list, an answer to this has 
>>never appeared.  Perhaps it is time to file a bug on this in sourceforge.
> 
> 
> The only time I ever had this problem was because my notification
> commands were broken.  Nagios uses different notification commands for
> hosts and services, so your service notification command could be
> working while your host one isn't.  Did you check the logs to see if
> nagios attempted a notification?
> 
> In /var/log/messages (on a RHL9 box) I get something like this:
> Apr 20 13:00:24 head4 nagios: HOST NOTIFICATION:
> sean-emergpager;storage1;DOWN;host-notify-by-epager;/bin/ping -n -U -c 1
> 10.10.1.1
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null