How to check DAQ log files?

These are the daq log files from each run. They contain all the messages that scroll by on the RUN CONTROL error display screen.
Look at the CDF shift elog for a general idea of recent run numbers. Or type "ls -lat | more" in the /cdf/code-common/cdfonline/errmon/log directory.
Or login to any b0dap** machine, type "setup fer", then type "goodrun". In the GUI, select the GoodRun ShiftCrew option and COT on, select a range of dates, then click select. A list of runs matching your criteria will be displayed, with information on the number of events, luminosity, live-time and trigger table id for each run.

1. Login to any b0dap** machine.

2. cd /cdf/code-common/cdfonline/errmon/log

3. grep -i "b0xft" errorfileNNNN* | more If NNNN=1193, this will print out any lines containing b0xft for error files from runs 119300-119399

See XFT.h and XFT.c in the fer (front-end readout) package in the online code repository for more details on the possible error messages and the code that generates them.

Fatal errors
These will stop a COLDSTART - you'll probably have been paged by the shift crew before finding these in the log files! Examples are:

VISIONread/write errors (fuse probably blown, check green light)
errorfile118769.log:(MLE) b0xft05:Messenger:11:26:21 AM->VISION read failed in slot 6

Download errors (serious board problem):
errorfile119300.log:(MLE) b0xft05:Messenger:5:10:42 PM->slot 10, Download attempt failed (code 35)
errorfile119300.log:(MLE) b0xft05:Messenger:5:10:42 PM->Setup failed with error code 35
errorfile119300.log:(MLE) b0xft05:Messenger:5:10:43 PM->Statechange failed
errorfile119301.log:(MLE) b0xft05:Messenger:5:18:50 PM->slot 10, Download attempt failed (code 35)
errorfile119301.log:(MLE) b0xft05:Messenger:5:18:50 PM->Setup failed with error code 35
errorfile119301.log:(MLE) b0xft05:Messenger:5:18:51 PM->Statechange failed
errorfile119302.log:(MLE) b0xft05:Messenger:5:28:57 PM->slot 10, Download attempt failed (code 35)
errorfile119302.log:(MLE) b0xft05:Messenger:5:28:57 PM->Setup failed with error code 35
errorfile119302.log:(MLE) b0xft05:Messenger:5:28:58 PM->Statechange failed
errorfile119303.log:(MLE) b0xft05:Messenger:5:37:32 PM->slot 10, Download attempt failed (code 35)
errorfile119303.log:(MLE) b0xft05:Messenger:5:37:32 PM->Setup failed with error code 35
errorfile119303.log:(MLE) b0xft05:Messenger:5:37:32 PM->Statechange failed

Messages
Bunch-counter mismatches - check these are infrequent, ie not on every event. They seem to be mostly in finder crates, should be very infrequent, with only one or two messages per run. Don't know the cause of these messages - clock glitch, ansley cable data error, system-wide problem?

errorfile119327.log:(MLE) b0xft02:Messenger:9:29:12 PM->Event 4620: Bunchcounters in slot 13 and slot 6 disagree (at least)
errorfile119327.log:(MLE) b0xft02:Messenger:9:29:13 PM->Runtime Error 1, Event 4620: Bunch counter mismatch, mismatch count = 1

Messages to ignore
End of run messages:

errorfile119394.log:(EOR) b0xft00: triggered 112705/readout 112705/sent 112705 events.
errorfile119394.log:(EOR) b0xft02: triggered 112705/readout 112705/sent 112705 events.
errorfile119394.log:(EOR) b0xft04: triggered 112705/readout 112705/sent 112705 events.