Nagios 3.0b2 - Not sending Notifications?

[Ethan Galstad]

Thanks for the debug report Hendrik.  I changed the way 
contacts/contactgroups are internally referenced in the daemon between 
b1 and b2.  I forgot to update some pointers, so notifications fail to 
go out to members of contactgroups.  They still go out to individual 
contacts that assigned to hosts/services, however.

I'll get a patch into CVS ASAP and release 3.0b3 tomorrow.

Hendrik Bäcker wrote:
> Sorry for double posting...
> 
> I've had enabled debug_level = 48 and got:
> 
> [1188406203.151628] [016.1] [pid=18818] Current/Max Attempt(s): 4/4
> [1188406203.151642] [016.1] [pid=18818] Service has reached max number
> of rechecks, so we'll handle the error...
> [1188406203.151962] [032.0] [pid=18818] ** Service Notification Attempt
> ** Host: 'hotel7', Service: 'xinetd Processes', Type: 0, Current State
> : 2, Last Notification: Thu Jan  1 01:00:00 1970
> [1188406203.151999] [032.0] [pid=18818] Notification viability test passed.
> [1188406203.152019] [032.1] [pid=18818] Current notification number: 1
> [1188406203.152037] [032.1] [pid=18818] Service notification will NOT be
> escalated.
> 
> [1188406203.152060] [032.0] [pid=18818] No contacts were found for
> notification purposes.  No notification was sent out.
> 
> [1188406203.152190] [016.1] [pid=18818] Rescheduling next check of
> service at Wed Aug 29 18:50:53 2007
> 
> ....
> 
> That with the "non contacts" is not true...
> 
> Out of the actual objects.cache:
> 
> define service {
>         host_name       hotel7
>         service_description     xinetd Processes
>         check_period    24x7
>         check_command   check_local_procs_cmd!1:15!1:30!xinetd
>         contact_groups  admins
>         notification_period     24x7
>         initial_state   o
>         check_interval  60.000000
>         retry_interval  5.000000
>         max_check_attempts      4
>         is_volatile     0
>         parallelize_check       1
>         active_checks_enabled   1
>         passive_checks_enabled  1
>         obsess_over_service     1
>         event_handler_enabled   1
>         low_flap_threshold      0.000000
>         high_flap_threshold     0.000000
>         flap_detection_enabled  1
>         flap_detection_options  o,w,u,c
>         freshness_threshold     0
>         check_freshness 0
>         notification_options    u,w,c,r
>         notifications_enabled   1
>         notification_interval   1800.000000
>         first_notification_delay        0.000000
>         stalking_options        n
>         process_perf_data       1
>         failure_prediction_enabled      1
>         retain_status_information       1
>         retain_nonstatus_information    1
>         }
> 
> 
> define contactgroup {
>         contactgroup_name       admins
>         alias   Nagios Administrators
>         members nagios-admin
>         }
> 
> 
> define contact {
>         contact_name    nagios-admin
>         alias   Nagios Admin
>         service_notification_period     24x7
>         host_notification_period        24x7
>         service_notification_options    w,u,c,r
>         host_notification_options       d,r
>         service_notification_commands   notify-by-email
>         host_notification_commands      host-notify-by-email
>         email   me at mail.org(faked)
>         host_notifications_enabled      1
>         service_notifications_enabled   1
>         can_submit_commands     1
>         retain_status_information       1
>         retain_nonstatus_information    1
>         }
> 
> So... I think all should be fine...
> 
> Regards
> 
> 


Ethan Galstad,
Nagios Developer
---
Email: nagios at nagios.org
Website: http://www.nagios.org

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/