-
Notifications
You must be signed in to change notification settings - Fork 7
How to restart the DAQ status monitor in DCS summary page
If the DAQ status info in the DCS summary page does not update anymore (see the timestamp) it means that the script collecting these information has crashed. Since these info are of primary importance for the shifters (specially if remote ...) these are updated every ~ 30 secs in the summary page and should always be updated
To get ALL the informations needed the script HAS to run from daq@l0padme3
You can restart it by going to the RecoMonitor folder and doing the following :
nohup ./control_merger_2020.sh > /dev/null
to avoid cluttering the terminal and/or a log file with a lot of info
The general summary page of the dcs in the monitoring updates every ~30' showing :
-
timestamp in the header (check if it's the updated local time !)
-
current run
-
merger node
-
setup used
-
run type
-
free disk space on l1padme1 (orange if occupied space > 60% - red if occupied space > 80%)
-
free disk space on l1padme2 (orange if occupied space > 60% - red if occupied space > 80%)
-
free DAQ disk space (orange if occupied space > 60% - red if occupied space > 80%)
-
last daq file
-
last reco file
-
if the recorun online is running and its process id on l0padme3
-
if the recomonitor is running and its process id on l0padme3
-
if the trend job is running and its process id on l0padme3
-
the last taken trigger event
-
the last taken merger event
==> of course these 2 last info will be invalid and show strange things at run start and run end
-
the toal size in GB of the last run data files and the total number of files written by ALL streams
The previously shown info on beam collimators-slits and trigger timimg are now available under the dcs/beam/BTF_beam page
© 2015 PADME Collaboration