SSB scripts
The following scripts are used to generate information for the Site Status Board.
site_avail_sum.pl
and
jr_successrate.pl
can be found at
SSBScripts
(for the rest:
SSBScripts@git.cern
)
Note: an RFC proxy is generated adding
-rfc
to the voms-proxy-init command.
Detailed description
site_avail_sum.pl
This script is used for the Site Readiness, to calculate the SAM availability of the previous day. The time range used to extract the numerical values and generate the URLs is [day-1 00:00, day 00:00] in UTC time, where
day is the day when the script is run.
- It is recommended to run the script at 2:10 local time to ensure that it is run after 00:00 UTC even during daylight saving time.
If the outfile is not given, it defaults to /afs/cern.ch/cms/LCG/SiteComm/site_avail_sum.txt, which is the path used by the Site Status Board (it can be changed in the SSB column configuration).
If it is run on SLC6, it has no special dependencies. On SL5, the JSON.pm module should be installed.
The typical cron job should look like
10 2 * * * (/data/cmssst/MonitoringScripts/init.sh && perl /data/cmssst/MonitoringScripts/SiteComm/SSBScripts/site_avail_sum.pl /afs/cern.ch/user/c/cmssst/www/ssb/site_avail_sum.txt)
In Central European Summer Time (CEST), unless it is possible to use UTC for cron jobs.
CEST = UTC +2
CET = UTC +1
jr_successrate.pl
This script is used for the Site Readiness, to calculate the HammerCloud jobs success rate. It allows to calculate it for the past N hours (the default is 24, which is what is needed by the Site Readiness). As time ranges are given up to seconds, there is no special need to run it before 00:00 UTC but it should still be run within minutes of that time because the Site Readiness metrics refer to whole days. The activity must be
hctest, which for historical reasons corresponds to glidein HC jobs.
If the outfile is not given, it defaults to /afs/cern.ch/cms/LCG/SiteComm/successrate_<activity>.txt, which is the path used by the Site Status Board (it can be changed in the SSB column configuration).
If it is run on SLC6, it has no special dependencies. On SL5, the JSON.pm module should be installed.
The typical cron job should look like
55 0 * * * (/data/cmssst/MonitoringScripts/init.sh && perl /data/cmssst/MonitoringScripts/SiteComm/SSBScripts/jr_successrate.pl hctest /afs/cern.ch/user/c/cmssst/www/ssb/successrate_hctest.txt 24)
55 * * * * (/data/cmssst/MonitoringScripts/init.sh && perl /data/cmssst/MonitoringScripts/SiteComm/SSBScripts/jr_successrate.pl hctest /afs/cern.ch/user/c/cmssst/www/ssb/successrate_hctest6.txt 6)
In Central European Summer Time (CEST), unless it is possible to use UTC for cron jobs.
- During winter time (CET) this requires to change the execution time to 55 0. This has been a frequent source of problems in the past.
CEST = UTC +2
CET = UTC +1
The first cron is for the Site Readiness, while the second cron job is to generate the information for the default view of the SSB.
cms-storage-info.pl
This script is used to feed the
'storage'
view of the SSB with information taken from PhEDEx and the BDII. It is hard coded to write its output to files in /afs/cern.ch/cms/LCG/SiteComm/.