[Nagios-users] Notification problem

[Matt Hanley]

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!:

 

# Generic service definition template
define service{
        name                            generic-service
        active_checks_enabled           1
        passive_checks_enabled          1
        parallelize_check               1
        obsess_over_service             0
        check_freshness                 0
        check_period                    24x7
        is_volatile                     0
        max_check_attempts              3
        normal_check_interval           5
        notifications_enabled           1
        notification_interval           0
        notification_period             24x7
        event_handler_enabled           1
        flap_detection_enabled          1
        process_perf_data               1
        retain_status_information       1
        retain_nonstatus_information    1
        retry_check_interval            1
        register                        0
        }

# Ping nebula
define service {
        use                             generic-service
        host_name                       nebula
        service_description             PING
        contact_groups                  mhanley
        notification_options            c,r,u
        check_command                   check_ping!20.0,20%!100.0,40%
        }

 

define host{
        name                            generic-host    ; The name of this host template - referenced in other host definitions, used for template recursion/resolution
        notifications_enabled           1       ; Host notifications are enabled

        event_handler_enabled           1       ; Host event handler is enabled
        flap_detection_enabled          1       ; Flap detection is enabled
        process_perf_data               1       ; Process performance data
        retain_status_information       1       ; Retain status information across program restarts
        retain_nonstatus_information    1       ; Retain non-status information across program restarts

 

        register                        0       ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE!
        }

 

# 'nebula' host definition
define host{
        use                     generic-host
        host_name               nebula
        alias                   nebula.cxtec.com
        address                 172.22.3.156
        check_command           check-host-alive
        max_check_attempts      10
        notification_interval   0
        notification_period     24x7
        notification_options    d,u,r
        }

# 'mhanley' contact group definition - For things only he wants to be notified
# for
define contactgroup{
        contactgroup_name       mhanley
        alias                   Matthew Hanley
        members                 mhanley
        }

# 'mhanley' contact definition
define contact{
        contact_name                    mhanley
        alias                           Matthew Hanley
        service_notification_period     24x7
        host_notification_period        24x7
        service_notification_options    w,u,c,r
        host_notification_options       d,u,r
        service_notification_commands   notify-by-email
        host_notification_commands      host-notify-by-email
        email                           [EMAIL PROTECTED]
        }

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

 

-matt

 

Matthew Hanley

[EMAIL PROTECTED]