Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ICMP Ping to and IPv6 address fails to gather data for Ping Latency / CentOS 7.4 #1058

jwomack opened this issue Nov 2, 2017 · 1 comment


Copy link

jwomack commented Nov 2, 2017

On a CentOS 7.4 VM, running version cacti 1.1.24, the script reports a "U" back to cacti.
Even using the current development branch, reports back a "U".

The installed version of ping from iputils-20160308-10.el7.x86_64, reports back a different error message:
ping: Name or service not known

Updating the script to account for the new error message resolves the issue.

`[root@netmon tmp]# diff -u
--- 2017-11-01 19:53:41.130704992 -0700
+++ 2017-11-01 19:52:37.901373928 -0700
@@ -21,12 +21,12 @@

old linux version use 'icmp_seq'

newer use 'icmp_req' instead

-open(PROCESS, "ping -c 1 $host 2>&1 | grep -E '(icmp_[s|r]eq.*time|unknown host|Unknown host|not supported|Name or service not known)' 2>/dev/null |");
+open(PROCESS, "ping -c 1 $host 2>&1 | grep -E '(icmp_[s|r]eq.*time|unknown host|Unknown host|not supported)' 2>/dev/null |");
$ping = ;

-if (($ping =~ 'unknown host') || ($ping =~ 'Unknown host') || ($ping =~ 'not supported') || ($ping =~ 'Name or service not known')) {
+if (($ping =~ 'unknown host') || ($ping =~ 'Unknown host') || ($ping =~ 'not supported')) {
if ((-f '/bin/ping6') || (-f '/sbin/ping6')) {
open(PROCESS, "ping6 -c 1 $host 2>&1 | grep 'icmp_[s|r]eq.*time' 2>/dev/null |");
$ping = ;

cigamit added a commit that referenced this issue Nov 4, 2017
ICMP Ping to and IPv6 address fails to gather data for Ping Latency /
CentOS 7.4
Copy link

cigamit commented Nov 4, 2017

Thanks for taking time to report. Will be resolved in 1.2.28. Again thanks!

@cigamit cigamit closed this as completed Nov 4, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
None yet

No branches or pull requests

2 participants