...
Make sure that all dss nodes are selected. If you needed to take a node out due to problems, you need to edit the <hutch>.cnf file.
XPP/XCS: use "serverStat <ip>" to check if both interfaces of the node in question are up. This script will also tell you which machine has the issue.
One/both of the pings fails: use "serverStat <ip/node name> cycle" to power cycle the machine. After the script returns, continue to run "serverStat <ip/node name>" until both pings work. If you can ssh into the node, you can restart the DAQ.
Otherwise: decide if you'd rather restart the DAQ and hope for the best. Power cycling a machine takes a few minutes.
The IP is a dss-node: here you have an additional option: you can edit the <hutch>.cnf file to take out the node: look for "dss_nodes = [....]" and take out the problematic node.
(XPP/XCS specific):Is this the first node, notify the PCDS-POC as this node runs a special process that will NOT stop when the DAQ stops. Depending on the data rate, you can run with 2 or 3 nodes (cspad + other detectors: 3 nodes, two EPIX: 2 nodes). As we run all the data into a single ami session and the best mapping allows max one ami node/dss node, you have less ami power if you have less dss nodes.
use "serverStat <DAQ device alias>" to check on the health of the node. Most likely it is prudent to power-cycle this node.
"serverStat" at this moment lives are /reg/g/xpp/scripts, but should work in all hutches. A better place for common scripts will created & populated soon.