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
On Tue, Aug 28, 2012 at 4:39 PM, Net Warrior <netwarrior...@gmail.com>wrote:
> Hi there guys.
>
> I have face something weird, I did not get a notificationn of a down
> state for a particular host,
> this is the host config.
>
> define service{
> use local-service ; Name
> of service template to use
> host_name hostname
> service_description SSH
> check_command check_ssh
> flap_detection_enabled 0
> notifications_enabled 1
> notification_options w,u,r,c
> check_period 24x7
> check_interval 1
> max_check_attempts 3
> first_notification_delay 0
> notification_interval 10
> }
>
>
>
> define host{
> use linux-server ; Name of host
> template to use
> ; This host
> definition will inherit all variables that are defined
> ; in (or
> inherited by) the linux-server host template definition.
> host_name hostname
> alias the alias
> address x.x.x.x
> contact_groups admins
> contacts nagiosadmin
> check_interval 1
> max_check_attempts 3
> notification_interval 10
> flap_detection_enabled 0
> first_notification_delay 0
> }
>
> and in the logs I got
> [1346196987.097821] [032.0] [pid=21145] ** Service Notification
> Attempt ** Host: 'hostname', Service: 'SSH', Type: 0, Options: 0,
> Current State: 2, Last Notification: Wed Dec 31 21:00:00 1969
> [1346196987.097843] [032.1] [pid=21145] The host is either down or
> unreachable, so we won't notify contacts about this service.
> [1346196987.097851] [032.0] [pid=21145] Notification viability test
> failed. No notification will be sent out.
>
> The host is either down or unreachable --- Of coure, so why the
> notification was not fired?
>
> Any idea what could be wrong?, I got some notification with other host
> and all have the same configuration, I have already restarted nagios
>
> Thanks for your time and support
> Best regards.
>
>
> ------------------------------------------------------------------------------
> 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@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
>
------------------------------------------------------------------------------
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@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
