first_notification_delay set but notifications still being send immediately

Mohr James james.mohr at elaxy.com
Thu Aug 14 07:39:45 CEST 2008


Hi All!

We have a service that is configured like this:

define service {
       use                             archiv_service
       host_name                       c21-app-01
       service_description             d.3 gateway
       check_command                   none
       active_checks_enabled           0
       max_check_attempts              1
       first_notification_delay        5
       normal_check_interval           180
       notification_interval           180
}

With interval_length=60, this should mean that the services should wait
5 minutes before sending out a notification. This morining, we had these
entries in the history:

[08-14-2008 06:19:51] SERVICE ALERT: c21-app-01;d.3 gateway;OK;HARD;1;OK
[08-14-2008 06:19:41] SERVICE ALERT: c21-app-01;d.3
gateway;CRITICAL;HARD;1;Error

A notification was sent at 08-14-2008 06:19:41, but this it does not
make sense to me. Any help is appreciated.

Regards,

Jim Mohr

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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