...
NUST: (No update 1/15/2019)
Unable to gather data from maggie1.seecs.edu.pk and monitor.seecs.edu.pk. Email sent 1/26/2019.
results{maggie1.seecs.edu.pk}[0] not defined, unable to gather data for 11 consecutive days this month- results{monitor.seecs.edu.pk}[0] not defined, unable to gather data for 11 consecutive days this monthSkipping maggie1.seecs.edu.pk(3) does not ping by name or address 111.68.101.45
- Skipping monitor.seecs.edu.pk(5) does not ping by name or address 111.68.101.10
- Wajahat fixed maggie.seecs.edu.pk 2/29/2019, Les sent email 2/3/2019 to Wajahat asking about monitor1.seecs.edu.pk.
- pinger.isra.edu.pk is not pingable and unable to gather data starting 2/11/2019.
Wajahat was unable to attend but provided the following update 12/8/2018
- "We have been aggressively pursuing the three nodes(121.52.146.180 (kohat.edu.pk) down since Nov 22/2017; cae.seecs.edu.pk last time we were able to gather any data was September 2nd 2018; and pinger.isra.edu.pk no data since 5th Sept 2018, so it is a candidate to Disable). It appears to me that the participating institutes have started to lose interest in the project. Anyhow, we will keep pushing. Maybe a letter of appreciation from SLAC might rejuvenate their energies. What is your opinion?
- We also need to formulate some research problems that have the potential of appearing in some well-known places. This might help in attracting NUST students which is getting harder these days. I need your help in this regard.
UAF/GHZU (Updated 1/18/2019)
...
| Host | State | last seen | Status |
|---|---|---|---|
pingersonar-um.myren.net.my, perfsonar-usm.myren.net.my, pingersonar-utm.myrec.net.my | Unable to gather data since mid-November, unable to ping, unable to contact Fizi Jalil, so they have been Disabled. | Mid-November 2018 | Disabled |
| pinger.nwfpuet.edu.pk/cgi-bin | The hostname did not resolve from SLAC, DESY andCERN, however it does resolve from some other places. Email sent to Wajahat and to SLAC net-admin 1/12/2019. No responses, on 1/13/2019 it was fixed, no idea how. It appears that the DNS resolution is intermittently failing. Therefore Les modified getdata.pl to first try DNS and if it fails try getting the data from the IP address in the configuration file. As of 1/18/2019 it appears to be working reliably. | Started 1/7/2019 | Working again. Recovered missing data. |
| pinger.isra.edu.pk | Down, it came up Sep 2-4, 2018. It is pinging, however, all the targets are not responding after 31 tries, email sent to Wajahat 9/18/2018. As of 10/14/2018it is not pingable. Working again as of 1/5/2019. It started again1/26/2019. It does not respond to pings from SLAC but does respond to http://pinger.isra.edu.pk/cgi-bin/ping_data.pl? which is used to get the data. However, the data indicate that none of the pings respond, e.g. pinger.isra.edu.pk 121.52.154.228 pinger.fsktm.um.edu.my 103.18.2.152 100 1548633600 31 0i.e. all 31 pings fail and 0 give any response. When one tries to ping from pinger.isra.edu.pk using http://pinger.isra.edu.pk/cgi-bin/traceroute.pl?function=ping&target=www-wanmon.slac.stanford.edu&options=-i%200.2 the web page responds but all pings from isra fail. Email sent to Wajahat 1/28/2019. Started working again 1/30/2019. Stopped being pingable and unable to gather data 2/11/2019. | March 6, 2018 | Fixed 1/5/2019 Failed again starting 1/26/2019. Working again 1/30/2019 |
| maggie1.seecs.edu.pk, | results{maggie1.seecs.edu.pk}[0] not defined, unable to gather data for 11 consecutive days this month, Skipping maggie1.seecs.edu.pk(3) does not ping by name or address 111.68.101.45 Wajahat fixed 1/14/2019. Went back and gathered missing data. | 1/14/2019 | Wajahat fixed 1/29/2019. |
| monitor.seecs.edu.pk |
| 1/14/2019 | |
| pinger.fsktm.um.edu.my | Sent email to Nor Badrual Anuar 1/5/2018. Recommend replacing the pinger.xml file from the master at http://www-iepm.slac.stanford.edu/pinger/pinger.xml and editing it. Nor Badrul Anuar replied saying he will look at it. The file pinger.xml does not close the HostList with a </HostList>. Nor Badrual Anuar edited the pinger.xml file, but the problem was that the hard disk space was full. There are data files going back to 2012. Recommended he deletes all data files up through October 2018. He did this. Then the version of pinger2.pl he was using (ca. 2012) needed SrcIP to be in the pinger.xml file. He added SrcIP to pinger.xml and also updated pinger2.pl. This fixed it. Also recommended he install the data trimmer (see http://www-iepm.slac.stanford.edu/pinger/tools/install2.html) and enter it in the cronjob. | 12/28/2018 | Badrul fixed 1/30/2019. |
...