Delayed notifications.

[Michael T. Halligan]

I'm running the 1.2.0 Nagios rpms from DAG for RHEL3 right now.

I'm wondering if there's just some problem with nagios 1.2.0's
notifications?

Notifications have been semi-flaky at best. I had a server go
down yesterday morning at 4am.  Nagios noted this, marked an
alert, but didn't send out a notification until 1PM. Embarrassingly, we
only knew the server was down because an affected user called about it.

I'm finding this really hard to track, because the archived logs don't
seem to have a time stamp.

When I look on the web interface in Notification History for this host,
it only shows notifications at 1Pm.. Clearly Nagios saw the alert but
delayed 10 hours in sending out a notification.


My configuration file for this server is as follows : 

define host {
  host_name                    some.server.name
  parents                      lbprod-gw-b.mypointsbeta.com
  alias                        some
  address                      IP.ADDR
  check_command                check-host-alive
  max_check_attempts           3
  checks_enabled               1
  failure_prediction_enabled   1
  retain_status_information    1
  retain_nonstatus_information 1
  notification_interval 120
}
                                                                                                                                                                                                     
define service {
  host_name             some.server.name
  service_description   Connectivity
  check_command         check_ping
  max_check_attempts    3
  normal_check_interval 2
  retry_check_interval  1
  check_period          24x7
  notification_interval 120
  notification_period   24x7
  notification_options  c,r
  contact_groups        admin
}
                                                                                                                                                                                                     
define service {
  host_name             some.server.name
  service_description   SSH
  check_command         check_ssh
  max_check_attempts    3
  normal_check_interval 2
  retry_check_interval  1
  check_period          24x7
  notification_interval 120
  notification_period   24x7
  notification_options  c,r
  contact_groups        admin
}
                                                                                                                                                                                                     
define service {
  host_name             some.server.name
  service_description   HTTP
  check_command         check_http
  max_check_attempts    3
  normal_check_interval 2
  retry_check_interval  1
  check_period          24x7
  notification_interval 120
  notification_period   24x7
  notification_options  c,r
  contact_groups        admin
}
                                                                                                                                                                                                     
define service {
  host_name             some.server.name
  service_description   https-tcp-443
  check_command         check_tcp!443
  max_check_attempts    3
  normal_check_interval 2
  retry_check_interval  1
  check_period          24x7
  notification_interval 120
  notification_period   24x7
  notification_options  c,r
  contact_groups        admin
}




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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