[naemon-dev] Naemon not respecting retry iinterval

Mikael Falkvidd mikael.falkvidd at op5.com
Wed Mar 8 13:17:00 CET 2017


Hi Alessandro.

Are there services on this host? In that case, the recheck is probably due
to on-demand host checks being triggered. More information is available at
https://jira.op5.com/browse/MON-8298?focusedCommentId=
201320&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpane
l#comment-201320

You might want to use first_notification_delay as described in
https://jira.op5.com/browse/MON-6634?focusedCommentId=
26527&page=com.atlassian.jira.plugin.system.issuetabpanels:
comment-tabpanel#comment-26527

Best regards
Mikael Falkvidd
OP5 Development Team Lead

On 7 March 2017 at 17:35, Alessandro Ren <alessandro.ren at opservices.com>
wrote:

>
>    Hello,
>
>    I have been experiencing some odd behavior  with retry interval. Since
> I was using a older version on Nagios, 3.5.1 to be more precisely, I had
> the idea to try naemon to see if the same thing would happens, as, I
> thought, this could be a bug long solved.
>    For my surprise, the same behavior happened on naemon 1.0.6, where it
> will not respect the 1 minute retry interval, as you can see in the logs
> bellow.
>    The monitoring has no latency and this behavior happens in different
> installation sizes that we have.
>
> define host {
>         _HOST_ID 29
>         host_name ns3
>         check_command check-host-alive
>         max_check_attempts 5
>         check_interval 5
>         check_period 24x7
>         retry_interval 1
>
>
>
> NAEMON
> [Sat Feb 25 02:00:54 2017] HOST ALERT: ns3;DOWN;SOFT;1;CRITICAL -
> ns3.opservices.com.br: rta nan, lost 100%
> [Sat Feb 25 02:01:16 2017] HOST ALERT: ns3;DOWN;SOFT;2;CRITICAL -
> ns3.opservices.com.br: rta nan, lost 100%
> [Sat Feb 25 02:02:01 2017] HOST ALERT: ns3;DOWN;SOFT;3;CRITICAL -
> ns3.opservices.com.br: rta nan, lost 100%
> [Sat Feb 25 02:02:15 2017] HOST ALERT: ns3;DOWN;SOFT;4;CRITICAL -
> ns3.opservices.com.br: rta nan, lost 100%
> [Sat Feb 25 02:02:28 2017] HOST ALERT: ns3;DOWN;HARD;5;CRITICAL -
> ns3.opservices.com.br: rta nan, lost 100%
> [Sat Feb 25 02:02:59 2017] HOST ALERT: ns3;UP;HARD;1;OK -
> ns3.opservices.com.br: , rta 167.203ms, lost 0%
>
> NAGIOS 3.5.1
> [Sat Feb 25 02:00:55 2017] HOST ALERT: ns3;DOWN;SOFT;1;CRITICAL -
> ns3.opservices.com.br: rta nan, lost 100%
> [Sat Feb 25 02:01:29 2017] HOST ALERT: ns3;DOWN;SOFT;2;CRITICAL -
> ns3.opservices.com.br: rta nan, lost 100%
> [Sat Feb 25 02:02:09 2017] HOST ALERT: ns3;DOWN;SOFT;3;CRITICAL -
> ns3.opservices.com.br: rta nan, lost 100%
> [Sat Feb 25 02:02:29 2017] HOST ALERT: ns3;DOWN;SOFT;4;CRITICAL -
> ns3.opservices.com.br: rta nan, lost 100%
> [Sat Feb 25 02:03:04 2017] HOST ALERT: ns3;DOWN;HARD;5;CRITICAL -
> ns3.opservices.com.br: rta nan, lost 100%
> [Sat Feb 25 02:03:09 2017] HOST ALERT: ns3;UP;HARD;1;OK -
> ns3.opservices.com.br: , rta 171.734ms, lost 0%
>
>    Any ideas?
>
>     Alessandro Ren
>
>    []s.
>
>


-- 

___________________________________________________________
*Mikael Falkvidd | Development Team Lead **| OP5*
Email: mikael.falkvidd at op5.com | LinkedIn
<https://se.linkedin.com/in/mikaelfalkvidd>

OP5 AB | Första Långgatan 19 | 413 27 Göteborg | Sweden
www.op5.com | LinkedIn <https://www.linkedin.com/company/op5> | Twitter
<http://twitter.com/op5ab> | Facebook <https://www.facebook.com/op5ab/> |
Youtube <https://www.youtube.com/user/op5video> | Vimeo
<https://vimeo.com/op5>
VAT SE556582913101
Red Herring Global top 100
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/naemon-dev/attachments/20170308/e0631614/attachment.html>


More information about the Naemon-dev mailing list