...
- Currently it does not respond to ping pingerqta.pern.edu.pk
271cottrell@pinger:~$ping pingerqta.pern.edu.pk
ping: unknown host pingerqta.pern.edu.pk[cottrell@pinger ~]$ nslookup pingerqta.pern.edu.pk
272cottrell@pinger:~$nslookup pingerqta.pern.edu.pk
Server: 134.79.111.111
Address: 134.79.111.111#53** server can't find pingerqta.pern.edu.pk: NXDOMAIN
274cottrell@pinger:~$ping 121.52.157.157
PING 121.52.157.157 (121.52.157.157) 56(84) bytes of data.
^C
--- 121.52.157.157 ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 5625ms- http://121.52.157.148, responds with the default Apache web page
- http://121.52.157.148//cgi-bin/ping_data.pl? responds (albeit very slowly) with Get Ping Data from sharedw228.b2bhosting.net Also there is data.
- This is a funny hostname. It comes from the system response to the perl commands:
use Net::Domain qw(hostname hostfqdn hostdomain);
my $hostname = hostfqdn();
- This is a funny hostname. It comes from the system response to the perl commands:
- The following needs to reflect the new IP address at 121.52.157.148. It is very easy to change the IP address once the Measurement Agent is up and running and responding, in fact the PingER meta data at SLAC was changed in February 2015. However the DNS still points to:
Output from: /bin/cat /etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost 121.52.157.157 pingerqta.pern.edu.pk
Also asked for an update on the following:
As of 7/30/2016 the following hosts are down and not responsive for >= 1 month. Anas Abrar reports the nodes were contacted many times for identifying their issues. i.e turn on their pinGER Computers but never responded well. Some have already been Disabled, (striketroughs as proposed at the 6/22/2016 meeting and hearing nothing from Pakistan following the meeting), I will disable the others if I hear nothing.
...