Place a limit on the number of MessageFacility messages of a given type getting printed out
One of the consequences of a recently observed segmentation fault in artdaq v2_03_03 on the CERN teststand (fixed by artdaq commit 74c497e054359025f785f00a3b1774a2a1f23292 on Oct. 23) is that tens of thousands of MPI error messages would start spewing out, obscuring any other error messages. In light of this, with artdaq-utilities-daqinterface commit 6902c575af3dd4134137e83c11bb208980edc7ca, the default behavior of DAQInterface is now to limit the number of printouts of any given message type to 50 in 10 seconds. Since this may not be the desired behavior, users can also edit the file containing the messagefacility FHiCL snippet - this file is either called "MessageFacility.fcl" in the current working directory, or can be referred to by an environment variable "DAQINTERFACE_MESSAGEFACILITY_FHICL".
I'm marking this down as 80% done because while this feature works for messageviewer and for the process specific logfiles (boardreader*.log, etc.), this doesn't yet work for pmt*.log.
#1 Updated by John Freeman about 2 years ago
- Status changed from New to Resolved
- % Done changed from 80 to 100
I've figured out how to suppress the error messages being sent to pmt*.rb. In artdaq's configureMessageFacility function, in its FHiCL definition of the console table, whether it uses "type: ANSI" or "type: cout" depends on whether ARTDAQ_MFEXTENSIONS_DIR is defined. By undefining it, so that "type: cout" ends up being used, suppression occurs. This leaves open the question as to why "type: ANSI" behaves differently, but that's outside the scope of this Issue.