Re: [Nagios-users] Notification did not execute
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 : >> 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" 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 : 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@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
Re: [Nagios-users] Notification did not execute
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 :
> 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" 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 :
>> > 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
>> > 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_optionsw,u,r,c
>> >> check_period24x7
>> >> check_interval 1
>> >> max_check_attempts 3
>> >> first_notification_delay0
>> >> 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
>> >> contactsnagiosadmin
>> >> check_interval 1
>> >> max_check_attempts 3
>> >> notification_interval 10
>> >> flap_detection_enabled 0
>> >> first_notification_delay0
>> >> }
>> >>
>> >> 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/
>> >> ___
Re: [Nagios-users] Notification did not execute
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" 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 :
> > 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
> > 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_optionsw,u,r,c
> >> check_period24x7
> >> check_interval 1
> >> max_check_attempts 3
> >> first_notification_delay0
> >> 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
> >> contactsnagiosadmin
> >> check_interval 1
> >> max_check_attempts 3
> >> notification_interval 10
> >> flap_detection_enabled 0
> >> first_notification_delay0
> >> }
> >>
> >> 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
> >
Re: [Nagios-users] Notification did not execute
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 :
> 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
> 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_optionsw,u,r,c
>> check_period24x7
>> check_interval 1
>> max_check_attempts 3
>> first_notification_delay0
>> 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
>> contactsnagiosadmin
>> check_interval 1
>> max_check_attempts 3
>> notification_interval 10
>> flap_detection_enabled 0
>> first_notification_delay0
>> }
>>
>> 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/1
Re: [Nagios-users] Notification did not execute
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 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_optionsw,u,r,c
> check_period24x7
> check_interval 1
> max_check_attempts 3
> first_notification_delay0
> 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
> contactsnagiosadmin
> check_interval 1
> max_check_attempts 3
> notification_interval 10
> flap_detection_enabled 0
> first_notification_delay0
> }
>
> 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
[Nagios-users] Notification did not execute
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_optionsw,u,r,c
check_period24x7
check_interval 1
max_check_attempts 3
first_notification_delay0
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
contactsnagiosadmin
check_interval 1
max_check_attempts 3
notification_interval 10
flap_detection_enabled 0
first_notification_delay0
}
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
