S800 Documentation

User Tools

Site Tools

Trace:
s800_daq_tools

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
s800_daq_tools [2017/07/17 17:35]
pereira [Troubleshooting] 		s800_daq_tools [2017/07/17 18:05]
pereira [Old processes still running]
Line 125: Line 125:
 ===== Troubleshooting ===== ===== Troubleshooting =====
 There are several common reasons why the S800 DAQ may fail. The list below describes what to do to fix some of these problems. There are several common reasons why the S800 DAQ may fail. The list below describes what to do to fix some of these problems.
-  * [[#Old processes still running]]    +  * [[#Old processes still running|Error message "Socket ID already in use"]]    
-  * [[#No data sources defined]]+  * [[#No data sources defined|Error message "No data sources are running so a run cannot be started"]]
   * [[#CCUSB and/or VMUSB claimed by existing programs]]   * [[#CCUSB and/or VMUSB claimed by existing programs]]
   * [[#Manual rebooting]]   * [[#Manual rebooting]]
Line 133: Line 133:
  
 ==== Old processes still running ==== ==== 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'' in Readout GUI), the system sends an error message complaining about one of these processes still running. If you find yourself in this situation try:   +Sometimes, particularly if the S800 DAQ session ended in an uncontrolled way (e.g. you tried to "kill" it), 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'' in Readout GUI), the system sends an error message complaining about one of these processes still running (for instance "Socket ID already in use"). If you find yourself in this situation try:   
-      - Exit your Readout GUI properly  +      - Exit your Readout GUI  
-      - On a Linux session, connect to spdaq19 by typing ''ssh -Y s800@spdaq19'' (the S800 password can be found in the S800 binder that is kept in the data-U1 logbook cabinet) +      - On a Linux session, connect to the S800 spdaq by typing ''ssh -Y s800@spdaqXX'' (Contact the Device Physicist to get the spdaq number XX and S800 password) 
-      - Type ''ps aux | grep Readout'' to ensure that Readout is indeed not running+      - Type ''ps aux | grep Readout'' to ensure that Readout is indeed not running. If "Readout" is still running, use ''kill -9 PID'', where PID identifies the Readout process ID 
       - Type ''/usr/opt/nscldaq/xxxx/bin/ringbuffer status'', where xxxx is the daq version, e.g. 11.0-020       - 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)       - 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)
s800_daq_tools.txt · Last modified: 2023/10/19 17:25 by swartzj

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
CC Attribution-Noncommercial-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki