...
Traceroute works as a traceroute server and a ping server
Looking at the function=ping output, you will notice that the requesting host (in this case at SLAC) is given a private IP address (10.0.253.1) which is going to cause some failures, e.g. a host at SLAC requesting a ping from 202.12.103.71 to the requesting host. The requesting host being identified as a private address 10.0.253.1 will not be able to be pinged. See below:
Update 2/17/2016
Question:
We have also been debugging the ping_data.pl which was giving us some problems. It seems that the script is unable to locate the pinger2.pl file at /afs/slac/package/pinger/pinger2/share/pinger/pinger2.pl. In our machine the script is placed in the directory /usr/local/share/pinger/pinger2.pl. Do we have to change the file path in ping_data.pl?
Response:
The easiest would be to simply comment out line 323 of ping_data.pl to remove the need to try and grep the /afs file:
my @cmds=('date',
'/bin/uname -a', '/usr/bin/uptime',
'/bin/grep "version" /usr/local/share/pinger/pinger2.pl',
#'/bin/grep "version" /afs/slac/package/pinger/pinger2/share/pinger/pinger2.pl',#line 323
'/bin/ps -efl | grep pinger2',
'/bin/cat /etc/hosts', '/bin/cat /etc/resolv.conf',
'/usr/bin/whoami', '/usr/ucb/whoami', '/bin/pwd',
'/usr/sbin/sestatus', '/bin/ps -efl | grep httpd',
#"/bin/ls -lt $stats_dir",
'/usr/bin/crontab -l', '/bin/crontab -l',
'/bin/hostname', '/bin/domainname',
);