Local Emu DAQ Troubleshooting
- emuFarmer failed
-
Make sure that you issue emuFarmer in the same shell that you did source emuPass in. The pass is valid for that single shell only.
- no local DAQ page
-
EmuDAQManager may have died or not been started. Check the DAQ farm's processes as described in the manual, and (re)launch them.
- run number not booked
-
The run database may be down or inaccessible. Please notify the local DAQ expert.
Unfortunately this also means that no entry will be posted automatically to eLog either, so you will have to post a run summary yourself.
- DAQ configuration failed
-
If the state of any of the applications is 'UNKNOWN', it has very likely died. Check the DAQ and DQM farms' processes as described in the manual, and (re)launch them.
If any of the DAQ applications 'Failed', click Stop and then Reset. Try to configure again. If it fails again, check the log window or file for FATAL messages and call the expert.
- DAQ start failed
-
If the state of any of the applications is 'UNKNOWN', it has very likely died. Check the DAQ and DQM farms' processes as described in the manual, and (re)launch them.
If any of the DAQ applications 'Failed', click Stop and then Reset. Try to configure again. If it fails again, check the log window or file for FATAL messages and call the expert.
- counters not incrementing
-
This may occur for several reasons:
- We are getting no trigger.
- Hardware is not configured properly or failed.
- The Gbit Ethernet drivers need (re)loading. Stop the run first. Kill the farm's processes by emuFarmer -a stop, reload the drivers by emuFarmer -a reload, and launch the processes again by emuFarmer -a start.
- DAQ stop failed
-
-
If the processes remain green, please wait for them. Sometimes it's hard to interrupt the readout, especially when it's starved of data (idle looping).
-
If the state of any of the applications is 'UNKNOWN', it has very likely died. Check the DAQ and DQM farms' processes as described in the manual, and (re)launch them.
If any of the DAQ applications 'Failed', click Stop and then Reset. Try to configure again. If it fails again, check the log window or file for FATAL messages and call the expert.
-