This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
s800_daq_tools [2016/02/29 11:51] pereira [Readout GUI tab] |
s800_daq_tools [2016/02/29 11:52] pereira [Eventbuilder tab] |
||
---|---|---|---|
Line 94: | Line 94: | ||
==== Troubleshooting ==== | ==== Troubleshooting ==== | ||
In the rare case that the RunControl GUI gets " | In the rare case that the RunControl GUI gets " | ||
- | |||
- | |||
- | ==== Eventbuilder tab ==== | ||
- | The communications port to the eventbuilder is tcp:8100 and it runs by default on spdaq48. These options can be changed in a manner identical to the Readout GUI tab. Information about the current statistics (input/ | ||
- | |||
- | {{: | ||
- | |||
- | This is the only information available to the tcp protocol, but the pid of the processes responsible for these connections can be investigated by using the following commands: | ||
- | |||
- | 1. For each remote host, log in as each user which may be connected to the DAQ (ie e11007, s800). Unfortunately, | ||
- | |||
- | 2. Do **lsof -i | grep port** (where port is replaced by the local port information obtained from the status gui. This will look similar to: | ||
- | |||
- | < | ||
- | netcat.tc 2498 e11007 | ||
- | </ | ||
- | |||
- | where the second column shows the PID of the connecting process. In this case the pid is 2498. | ||
- | |||
- | 3. Do **ps -aux | grep PID**. This will look similar to: | ||
- | |||
- | |||
- | < | ||
- | e11007 | ||
- | </ | ||
- | |||
- | which gives the program name associated with the PID that is connecting to the eventbuilder. | ||
- | |||
- | If the eventbuilder is hanging, which is evidenced by non-increasing statistics and no data/ | ||