Nevermind on this question. I did a good bit more digging on Google and found
a very simple suggestion to add the -4 flag onto the check_ping command to
force it to use ipv4. When doing this, it works perfectly.
Thanks,
Daniel Ceola
From: Daniel Ceola [mailto:dce...@twgi.net]
Sent: Wednesday, December 12, 2012 9:53 AM
To: Nagios Users (nagios-users@lists.sourceforge.net)
Subject: [Nagios-users] Simple check_ping question
Hello all,
Is it meant for the "check_ping" command from the Nagios plugins to not
function when using a host name instead of an IP address? I have a handful of
hosts that I've setup within Nagios that I want to monitor the ping time (as
well as a few other items) on, but since they are dhcp clients, I have the host
within Nagios setup with the hostname on my local network instead of an IP
address.
When I do a simple check_ping using the hostname (which I have entered as the
local FQDN, not just a short name), it returns a "Network Unreachable" error.
Example:
nagios@nagios:/usr/local/nagios/libexec$ ./check_ping -H dceola.twgi.net -w
400,20% -c 600,50%
CRITICAL - Network Unreachable (dceola.twgi.net)
Thanks,
Daniel Ceola
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
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
