Notification sent during host downtime
Posted: Mon Jan 21, 2013 5:20 am
Hello everybody
I am using Nagios in a professional environment, and I'm facing a problem. I tought that I understood how downtime works, but this problem shows that I don't...
Technical environment :
Nagios Core 3.4.1 on Ubuntu 8.04.
Here is my host configuration (and its template) :
Scenario :
I've got a host : HOST1.
I shedule a downtime on this host : from 17/01/2013 04:00 to 19/01/2013 18:00.
I shut down this host on 17/01 around 20h.
Bug :
- I receive notification every 3 or 4 minutes.
- I see no log of these notifications in nagios.log
Following :
- Host1 is now up
- I remove the downtime
- I edit my nagios configuration : I remove "retry_interval" and "notification_interval"
- Restart nagios
- I shedule a downtime on this host : from 17/01/2013 21h17 to 19/01/2013 18:00.
- I receive a "DOWNTIME START" notification at 21h17 --> OK
- I shut down HOST1
- I wait till 21h23 --> no notification received.
- I launch a "FORCED HOST CHECK" --> no notification received.
- 21h26 : I edit the nagios configuration : "retry_interval = 2" and "notification_interval = 1"
- Restart nagios
- 21h30, I receive a "HOST DOWN" notification
Conclusion : When i configure retry_interval and/or notification_interval, it seems to bypass the downtime configuration...
My question is :
Is this normal ? Are downtimes supposed to work like that ? Or is this some kind of bug ?
Information :
I found this in the nagios bugtracker :
http://tracker.nagios.org/view.php?id=294
Maybe it is related ?
Thanks in advance for your help.
Yours,
Misterdev.
I am using Nagios in a professional environment, and I'm facing a problem. I tought that I understood how downtime works, but this problem shows that I don't...
Technical environment :
Nagios Core 3.4.1 on Ubuntu 8.04.
Here is my host configuration (and its template) :
Code: Select all
define host{
host_name HOST1
use TEMPLATE1
alias HOST1
address 192.168.0.9
max_check_attempts 3
check_interval 1
retry_interval 1
passive_checks_enabled 0
check_period 00h_-_24h_LMMJVSD
contacts CONTACT_SUPERVISION
notification_interval 3
notification_period 00h_-_24h_LMMJVSD
notification_options d,r,u,s
notifications_enabled 1
}
define host{
name TEMPLATE1
alias TEMPLATE1
check_command check_host_alive_icmp!1500,100%!2000,100%
max_check_attempts 1
check_interval 2
retry_interval 2
active_checks_enabled 1
passive_checks_enabled 0
check_period 00h_-_24h_LMMJVSD
notification_interval 0
notification_period 00h_-_24h_LMMJVSD
register 0
}
I've got a host : HOST1.
I shedule a downtime on this host : from 17/01/2013 04:00 to 19/01/2013 18:00.
I shut down this host on 17/01 around 20h.
Bug :
- I receive notification every 3 or 4 minutes.
- I see no log of these notifications in nagios.log
Following :
- Host1 is now up
- I remove the downtime
- I edit my nagios configuration : I remove "retry_interval" and "notification_interval"
Code: Select all
max_check_attempts 0
retry_interval 0
Remove line : notification_interval 3- I shedule a downtime on this host : from 17/01/2013 21h17 to 19/01/2013 18:00.
- I receive a "DOWNTIME START" notification at 21h17 --> OK
- I shut down HOST1
- I wait till 21h23 --> no notification received.
- I launch a "FORCED HOST CHECK" --> no notification received.
- 21h26 : I edit the nagios configuration : "retry_interval = 2" and "notification_interval = 1"
Code: Select all
max_check_attempts 2
retry_interval 1
notification_interval 1- 21h30, I receive a "HOST DOWN" notification
Conclusion : When i configure retry_interval and/or notification_interval, it seems to bypass the downtime configuration...
My question is :
Is this normal ? Are downtimes supposed to work like that ? Or is this some kind of bug ?
Information :
I found this in the nagios bugtracker :
http://tracker.nagios.org/view.php?id=294
Maybe it is related ?
Thanks in advance for your help.
Yours,
Misterdev.