PingER and the tracerouter server were installed at Daffodil University in Bangladesh.
- http://203.190.11.4/cgi-bin/traceroute.pl works for both reverse traceroute and pin servers.
- http://203.190.11.4/cgi-bin/ping_data.pl responds with the form, however:
- The output has been modified to remove the debugging/help boxes at the top. See Difference in Daffodil and normal ping_data.pl form output
- When one gathers data (e.g. by pushing Getdata!) one gets the response:
Code Block #No data found in 0 lines of data between dates specified in /usr/local/share/pinger/data/ping-2013-09.txt. #Dates: 2013/9..2013/9. Epoch time searched from 1380240000-120 secs to 1380412740+120 secs #Results (6 lines) from /usr/bin/tail -20 /usr/local/share/pinger/data/ping-2013-09.txt are: #Pinging pinger.daffodilvarsity.edu.bd [203.190.11.4] with 32 bytes of data: #Reply from 203.190.11.4: bytes=32 time=12ms TTL=63 #Reply from 203.190.11.4: bytes=32 time=3ms TTL=63 #Reply from 203.190.11.4: bytes=32 time=8ms TTL=63 #Reply from 203.190.11.4: bytes=32 time=9ms TTL=63
...
- There was nothing in the <BeaconList></BeaconList> stanza. This is normally updated weekly by pinger2.pl accessing the beacon table at SLAC http://www-iepm.slac.stanford.edu/pinger/beacons.txt.
- <SrcName>pinger.slac.stanford.edu</SrcName> needs to be updated to <SrcName>203.190.11.4</SrcName>.
- Also the host needs to get a Domain name registration (e.g. pinger.daffodilvarsity.edu.bd>):w and that entered into the <Srcname>
- Looking at the processes running I see:
andCode Block [root@pinger pinger]# ps -efl | grep pinger 5 S avahi 6628 1 0 80 0 - 822 - Sep01 ? 00:00:41 avahi-daemon: running [pinger.local]
Code Block [root@pinger ~]# ps -efl | grep http 5 S apache 13111 16592 0 80 0 - 8046 - Sep29 ? 00:00:00 /usr/sbin/httpd 5 S apache 13112 16592 0 80 0 - 8112 - Sep29 ? 00:00:00 /usr/sbin/httpd 5 S apache 13113 16592 0 80 0 - 8079 - Sep29 ? 00:00:00 /usr/sbin/httpd 5 S apache 13114 16592 0 80 0 - 8112 - Sep29 ? 00:00:00 /usr/sbin/httpd 5 S apache 13115 16592 0 80 0 - 8079 - Sep29 ? 00:00:00 /usr/sbin/httpd 5 S apache 13116 16592 0 80 0 - 8112 - Sep29 ? 00:00:00 /usr/sbin/httpd 5 S apache 13117 16592 0 80 0 - 8079 - Sep29 ? 00:00:00 /usr/sbin/httpd 5 S apache 13120 16592 0 80 0 - 8112 - Sep29 ? 00:00:00 /usr/sbin/httpd 5 S apache 13121 16592 0 80 0 - 8079 - Sep29 ? 00:00:00 /usr/sbin/httpd 5 S root 16592 1 0 80 0 - 8046 - Sep14 ? 00:00:21 /usr/sbin/httpd
...
In addition I verified that the locations of the dig, mail and ping were correctly entered in pinger.xml.
I looked at the latest entry in /usr/local/share/pinger/data/
Code Block |
---|
[root@pinger pinger]# ls -l data/
total 32
-rw-r--r-- 1 root root 27480 Oct 1 03:54 ping-2013-09.txt
|
The update time and date were recent and there were >> 1000 bytes in the file so it looked promising. So I did a head command on the file:
Code Block |
---|
[root@pinger ~]# head /usr/local/share/pinger/data/ping-2013-09.txt
Pinging pinger.daffodilvarsity.edu.bd [203.190.11.4] with 32 bytes of data:
Reply from 203.190.11.4: bytes=32 time=12ms TTL=63
Reply from 203.190.11.4: bytes=32 time=3ms TTL=63
Reply from 203.190.11.4: bytes=32 time=8ms TTL=63
Reply from 203.190.11.4: bytes=32 time=9ms TTL=63
203.190.11.4 203.190.11.4 www.univ-sba.dz 80.249.75.2 100 1380577705 10 10 238.610 239.389 240.745 1 2 3 4 5 6 7 8 9 10 240 238 240 239 239 238 238 239 238 238
203.190.11.4 203.190.11.4 waib.gouv.bj 81.91.232.2 100 1380577707 10 10 347.761 348.693 350.187 1 2 3 4 5 6 7 8 9 10 350 348 348 347 350 347 348 349 347 348
203.190.11.4 203.190.11.4 frcu.eun.eg 193.227.1.1 100 1380577708 10 10 310.162 321.238 334.306 1 2 3 4 5 6 7 8 9 10 330 319 320 319 319 311 310 313 332 334203.190.11.4 203.190.11.4 www.stmaryuniversitycollege.edu.et 213.55.83.210 100 1380577709 10 10 410.875 417.609 422.054 1 2 3 4 5 6 7 8 9 10 417 420 417 410 414 418 420 416 422 417
|
"It's alive!"*
_________
* Mary Shelley, "Frankenstein".