<div dir="ltr"><div><br></div> Hello,<div><br></div><div> 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.</div><div> 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.</div><div> The monitoring has no latency and this behavior happens in different installation sizes that we have.<br>
<br>
<span style="font-family:"courier new",courier,monospace">define host {<br>
_HOST_ID 29<br>
host_name ns3<br>
check_command check-host-alive<br>
max_check_attempts 5<br>
check_interval 5<br>
check_period 24x7<br>
retry_interval 1<br>
</span><div><span style="font-family:"courier new",courier,monospace"><br></span></div><div><span style="font-family:"courier new",courier,monospace"><br>
NAEMON<br>
[Sat Feb 25 02:00:54 2017] HOST ALERT: ns3;DOWN;SOFT;1;CRITICAL - <a href="http://ns3.opservices.com.br">ns3.opservices.com.br</a>: rta nan, lost 100%<br>
[Sat Feb 25 02:01:16 2017] HOST ALERT: ns3;DOWN;SOFT;2;CRITICAL - <a href="http://ns3.opservices.com.br">ns3.opservices.com.br</a>: rta nan, lost 100%<br>
[Sat Feb 25 02:02:01 2017] HOST ALERT: ns3;DOWN;SOFT;3;CRITICAL - <a href="http://ns3.opservices.com.br">ns3.opservices.com.br</a>: rta nan, lost 100%<br>
[Sat Feb 25 02:02:15 2017] HOST ALERT: ns3;DOWN;SOFT;4;CRITICAL - <a href="http://ns3.opservices.com.br">ns3.opservices.com.br</a>: rta nan, lost 100%<br>
[Sat Feb 25 02:02:28 2017] HOST ALERT: ns3;DOWN;HARD;5;CRITICAL - <a href="http://ns3.opservices.com.br">ns3.opservices.com.br</a>: rta nan, lost 100%<br>
[Sat Feb 25 02:02:59 2017] HOST ALERT: ns3;UP;HARD;1;OK - <a href="http://ns3.opservices.com.br">ns3.opservices.com.br</a>: , rta 167.203ms, lost 0%<br>
<br>
NAGIOS 3.5.1<br>
[Sat Feb 25 02:00:55 2017] HOST ALERT: ns3;DOWN;SOFT;1;CRITICAL - <a href="http://ns3.opservices.com.br">ns3.opservices.com.br</a>: rta nan, lost 100%<br>
[Sat Feb 25 02:01:29 2017] HOST ALERT: ns3;DOWN;SOFT;2;CRITICAL - <a href="http://ns3.opservices.com.br">ns3.opservices.com.br</a>: rta nan, lost 100%<br>
[Sat Feb 25 02:02:09 2017] HOST ALERT: ns3;DOWN;SOFT;3;CRITICAL - <a href="http://ns3.opservices.com.br">ns3.opservices.com.br</a>: rta nan, lost 100%<br>
[Sat Feb 25 02:02:29 2017] HOST ALERT: ns3;DOWN;SOFT;4;CRITICAL - <a href="http://ns3.opservices.com.br">ns3.opservices.com.br</a>: rta nan, lost 100%<br>
[Sat Feb 25 02:03:04 2017] HOST ALERT: ns3;DOWN;HARD;5;CRITICAL - <a href="http://ns3.opservices.com.br">ns3.opservices.com.br</a>: rta nan, lost 100%<br>
[Sat Feb 25 02:03:09 2017] HOST ALERT: ns3;UP;HARD;1;OK - <a href="http://ns3.opservices.com.br">ns3.opservices.com.br</a>: , rta 171.734ms, lost 0%</span><br></div></div><div><span style="font-family:"courier new",courier,monospace"><br></span></div><div><span style="font-family:"courier new",courier,monospace"> Any ideas?</span></div><div><span style="font-family:"courier new",courier,monospace"> </span></div><div><span style="font-family:"courier new",courier,monospace"> Alessandro Ren</span></div><div><span style="font-family:"courier new",courier,monospace"><br></span></div><div><span style="font-family:"courier new",courier,monospace"> []s.</span></div><div><span style="font-family:"courier new",courier,monospace"><br></span></div></div>