Notification problem

Marc Powell marc at ena.com
Thu Jan 5 16:19:36 CET 2006



> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Matt Hanley
> Sent: Wednesday, January 04, 2006 2:24 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Notification problem
> 
> I'm having trouble diagnosing a problem with notifications.  I am
using
> Nagios v1.2 on Red Hat Enterprise Linux ES version 3 and it has been
> working great for the most part.  I noticed that at some point (don't
know
> when), Nagios stopped sending notifications for the PING service.  All
> other notifications appeared to be working great.  In an effort to
> troubleshoot the problem, I added a host named 'nebula' and brought
the
> interface down and back up.  No notification was sent for the host or
the
> service.
> 
> I've searched with Google, et al, but am at a loss, so any guidance
would
> be appreciated.  I've included everything I thought was relevant,
thanks!:
> 

[chop]

> Jan  4 14:30:32 nagios nagios: HOST ALERT:
nebula;DOWN;SOFT;1;/bin/ping -n
> -U -c 1 172.22.3.156
> Jan  4 14:30:35 nagios nagios: HOST ALERT:
nebula;DOWN;SOFT;2;/bin/ping -n
> -U -c 1 172.22.3.156
> Jan  4 14:30:38 nagios nagios: HOST ALERT:
nebula;DOWN;SOFT;3;/bin/ping -n
> -U -c 1 172.22.3.156
> Jan  4 14:30:41 nagios nagios: HOST ALERT:
nebula;DOWN;SOFT;4;/bin/ping -n
> -U -c 1 172.22.3.156
> Jan  4 14:30:44 nagios nagios: HOST ALERT:
nebula;DOWN;SOFT;5;/bin/ping -n
> -U -c 1 172.22.3.156
> Jan  4 14:30:48 nagios nagios: HOST ALERT:
nebula;DOWN;SOFT;6;/bin/ping -n
> -U -c 1 172.22.3.156
> Jan  4 14:30:51 nagios nagios: HOST ALERT:
nebula;DOWN;SOFT;7;/bin/ping -n
> -U -c 1 172.22.3.156
> Jan  4 14:30:54 nagios nagios: HOST ALERT:
nebula;DOWN;SOFT;8;/bin/ping -n
> -U -c 1 172.22.3.156
> Jan  4 14:30:57 nagios nagios: HOST ALERT:
nebula;DOWN;SOFT;9;/bin/ping -n
> -U -c 1 172.22.3.156
> Jan  4 14:31:00 nagios nagios: HOST ALERT:
nebula;DOWN;HARD;10;/bin/ping -
> n -U -c 1 172.22.3.156
> Jan  4 14:31:00 nagios nagios: SERVICE ALERT:
> nebula;PING;UNKNOWN;HARD;1;/bin/ping -n -U -c 5 172.22.3.156
> Jan  4 14:35:29 nagios nagios: HOST ALERT: nebula;UP;HARD;1;PING OK -
> Packet loss = 0%, RTA = 0.46 ms
> Jan  4 14:35:29 nagios nagios: SERVICE ALERT:
nebula;PING;OK;HARD;1;PING
> OK - Packet loss = 0%, RTA = 0.48 ms

To start, it looks like /bin/ping wasn't executable by nagios before
14:35 and you corrected that, is that the case?

As far as the notifications, the one thing that seems a possibility to
me is that you have retention enabled, may have disabled notifications
at some point and now the notifications_enabled setting is now being
preferenced from the retention file over the config file. If that sounds
familiar, take a look at the Retention Notes at
http://nagios.sourceforge.net/docs/1_0/xodtemplate.html.

--
Marc


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&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





More information about the Users mailing list