Versions Compared

Old Version 153

changes.mady.by.user Les Cottrell

Saved on

compared with

New Version Current

changes.mady.by.user Les Cottrell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • TimePing:** /afs/slac/package/pinger/timeping.pl
    • Represents the old script to perform ping measurements and store raw data.

    • a caode.Stores raw data on nfs at:

      Code Block
      /nfs/slac/g/net/pinger/pinger_mon_data/ping-<YYYY>-<MM>.txt

    • The following files were moved from /nfs/slac/g/net/pinger/pinger_mon_data to /nfs/slac/g/net/pinger/pingerdata/hep/data.unite/pinger_mon_data:

      Code Block
      -rw-rw-r-- 1 pinger iepm      3271 Sep 28  2006 countries.txt
-rw-r--r-- 1 pinger iepm   5149872 Jan  3  2013 gl-2008
-rw-r--r-- 1 pinger iepm   1211063 Apr  1  2010 ping-1970-01.txt
-rw-rw-r-- 1 pinger iepm  99615499 Jan 31  2005 ping-2005-01.txt
-rw-r--r-- 1 pinger iepm 138793772 Feb 28  2005 ping-2005-02.txt
-rw-r--r-- 1 pinger iepm 158497470 Mar 31  2005 ping-2005-03.txt
...
-rw-r--r-- 1 pinger iepm 295723517 Mar 31  2010 ping-2010-03.txt
-rw-r--r-- 1 pinger iepm  32801520 Apr  4  2010 ping-2010-04.txt
-rw-rw-r-- 1 pinger iepm    126894 Sep 28  2006 pingtable.txt

       

  • PingER2:
    • /afs/slac/package/pinger/pinger2/share/pinger/pinger2.pl: is  the new/current tool to perform ping measurements and store raw data. 
      • At SLAC pinger2.pl is called by /afs/slac.stanford.edu/package/pinger/pinger2/share/pinger/pinger_startup.pl
        This is to check that all is well (pinger2.pl exists, pinger.xml exists and pinger2.pl is not already/still running).
        It executes:

        /usr/bin/perl  /afs/slac/package/pinger/pinger2/share/pinger/pinger2.pl >/afs/slac/package/pinger/pinger2/share/pinger/pingerCronStat.stdout

        Look at /afs/slac/package/pinger/pinger2/share/pinger/pingerCronStat.stdout to see how it is doing.
      • It appends the measurements to a file of the form (also see below):

        • /nfs/slac/g/net/pinger/pinger2/data/ping-<yyyy>-<mm>.txt with records looking like:

        • pinger.slac.stanford.edu 134.79.104.80 www.sonabel.bf 212.52.147.202 100 1693526406 10 10 248.170 254.193 266.091 1 2 3 4 5 6 7 8 9 10 256 250 266 255 252 257 248 252 249 253

        • One can use https://www.epochconverter.com/ to translate the epoch time (e.g. in the above 1693526406) to GMT.
      • It "use"'s 

        useXML::Simple;
        useData::Dumper;
        useFcntl;
        useFile::stat;
        useNet::Domain qw(hostname hostfqdn hostdomain);

      • Since it is run under perl, it shows up in top as:

        Code Block
           PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND                         
 15038 pinger    20   0 3769872   3.5g  11604 R  5.8  7.3 231:43.85 perl                            
112054 ytl       20   0  202832  10032   1372 S  0.1  0.0   8:52.46 sshd
    • See http://confluence.slac.stanford.edu/display/IEPM/PingER2+at+SLAC]

    • At SLAC stores raw data on nfs at:

      Code Block
      /nfs/slac/g/net/pinger/pinger2/data/ping-<YYYY>-<MM>.txt
e.g.
/nfs/slac/g/net/pinger/pinger2/data/ping-2021-08.txt
lines aree of the form:
pinger.slac.stanford.edu 134.79.104.80 www.alief.dz 194.163.133.136 100 1627776002 10 10 148.694 149.496 152.268 1 2 3 4 5 6 7 8 9 10 148 152 148 150 148 148 151 148 148 148

      This file is opened and written to for each set of pings in pingers.pl via the sub log_it in pinger2.pl.  Failure to access the file will result in the following message example in the CronStat.stderr file:

      Code Block
      Wed Sep  8 17:09:03 2021 Can't open PINGDATA /afs/slac/package/pinger/pinger2/share/pinger/ping-2021-09.txt: No such file or directory
    • At SLAC:
  • Ping_Data
  • getdata_all.pl  [-h  monitoring_hostname] [-d days_ago] [-s start_date] [-e end_date] 
  •  getdata.pl
    • /afs/slac/package/pinger/getdata.pl
    • Typically called from /afs/slac/package/pinger/getdata_all.pl

    • Typical debug call:

    • queries ping_data.pl http://slac.stanford.edu/cgi-bin/ping_data.pl to fetch data (e.g. from  /nfs/slac/g/net/pinger/pinger2/data)
    • uses wget calls of the form:
    • Writes files of the form: 

      /nfs/slac/g/net/pinger/pingerdata/hep/data/pinger.slac.stanford.edu/ping-2023-09-03.txt.gz

    • Since 2004 it stores old files as zipped File at

      Code Block
      /nfs/slac/g/net/pinger/pingerdata/hep/data/<host>/ping-<YYYY>-<MM>-<DD>.txt.gz
e.g.
/nfs/slac/g/net/pinger/pingerdata/hep/data/pinger.slac.stanford.edu/ping-2022-11-23.txt.gz
/nfs/slac/g/net/pinger/pingerdata/hep/data/pcgiga.cern.ch/ping-2006-09-28.txt.gz
/nfs/slac/g/net/pinger/pingerdata/hep/data/2001:da8:270:2018:f816:3eff:fef3:bd3/ping-2018-09-09.txt.gz
or 
[pinger@pinger ~]$ ls -l /nfs/slac/g/net/pinger/pingerdata/hep/data/pinger.slac.stanford.edu/ping-2022-11-23.txt.gz
-rw-rw-r--. 1 pinger iepm 2720699 Nov 24 09:05 /nfs/slac/g/net/pinger/pingerdata/hep/data/pinger.slac.stanford.edu/ping-2022-11-23.txt.gz

      At the Measurement Agents (MAs) it is typically stored at: /usr/local/share/pinger/data

    • There is also a wrapper to get data from multiple days. It is at /afs/slac/package/pinger/getdata_all.pl
    • See Restoring PingER data for more details.

    • Data from 1997-2003 can be found in /nfs/slac/g/net/pinger/pingerdata/. The files are zipped and compressed and contain the gathered data for 100 and 1000 byte pings for each day for all monitors.

      Code Block
      157cottrell@pinger:~$ls -l /nfs/slac/g/net/pinger/pingerdata/
total 11
drwxrwsr-x  2   6995 iepm  512 Dec  2  2011 1997/
drwxrwsr-x  2   6995 iepm 1024 Jan 25  2005 1998/
drwxrwsr-x  2   6995 iepm 1024 Jan 25  2005 1999/
drwxrwsr-x  2   6995 iepm 1024 Aug  3  2007 2000/
drwxrwsr-x  2   6995 iepm  512 Jan 25  2005 2001/
drwxrwsr-x  2   6995 iepm  512 Jan 25  2005 2002/
drwxrwsr-x 38   6995 iepm 1536 Feb  8  2007 2003/
drwxrwsr-x  6 iepm   iepm  512 Jul 20 15:19 hep/
drwxrwsr-x  3 pinger iepm  512 Mar  8  2012 new/
drwxrwsr-x  4   6995 iepm  512 Jan 25  2005 oldftp/
158cottrell@pinger:~$ls -l /nfs/slac/g/net/pinger/pingerdata/2002/
total 3844288
-rw-r--r-- 1 6995 iepm 349112320 Jan 25  2005 data-2002-01.tar
-rw-r--r-- 1 6995 iepm 316467200 Jan 25  2005 data-2002-02.tar
-rw-r--r-- 1 6995 iepm 332656640 Jan 25  2005 data-2002-03.tar
-rw-r--r-- 1 6995 iepm 326103040 Jan 25  2005 data-2002-04.tar
-rw-r--r-- 1 6995 iepm 347064320 Jan 25  2005 data-2002-05.tar
-rw-r--r-- 1 6995 iepm 324648960 Jan 25  2005 data-2002-06.tar
-rw-r--r-- 1 6995 iepm 319150080 Jan 25  2005 data-2002-07.tar
-rw-r--r-- 1 6995 iepm 320245760 Jan 25  2005 data-2002-08.tar
-rw-r--r-- 1 6995 iepm 336117760 Jan 25  2005 data-2002-09.tar
-rw-r--r-- 1 6995 iepm 335669760 Jan 25  2005 data-2002-10.tar
-rw-r--r-- 1 6995 iepm 303858176 Jan 25  2005 data-2002-11.tar
-rw-r--r-- 1 6995 iepm 323323904 Jan 25  2005 data-2002-12.tar
168cottrell@pinger:~$cp /nfs/slac/g/net/pinger/pingerdata/2002/data-2002-01.tar /nfs/slac/g/net/pinger/pingerdata/hep/data.unite/
$cd /nfs/slac/g/net/pinger/pingerdata/hep/data.unite/ 
$tar -xvf /nfs/slac/g/net/pinger/pingerdata/hep/data.unite/data-2002-01.tar
cache01.ansp.br/ping-2002-01-01.txt.gz
cache01.ansp.br/ping-2002-01-02.txt.gz
...
yumj2.kek.jp/ping-2002-01-30.txt.gz
yumj2.kek.jp/ping-2002-01-31.txt.gz
182cottrell@pinger:/nfs/slac/g/net/pinger/pingerdata/hep/data.unite$ls
172.23.52.7/                  monitor.seecs.edu.pk/                pinger.cdacmumbai.in/       pingerlhr-pu.pern.edu.pk/
aup.seecs.edu.pk/             moore.ece.rice.edu/                  pinger.cemb.edu.pk/         pingerpwr.pern.edu.pk/
...
177cottrell@pinger:/nfs/slac/g/net/pinger/pingerdata/hep/data.unite$cp yumj2.kek.jp/ping-2002-01-31.txt.gz /tmp/
178cottrell@pinger:/nfs/slac/g/net/pinger/pingerdata/hep/data.unite$gunzip /tmp/ping-2002-01-31.txt.gz
180cottrell@pinger:/nfs/slac/g/net/pinger/pingerdata/hep/data.unite$tail /tmp/ping-2002-01-31.txt
yumj2.kek.jp 130.87.34.37 ultra.edu.uy 164.73.128.70 100 1012520610 10 10 379.815 381.366 384.206 0 1 2 3 4 5 6 7 8 9 380.758 380.938 382.205 380.480 380.878 384.206 379.815 381.087 382.547 380.743
yumj2.kek.jp 130.87.34.37 frcu.eun.eg 193.227.1.1 100 1012520610 10 10 364.870 399.626 446.021 0 1 2 3 4 5 6 7 8 9 398.877 395.008 388.069 396.147 416.314 392.862 398.349 399.744 364.870 446.021

      Note that after the above, the raw input data to  wrap-analyze-hourly.pl (see below) for 1998..2003 comes from /nfs/slac/g/net/pinger/pingerdata/hep/data.unite/ rather than /nfs/slac/g/net/pinger/pingerdata/hep/data/.  

      • There is a script /afs/slac/package/pinger/pre2004.pl that will take the data in /nfs/slac/g/net/pinger/pingerdata/<1998..2003> copy it, unzip, and untar into /nfs/slac/g/net/pinger/pingerdata/hep/data.unite/.   

      • There is a second script  /afs/slac/package/pinger/pre2004-hourly.pl that using /afs/slac/package/pinger/analysis/analyze-all.pl reads the raw data from /afs/slac/g/net/pinger/pingerdata/hep/data.unite/ and analyzes and stores the hourly data for the selected years.

  • Unite-monthly

    • There is a script /afs/slac/package/pinger/unite-monthly.pl that unites all the raw data for a month into a single file of the form /nfs/slac/g/net/pinger/pingerdata/hep/data/<host>/ping-<YYYY>-<MM>.txt. It is run from a trscronjob at 4:00am each morning.

    • The files appear as:


      Code Block
      [pinger@cent7a ~]$ ls -l /nfs/slac/g/net/pinger/pingerdata/hep/data/pinger.slac.stanford.edu/ping-2023-06-03.txt.gz
-rw-rw-r--. 1 pinger iepm 3216199 Jun  4 12:47 /nfs/slac/g/net/pinger/pingerdata/hep/data/pinger.slac.stanford.edu/ping-2023-06-03.txt.gz

    • The output data appears as:

      Code Block
      cottrell@pinger $ head /nfs/slac/g/net/pinger/pingerdata/hep/data/pinger.slac.stanford.edu/ping-2020-03.txt
pinger.slac.stanford.edu 134.79.104.80 www.alief.dz 91.121.45.149 100 1583020804 10 10 149.672 149.979 150.649 1 2 3 4 5 6 7 8 9 10 149 149 150 150 149 149 150 149 149 149
pinger.slac.stanford.edu 134.79.104.80 www.ons.dz 196.20.66.100 100 1583020805 10 10 193.218 193.371 193.576 1 2 3 4 5 6 7 8 9 10 193 193 193 193 193 193 193 193 193 193
[pinger@pinger ~]$ tail /nfs/slac/g/net/pinger/pingerdata/hep/data/pinger.slac.stanford.edu/ping-2022-11.txt
pinger.slac.stanford.edu 134.79.104.80 mail.neda.af 117.55.192.5 1000 1669247047 11 10 310.965 311.160 311.281 1 2 3 4 5 6 8 9 10 11 311 311 311 311 311 311 311 310 311 311
...
Where for example you can use https://www.epochconverter.com/ to find that the epoch time 1669247047 was equivalent to
GMT: Wednesday, November 23, 2022 11:44:07 PM

The timestamp on the file appears as:
[pinger@cent7a ~]$ ls -l /nfs/slac/g/net/pinger/pingerdata/hep/data/pinger.slac.stanford.edu/ping-2023-06.txt
-rw-rw-r--. 1 pinger iepm 68740320 Jun  4 04:00 /nfs/slac/g/net/pinger/pingerdata/hep/data/pinger.slac.stanford.edu/ping-2023-06.txt
where the date is todays date at 4:00am
  • Data formats for timeping.pl, pinger2.pl, ping_data.pl, getdata.pl and getdata_all.pl
  • Check the data has been gathered:
    • /afs/slac/package/pinger/checkdata_gif.pl calls /afs/slac/package/pinger/checkdata.pl to see if there is gathered data, and then writes out a summary web page to http://www-iepm.slac.stanford.edu/monitoring/checkdata/
    • You can manually run /afs/slac/package/pinger/checkdata.pl for a particular date with debugging

      • [pinger@cent7a ~]$ perl -d  ~cottrell/bin/checkdata.pl 2023-06-03 2 #Check whether data for 2023-06-03 is present with debug set to 2.

  • Analyze
    • There is a group of analysis scripts, that pick up zipped data; do their analysis, aggregate data and prepare web reports.
      • Note that to be included in the analyzed data the host must be in NODEDETAILS.

    • The first script to be executed is wrap-analyze-hourly.pl (which is executed by calling the wrapper analyze-all.pl --date 1days from the trscronjob) which takes as input data the output of getdata.pl (raw data) and from this aggregates the data to by day and writes the latest  to the /nfs/slac/g/net/pinger/pingerreports/hep/<metric>/ directory with the file name <metric><size><by><yyyy><mm>-<dd>.txt.X., this is referred to as the hourly analyzed data. The wrap-analyze-hourly.pl script is run daily from the trscrontab on pinger and by default analyzes the data gathered for yesterday. 

    • Example of analyze-all.pl

      Code Block
      [pinger@pinger ~]$ ~cottrell/bin/analyze-all.pl  --date 2023-08-01 1 #analyze the 
Sat Aug 12 11:44:42 2023(0s so far) executing /afs/slac/package/pinger/analysis/wrap-analyze-hourly.pl  --basedir /nfs/slac/g/net/pinger --usemetric --dataset hep --debug 0  --datadir /nfs/slac/g/net/pinger/pingerdata/hep/data --size 100 --by by-node --date 2023-08-01  --set_metric 4
...
Sat Aug 12 11:44:43 2023: wrap-analyze-hourly.pl unzipped(debug=0, size=100, by=by-node, 1s so far) (85/229)16532 lines from /nfs/slac/g/net/pinger/pingerdata/hep/data/ping.desy.de/ping-2023-08-01.txt.gz
Read 16532 lines for $monitoring_site ping.desy.de: found 8218 valid lines,  0 corrupted lines & 140 alpha>1.1 lines
... for each metric 
wrap-analyze-hourly.pl opening metric=maximum_rtt (16/1) for write to /nfs/slac/g/net/pinger/pingerreports/hep/maximum_rtt/maximum_rtt-100-by-node-2023-08-01.txt
Wrote 1955 lines to /nfs/slac/g/net/pinger/pingerreports/hep/maximum_rtt/maximum_rtt-100-by-node-2023-08-01.txt.gz
... new value of --by (--by node, --by site) also will be --size 100, and --size 1000
Sat Aug 12 11:49:33 2023: wrap-analyze-hourly.pl unzipped(debug=0, size=100, by=by-site, 0s so far) (85/229)16532 lines from /nfs/slac/g/net/pinger/pingerdata/hep/data/ping.desy.de/ping-2023-08-01.txt.gz
... Both -by site and --size 1000
wrap-analyze-hourly.pl opening metric=minimum_rtt (16/2) for write to /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-1000-by-site-2023-08-05.txt
Wrote 851 lines to /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-1000-by-site-2023-08-05.txt.gz


      The file names appear as:

      Code Block
      /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2006-09-28.txt.gz

      You can test whether the latest data is there (e.g. say today is 6/4/2023) 

      Code Block
      [cottrell@pinger ~]$ date
Sun Jun  4 16:32:37 PDT 2023
[cottrell@pinger ~]$ ls -l /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2023-06-*.txt.gz
-rw-rw-r--. 1 pinger iepm 153081 Jun  2 02:58 /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2023-06-01.txt.gz
-rw-rw-r--. 1 pinger iepm 154116 Jun  3 02:58 /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2023-06-02.txt.gz
i.e. the 2003-06-03 data is missing.

      The output appears as:

      Code Block
      cottrell@pinger $ cp /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2006-09-28.txt.gz /tmp/
cottrell@pinger $ zcat /tmp/minimum_rtt-100-by-node-2006-09-28.txt.gz
cottrell@pinger $ head /tmp/minimum_rtt-100-by-node-2006-09-28.txt 
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 
pinger.slac.stanford.edu manila.global.net.pg 547.877 548.021 547.934 548.611 548.680 548.069 549.023 548.124 548.687 547.573 548.639 549.181 547.998 548.302 547.858 547.464 548.470 548.251 547.849 547.708 548.463 547.473 547.651 547.732 pinger.slac.stanford.edu manila.global.net.pg
pinger.slac.stanford.edu lobelia.physics.wisc.edu 61.089 60.958 61.037 61.332 60.958 61.262 61.073 61.093 61.040 61.086 60.974 60.979 60.956 61.070 60.942 61.035 61.994 61.022 60.927 60.957 61.091 61.009 61.024 60.974 pinger.slac.stanford.edu lobelia.physics.wisc.edu

      By default the above file is created once thus the directory appears as:

      Code Block
      57cottrell@pinger:~>ls -l /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2011-05*
-rw-rw-r--  1 pinger   iepm 492144 May  2 02:17 /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2011-05-01.txt.gz
-rw-rw-r--  1 pinger   iepm 545968 May  3 02:17 /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2011-05-02.txt.gz
-rw-rw-r--  1 pinger   iepm 561661 May  4 02:17 /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2011-05-03.txt.gz
-rw-rw-r--  1 pinger   iepm 566550 May  5 02:17 /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2011-05-04.txt.gz
-rw-rw-r--  1 pinger   iepm 537127 May  6 02:17 /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2011-05-05.txt.gz
-rw-rw-r--  1 pinger   iepm 538830 May  7 02:17 /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2011-05-06.txt.gz
-rw-rw-r--  1 pinger   iepm 488360 May  8 02:17 /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2011-05-07.txt.gz
-rw-rw-r--  1 pinger   iepm 499020 May  9 02:17 /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2011-05-08.txt.gz
-rw-rw-r--  1 pinger   iepm 563840 May 10 02:17 /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2011-05-09.txt.gz
-rw-rw-r--  1 pinger   iepm 583454 May 11 02:17 /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2011-05-10.txt.gz
-rw-rw-r--  1 cottrell iepm 577949 May 12 22:08 /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2011-05-11.txt.gz
-rw-rw-r--  1 cottrell iepm    102 May 12 17:25 /nfs/slac/g/net/pinger/pingerreports/hep/minimum_rtt/minimum_rtt-100-by-node-2011-05-12.txt.gz

      Example output format. Following the 1st line in the file there is 1 line like the following per day/per host pair.  Between the initial and final src_name and tgt_name tokens there are 24 tokens one for each hour of the day, missing data is identified by a dot followed by a space (. ), e.g.:

      Code Block
      icfamon.dl.ac.uk lns62.lns.cornell.edu 108.871 . . . . . . . . 108.892 . . . . . . . . . . . . . 109.620 icfamon.dl.ac.uk lns62.lns.cornell.edu


      The first line in the file contains a label for each of the time slots (e.g. hours):

      Code Block
      0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23


      Example output filename for the minimum_rtt metric:

...