first_notification_delay & recovery messages
Brandino Andreas
ampranti at gmail.com
Tue Sep 25 20:00:25 CEST 2007
I get successfully a notification about the problem of the service.
But i don't get notification about the recovery.
For example:
I stop the service, i wait 10-15 minutes and then i get the error
notification. I start the service, its again ok, but i never get the
recovery notification.
The problem have to do with the way "first_notification_delay" is
being handled because if i remove that line then it works fine.
Regards
Tuesday, September 25, 2007, 5:53:09 PM, you wrote:
> Brandino Andreas wrote:
>> Hi all again!!
>>
>> I face a problem with first_notification_delay (I wrote a similar
>> mail some days ago but still i cant find any mistake in my
>> configuration)
>>
>> - When i use "first_notification_delay 10" when i should get a recovery
>> notification? Immediately after the service state is "OK" or service
>> state is OK + notification interval?
>>
>> - If i remove the option "first_notification_delay 10" i get
>> with success recovery messages.
>> When i use "first_notification_delay 10" nagios never calls the
>> notification command (doesn't appear an attempt to the notification
>> log). So it isn't an error in my notification command.
>>
>> All the configuration files where old, from version 2.5x. Today i
>> installed again 3.03b from scratch , and i migrate all configuration
>> (using the new default files),line by line , so i don't miss anything new.
>> But again i don't get any recovery notifications.
>>
>> A service configuration looks like that:
>>
>> define service{
>> name local-service ; The name of this service template
>> use generic-service ; Inherit default values from the generic-service definition
>> max_check_attempts 4 ; Re-check the service up to 4 times in order to determine its final (hard) state
>> normal_check_interval 5 ; Check the service every 5 minutes under normal conditions
>> retry_check_interval 1 ; Re-check the service every minute until a hard state can be determined
>> register 0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
>> }
>>
>> define service{
>> use generic-service ; Name of service template to use
>> host_name Central
>> service_description Service1
>> is_volatile 0
>> check_period 24x7
>> max_check_attempts 3
>> normal_check_interval 5
>> retry_check_interval 1
>> contact_groups sadmins
>> notification_interval 0
>> notification_period 24x7
>> notification_options c,r
>> first_notification_delay 10
>> check_command check_snmp_interface!snmp!service1
>> }
>>
>>
>>
>> Any idea?
>>
>>
>> Regards
> Is the service problem getting resolved before 1) the 10 second
> notification delay and 2) the next active check of the service? If so,
> there would be no problem notification in the first place, so you
> wouldn't get a recovery notification. Recovery notifications only go
> out if Nagios sent a notification about a problem.
> Ethan Galstad,
> Nagios Developer
> ---
> Email: nagios at nagios.org
> Website: http://www.nagios.org
<> --- - - - --- <>
Brandino Andreas
ampranti at gmail.com
<> --- - - - --- <>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
More information about the Developers
mailing list