Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request for review of various error messages that one sees in logfiles #135

Open
bieryAtFnal opened this issue Aug 16, 2023 · 1 comment

Comments

@bieryAtFnal
Copy link
Contributor

There are at least three different types of "error" messages that we occasionally see in the RU logfiles. It is hard to know whether these are really errors that a user should be worried about. And in some cases, it is not clear why the message is not being reported with an error status. I've seen these errors when using emulated-data systems.

It would be great to understand what these errors mean and, if needed, change their reporting appropriately.

  1. 2023-Aug-16 13:13:39,318 WARNING [void dunedaq::readoutlibs::FileSourceBuffer::read(const std::string&) at /home/biery/dunedaq/15AugFDDevLogFileChecks/sourcecode/readoutlibs/include/readoutlibs/utils/FileSourceBuffer.hpp:73] Configuration Error: Binary file contains more data than expected, filesize is 237336, chunk_size is 7200, filename is /cvmfs/dunedaq.opensciencegrid.org/assets/files/c/1/4/wibeth-frames-0.bin
  2. 2023-Aug-16 13:13:39,515 LOG [void dunedaq::readoutlibs::FrameErrorRegistry::add_error(std::string, ErrorInterval) at /home/biery/dunedaq/15AugFDDevLogFileChecks/sourcecode/readoutlibs/include/readoutlibs/FrameErrorRegistry.hpp:47] Encountered new error
  3. log_rulocalhosteth0_3336.txt:2023-Aug-15 10:24:30,867 LOG [void dunedaq::fdreadoutlibs::WIBEthFrameProcessor::sequence_check(frameptr) at /tmp/root/spack-stage/spack-stage-fdreadoutlibs-v1.7.3-wlxygdqw64irgdiurmgtoiemip53mzpm/spack-src/src/wibeth/WIBEthFrameProcessor.cpp:393] *** Data Integrity ERROR *** Sequence ID continuity is completely broken! Something is wrong with the FE source or with the configuration!

The first one has been discussed before, so maybe we just need to implement a known change.

I filed an incremental PR for the second one, in which I added more information about the type of error. It is easy to reproduce with certain WIBEth asset files and the minimal_system_quick_test.

I noticed the third one when testing a software area based on v4.1.1.

@bieryAtFnal
Copy link
Contributor Author

On the dunedaq-integration Slack channel, Michal Rigan posted the following:

Dunno if this is known, but I'm doing some offline development and I often get this error from ru:
2023-Sep-05 11:54:52,995 LOG [void dunedaq::fdreadoutlibs::WIBEthFrameProcessor::sequence_check(frameptr) at /tmp/root/spack-stage/spack-stage-fdreadoutlibs-NFD23-09-04-4ijcp6hukfsdxe3iagfnnr4y67lca35u/spack-src/src/wibeth/WIBEthFrameProcessor.cpp:393] *** Data Integrity ERROR *** Sequence ID continuity is completely broken! Something is wrong with the FE source or with the configuration!
(running dev, FD, use_recent_verified_dunedaq_code, very basic config, close to the one from the instructions page, including "default_data_file": "asset://?label=WIBEth&subsystem=readout") (edited)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant