Starting the CDR service - PADME-Experiment/padme-cdr GitHub Wiki

The current data distribution schema requires 7 instances of PadmeCDR to run simultaneously:

On padmeui

  1. Copy of new files from the l1padme3 DAQ data server to the LNF Tier2 disk storage
  2. Copy of new files from the l1padme4 DAQ data server to the LNF Tier2 disk storage
  3. Copy of new files from the l0padme2 MM data server to the LNF Tier2 disk storage
  4. Copy of new files from the 192.168.60.10 TMM data server to the LNF Tier2 disk storage

On tier2-ui004

  1. Copy of DAQ new files from LNF disk storage to the CNAF tape library
  2. Copy of MM new files from LNF disk storage to the CNAF tape library
  3. Copy of TMM new files from LNF disk storage to the CNAF tape library

To start these instances you must run the following commands:

On padmeui

cd $HOME/cdr
./PadmeCDR -T DAQ -S DAQ -s l1padme3 -D LNF
./PadmeCDR -T DAQ -S DAQ -s l1padme4 -D LNF
./PadmeCDR -T MM -S DAQ -D LNF
./PadmeCDR -T TMM -S DAQ -D LNF

On tier2-ui004

cd $HOME/cdr
./PadmeCDR -T DAQ -S LNF -D CNAF
./PadmeCDR -T MM -S LNF -D CNAF
./PadmeCDR -T TMM -S LNF -D CNAF

The complete syntax of PadmeCDR is

PadmeCDR [-T data_type] [-S src_site -D dst_site] [-s data_srv] [-Y year] [-a after] [-b before] [-i] [-h]
  -T data_type    Data type to transfer ['DAQ', 'MM', 'TMM']
  -S src_site     Source site ['DAQ', 'LNF', 'CNAF', 'CNAF2']
  -D dst_site     Destination site ['LNF', 'CNAF', 'CNAF2', 'KLOE']
  -s data_srv     Data server from which data are copied ['l1padme3', 'l1padme4', 'padmesrv2']
                  N.B. -s is only used when -S is DAQ
  -Y year         Specify year of data taking to copy. Default: current year
  -a after_date   Only transfer runs collected after specified date (included). Format: yyyymmdd. Default: no limit
  -b before_date  Only transfer runs collected before specified date (included). Format: yyyymmdd. Default: no limit
  -i              Run the PadmeCDR server in interactive mode
  -h              Show this help message and exit

Each instance of PadmeCDR will append a full log of its activities to the log/PadmeCDRServer_<TYPE>_<SRC>_<DST>.log file. The log files of the seven instances are therefore:

On padmeui

log/PadmeCDRServer_DAQ_DAQ_l1padme3_LNF.log
log/PadmeCDRServer_DAQ_DAQ_l1padme4_LNF.log
log/PadmeCDRServer_MM_DAQ_l0padme2_LNF.log
log/PadmeCDRServer_TMM_DAQ_192.168.60.10_LNF.log

On tier2-ui004

log/PadmeCDRServer_DAQ_LNF_CNAF.log
log/PadmeCDRServer_MM_LNF_CNAF.log
log/PadmeCDRServer_TMM_LNF_CNAF.log

Note that these log files are updated even when the -i option is selected.

The CDR Manager should also start the CDRMonitor service which will update the CDR page on the DCS monitor system running on l0padme3. CDRMonitor can be started on padmeui from the CDR directory with the command ./CDRMonitor and will write some log information to log/CDRMonitor.log. Information will then be visible from the DCS monitor system on l0padme3:9090 at page DCS - CDR - CDR_Summary - Summary.

⚠️ **GitHub.com Fallback** ⚠️