Notification did not execute

[Patrick Morris]

On 8/29/2012 3:54 AM, Net Warrior wrote:
> Cannot do that cuz it-s a production server, I have a testing server
> where I test the alarms with the same configuration and it works
> If I find something I will let you know.
>
> Thanks
>
>
> 2012/8/28 Travis Runyard <travisrunyard at gmail.com>:
>> That is really strange. Have you tried changing its ip to an invalid one and
>> see if you can recreate the problem?
>>
>> On Aug 28, 2012 5:29 PM, "Net Warrior" <netwarrior863 at gmail.com> wrote:
>>> Thanks for your advice, I know what you mean, but this is not the case
>>> unfortunately, In the logs I can see the 3 time check was reached and
>>> the alarm did not fired, now the server is up and I did not get the
>>> notification the server is back on line either.
>>>
>>> Is critical and not SOFT for the host and the service
>>> [1346193488] HOST ALERT: hostname;DOWN;HARD;3;(Host Check Timed Out)
>>> [1346193328] SERVICE ALERT: hostname;SSH;CRITICAL;HARD;3;CRITICAL -
>>> Socket timeout after 30 seconds
>>>
>>> [1346198377] HOST ALERT: hostname;UP;SOFT;3;PING OK - Packet loss =
>>> 0%, RTA = 4.84 ms
>>>
>>> This is weird.
>>>
>>> Thanks for your time and support
>>> Regards
>>>
>>>
>>> 2012/8/28 Travis Runyard <travisrunyard at gmail.com>:
>>>> Your should look at the log before the service notification was
>>>> suppressed
>>>> because the host was down. I'm 90% sure the reason why your host down
>>>> notification was not sent was because the host was in a soft state type
>>>> and
>>>> came back online before it was determined to be in a hard state. And you
>>>> didn't post your linux-server template config so you will have to check
>>>> your
>>>> and retry_interval definition.
>>>>
>>>> For my host objects I set a retry_interval of 1 and max_check_attemps of
>>>> 2
>>>> in the template so I get notified a little quicker when a host goes
>>>> down.
>>>>
>>>> http://nagios.sourceforge.net/docs/3_0/objectdefinitions.html
>>>>
>>>> -Travis Runyard
>>>>

I would also check to make sure host or global notifications were not 
disabled at that point in time, and that flap detection had not kicked 
in.  Those are the most likely reasons I can think of for no 
notification to happen even though the host was in a hard critical state.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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