Versions Compared

Old Version 35

changes.mady.by.user Les Cottrell

Saved on

compared with

New Version 36

changes.mady.by.user Les Cottrell

Saved on

Key

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

...

  • The copying of data to the anonymous FTP server and moving from there to the PingER raw data archive needs to complete beforegetdata.pl starts at 01:32 local time each night at SLAC
  • The data is copied from the MA to anonymous FTP incoming spaceat  thenproxyspace at  then proxy.pl, needs to be scheduled to copy the data from anonymous FTP directory to the directory accessible by the ping_data.pl CGI script.
    • This also has to complete before getdata.pl is scheduled, 
    • proxy.pl takes < 5 seconds to execute. 
    • proxy.pl is therefore currently scheduled to run at01:20amCalifornialocaltime
  • Once the move is completed by proxy.pl then getdata.pl can be scheduled to gather and save the selected data from the MAs in the PingER raw data archive at:
    /nfs/slac/g/net/pinger/pingerdata/hep/data/<host>/ping-<YYYY>-<MM>-<DD>.txt.gz
    • This (getdata.pl) takes about 15 minutes.
    • getdata.pl is scheduled to run at01:32amlocaltime.

  • The analysis of the hourly data by analyze-all.pl needs to start after getdata.pl has completed. Currentlyanalyze-all.pl starts as a cron job at 55 minutes past 2 am local time at SLAC each morning. The scheduling of the jobs at SLAC is shown below:

    20 1 * * * /afs/slac/package/pinger/proxy.pl
    32 1 * * * /afs/slac/package/pinger/getdata.pl > /afs/slac/g/www/www-iepm/pinger/slaconly/getdata.err
    55 2 * * * /afs/slac/package/pinger/analysis/analyze-all.pl --date 1days #Takes 25:1410/20/2011(55mins 9/21/2011, 70minutes 5/11/2018)

...

The CGI script ping_data.pl provides remote access to PingER information at the MA. Besides providing access to the measured data, this alos also provides validation and debugging information (e.g. logging information from execution of pinger2.pl, the pinger.xml configuration file, the version of pinger2.pl running, the pinger.pl environment at the MA etc) . However, it is not possible to access the Beijing web site (or a PingER AndroiAndroid) from outside. Thus we need a solution to provide access to the various information that ping_data.pl provides for the MA. This includes (where for example <MA domain might be unimas.my):

...

A possible way to address items 1 thru 8 for Beijing might be to copy the files to anonymous incoming FTP at SLAC on a daily basis at the same time the actual data is copied. Thus the files (updated as of the previous night) would be available for review. Since Bejing has a copy of ping_data.pl this could be used to acces access the files so they could be copied.  For the Android some new code would be needed to copy the files to SLAC. 

...