About notification procedure

[Yu Watanabe]

Hello,

I would like to get an advice regarding to the host and service notification procedure.

Following are few conditions that I have for my configuration.

1. I am monitoring host : Host A and associates  icmp_ping_alive for service.

2. The host configuration for Host A is below:
Notifications enabled: disabled
Max check attempts: 3
Notification interval: 60

3. The service configuration for icmp_ping_alive
Notifications enabled: enabled
Max check attempts: 3
Notification interval: 60

I have following lines were in the nagios.log.

   3440 [1207507087] HOST ALERT: HostA;DOWN;SOFT;1;CRITICAL - 192.168.0.1: rta nan, lost 100%
   3441 [1207507097] HOST ALERT: HostA;DOWN;SOFT;2;CRITICAL - 192.168.0.1: rta nan, lost 100%
   3442 [1207507107] HOST ALERT: HostA;DOWN;HARD;3;CRITICAL - 192.168.0.1: rta nan, lost 100%
   3447 [1207507107] SERVICE ALERT: HostA;icmp_ping_alive;CRITICAL;HARD;1;CRITICAL - 192.168.0.1: rta nan, lost 100%
   3450 [1207507187] HOST ALERT: HostA;UP;HARD;1;OK - 192.168.0.1: rta 0.803ms, lost 0%

My question is why there wasn't any notification after the line 3447?

I have searched the document(Nagios 2.x) for this issue but I couldn't
find a description which describes, 
"Why Nagios does not send Service Notification if there were an Host Hard Status changes before the Service Alert?"

I have also checked the log and confirmed it that there were any Service Notification
in the last one hour.

Yu Watanabe


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
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