Differences

This shows you the differences between two versions of the page.

--- s800_daq_tools [2016/02/29 13:07]
pereira [Troubleshooting]
+++ s800_daq_tools [2016/02/29 14:56]
pereira [Old processes still running]
@@ Line 88: / Line 88: @@
 ===== Troubleshooting =====
+There are several common reasons why the S800 DAQ may fails to start. The list below describes what to do to fix these problems.
+  * [[#No data sources defined]]
+  * [[#CCUSB and/or VMUSB claimed by existing programs]]
+  * [[#Manual rebooting]]
+==== Old processes still running ====
+Sometimes, particularly if the previous S800 DAQ session ended in an uncontrolled way, there may be old processes running (CCUSB and/or VMUSB and/or S800 event builder) that will prevent Readout GUI to begin a run. Whenever this happens (typically after clicking ''Begin''), the system sends an error message complaining about one of these processes still running. If you find yourself in this situation try:
+      - Make sure that you exit your Readout GUI properly
+      - Type ''ps aux | grep Readout'' to ensure that Readout is indeed not running
+      - Type ''/usr/opt/nscldaq/xxxx/bin/ringbuffer status'', where xxxx is the daq version, e.g. 11.0-020
+      - You will see a list of ringbuffers with information about their status (see figure below). Check that the producer value of each ringbuffer (see column ''producer'') is **-1**. (Don't worry about the ringbuffer **s800filter**, which is automatically killed when starting ReadoutGUI)
+      - If the producer value of a ringbuffer is not -1, take note of the PID, and kill the process by typing ''kill -9 PID''
+      - You should now be able to run Readout GUI and begin a run without problem.
+==== No data sources defined ====
+When clicking ''Begin'' in the S800 Readout GUI, you get the error message: "No data sources are running so a run cannot be started". Very likely, the setting file **.settings.tcl** is missing. On a Linux session in u6pc5, type ''ls -lisa ~/stagearea''. You should see a hidden file **.settings.tcl**. If no, try the following:
+      - Go to **/mnt/daqtesting/s800/exxxxlast**, where **exxxxlast** corresponds to the experiment number of the last (successfully) run experiment
+      - Copy the file **.settings.tcl** from that directory to the current stagearea. **NOTE**: we are assuming that the stagearea is pointing to the new experiment directory **/mnt/daqtesting/s800/exxxxnew**
+      - If you cannot find that file, there is an old version that can be copied from the directory **/user/s800/converged_daq**
+      - You should now be able to run ReadoutGUI without problem
+==== CCUSB and/or VMUSB claimed by existing programs ====
+One of the most common reasons why the S800 DAQ fails to start is because the CCUSB and/or VMUSB are claimed by existing programs. This is shown by the error messages displayed by the system. If you find yourself in this situation try the following:
+      - Log on to S800 spdaq (spdaq19 as of October 2015)
+      - Type ''ps aux | grep Readout''
+      - Use ''kill -9 PID'', where PID identifies any CCUSBReadout or VMUSBReadout processes that show up
+      - Use ''kill -9 PID'', where PID identifies any tclsh ReadoutShell process that might show up
+      - Try ''godaq'' to see if this works now
+      - If this didn't help try rebooting the S800 DAQ manually (see below)
 ==== Manual rebooting ====
 In the rare case that the RunControl GUI gets "frozen", it is possible to reboot the whole system manually. This operation requires to turn off the VME and CAMAC crates, and the spdaq computer, all them located in the rack seating near the FP box in the S3 vault. Then, the system must be turned back on in the following order. First, CAMAC crate, second VME crate, and third spdaq.

S800 Documentation

User Tools

Site Tools

Differences

Page Tools