...
We wanted to verify whether the sharing cretaed created by running on a virtual machine made any statistical difference to the PingER results. Thus we compare the results from PinGER running on a bare metal machine (pinger.slac.stanford.edu) vs running on a VM.
...
- Follow the instructions at: Installation Overview
- Then
Verify installation
- To see if the cronjob is running look at the dates on the files /usr/local/share/pinger/pingerCronStat.stdout and /usr/local/share/pinger/pingerCronStat.stderr, they should be withing the last 30 mins (example)
- Examine the above files (in particular the stderr file) to verify pinger2.pl is properly configured (an example of a typical error in the stderr file). If all is well then the stderr file will be empty. Example of a normal stdout file.
...
These are CGI scripts to enable a reverse traceroute and ping server (traceroute.pl), and to enable the gathering of data (ping_data.pl) from the archive sites. The two scripts were installed in the standard CGI script location /var/www/cgi-bin as defined in /etc/httpd/conf/http.conf. They are accessible from within SLAC as: http://dhcp-nebula-124-66.slac.stanford.edu/cgi-bin/ping_data.pl and http://dhcp-nebula-124-66.slac.stanford.edu/cgi-bin/traceroute.pl. Since they are on port 80 there is no access to the web server from offiste.