Why Did the DAQ Stop or Crash?

This page will describe the steps to take to figure out what caused the DAQ to stop or crash crash.

Stopped runs

There is a script (which I think Erin made?) that auto-stops runs that are going bad. Sometimes, if the shifter or expert hasn't noted down why the run stopped, it could be that it was auto-stopped by this script.

Working out which runs were auto-stopped

You can find the logs of the runs that were auto-stopped in the directory noted below:

/home/nfs/sbnddaq/stopdaq/stop_daq.log

Crashed runs

Working out which runs crashed

The DAQ runs spreadsheet, as seen below, automatically records in the 'Crashed' column whether the DAQ crashed or not. This is where you need to look for this!

Working out how/why the run crashed

Sometimes, it's not instantly obvious how or why a run crashed. Luckily, Gray's script, printDAQLogs.py will tell you why a run crashed if you give it a run number (also in the spreadsheet):

python printDAQLogs.py -r <run_number>

This will output the logs for this specific run, allowing you to see any messages that might have appeared at the time it crashed. This is useful to run when you're writing your expert update for the following week's Operations meeting!