...
Email 6/15/2016 to Fitzi, pinger.fsksm.utm.my is down.
NUST
Emailed Dr Hassaan 6/15/2016 asking for update and 6/18/2016.
Dr Hassaan Khaliq contacted and said "We shall look into the issues with them" 5/13/2016.
Last update 4/6/2016.
Hassaan's student (Mian Anas Abrar <anas.abrar@gmail.com>) reports: "Sir haven't disabled any of them which i told earlier and actually can't even get back to them because of their wrong contact numbers or their numbers not responding since then. I have tried contacting Dr.Les earlier few time as per your instructions but don't know why i wasn't able to email him. rest the status is actually same nodes being down". We believe we have solved the mail problem.
We are unable to gather data from the following Pakistani PingER monitors:
...
- Currently it does not respond to ping pingerqta.pern.edu.pk
- Ping 121.52.157.148, responds
- http://121.52.157.148/ Apache responds. http://121.52.157.148//cgi-bin/ping_data.pl? responds (albeit very slowly) with Get Ping Data from sharedw228.b2bhosting.net
- 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:
- Also there is data.
- The following needs to reflect the new IP address at 121.52.157.148
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
- 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. Howeer the DNS still points to:
[cottrell@pinger ~]$ nslookup pingerqta.pern.edu.pk
Server: 134.79.111.111
Address: 134.79.111.111#53
Non-authoritative answer:
Name: pingerqta.pern.edu.pk
Address: 121.52.157.157
Following hosts are down and not responsive. Nodes were contacted many times for identifying their issues. i.e turn on their pinGER Computers but never responded well.
- aup.seecs.edu.pk #AUP said that they will look intothe issue in a while everytime I ask them or give them the reminder. Does not ping
- cae.seecs.edu.pk #Does not ping
- kinniard.seecs.edu.pk+ #Unknown host
- maggie1.seecs.edu.pk # Ping responds with Time to live exceeded
- maggie2.seecs.edu.pk #Does not ping
- npm.neduet.edu.pk* # Not pingable
- pinger.uettaxila.edu.pk* #UET taxila are not receiving the provided Number, Unknown host.
- pingerisl-qau.pern.edu.pk* #number is not responding for QUA. Not pingable
- quest.seecs.edu.pk* #Quest are not receiving my Call now. Not pingable
- pingerlhr-pu.pern.edu.pk* #Site pings via http://www-wanmon.slac.stanford.edu/cgi-bin/nph-traceroute.pl?target=pingerlhr-pu.pern.edu.pk&function=ping, however http://pingerlhr-pu.pern.edu.pk/cgi-bin/ping_data.pl? gives site can't be reached.
- pingerpwr.pern.edu.pk* # Site pings via http://www-wanmon.slac.stanford.edu/cgi-bin/nph-traceroute.pl?target=pingerpwr.pern.edu.pk&function=ping however the configuration file /usr/local/share/pinger/pinger.xml is truncated, see FAQ for how to go about fixing.
...
...
- :1313/cgi-bin/ping_data.pl? gives site can't be reached and http://pinger.iba-suk.edu.pk
...
- /cgi-bin/ping_data.pl? takes me to a generic site for iba-suk.
- pinger.isra.edu.pk # Site can't be pingerd via http://www-wanmon.slac.stanford.edu/cgi-bin/nph-traceroute.pl?target=pinger.isra.edu.pk&function=ping
...
* This host was noted at the 3/9/2016 meeting as being down for the last 30 days.
+ Not seen in June 2016
Les proposes:
- Give up (i.e. remove from Monitoring node table by setting Projecttype to D (for Disabled)) on non-responsive hosts not working since 3/9/2016.
- I would not oppose extending thsi to all non-responsive, non-working hosts.
- Focus on the close to working hosts
Strikethrough working again in June
PingER at SLAC
Working on the following hosts to be able to gather data
...