Check_Ping plugin not Incrementing Check Attempt Value

[Robert V. Bolton]

On Mon, Jan 30, 2012 at 11:39 AM, Claudio Kuenzler
<ck at claudiokuenzler.com>wrote:

> It looks like you use parent-child-relationships?
> That would explain why it's written "Host Unreachable (172.21.10.170) "
> instead of Host Down.
> Was the parent of this host down as well? In this case, Nagios 'knows'
> that it doesn't make sense to continue checks on the child hosts.
>

This host is duel homed using both Ethernet and Infiniband networks. To
Nagios's point of view the parent of this host is the Ethernet switch that
it is plugged into, which didn't go down at all during this outage. Host
Unreachable is a valid ICMP code, so that's why the plugin reported this
error, not because of any Nagios parent/child relationship.

So in this situation Nagios should have increased the check attempts count
by one until the max check attempts threshold was reached, thus sending out
a service notification. Is this an error in Nagios or the check_ping
plugin. I'm using Nagios v3.2.3 and check_ping v1.4.15 by the way.

--
*Robert V. Bolton*
Email: robert at robertvbolton.com
Web: http://robertvbolton.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20120130/444923b8/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
-------------- next part --------------
_______________________________________________
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