Project

General

Profile

Bug #20404

EventBuilders stop dataflow when there is a configured rootNetOutput module, but no Dispatcher running

Added by Kurt Biery over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
07/23/2018
Due date:
% Done:

0%

Estimated time:
Experiment:
-
Co-Assignees:
Duration:

Description

Messages from the EB log, run 2813 at protoDUNE:

%MSG-i SharedMemoryReader:  Early 23-Jul-2018 13:34:30 CEST JobSetup SharedMemoryReader.hh:110
SharedMemoryReader initialized with ParameterSet: module_label:"source" module_type:"DuneInput" resume_after_timeout:true waiting_time:2.5e6
%MSG
%MSG-e _DataSenderManager:  DAQ 23-Jul-2018 13:34:30 CEST Booted DataSenderManager.cc:85
No destinations specified!
%MSG
%MSG-i FastCloning:  RootOutput:normalOutput@Construction  23-Jul-2018 13:34:30 CEST ModuleConstruction
Initial fast cloning configuration (user-set): false
%MSG
23-Jul-2018 13:35:00 CEST  Opened output file with pattern "/data1/np04_raw_run%06r_%#_dl2.root" 
%MSG-w _DataSenderManager:  DAQ 23-Jul-2018 13:35:01 CEST Booted DataSenderManager.cc:403
Could not get destination for seqID 1, retrying.
%MSG
%MSG-w _DataSenderManager:  DAQ 23-Jul-2018 13:35:01 CEST Booted DataSenderManager.cc:403
Could not get destination for seqID 1, retrying.
%MSG
%MSG-w _DataSenderManager:  DAQ 23-Jul-2018 13:35:01 CEST Booted DataSenderManager.cc:403
Could not get destination for seqID 1, retrying.
%MSG
%MSG-w _DataSenderManager:  DAQ 23-Jul-2018 13:35:01 CEST Booted DataSenderManager.cc:403
Could not get destination for seqID 1, retrying.
%MSG
%MSG-w _DataSenderManager:  DAQ 23-Jul-2018 13:35:01 CEST Booted DataSenderManager.cc:403
Could not get destination for seqID 1.
%MSG
%MSG-e _DataSenderManager:  DAQ 23-Jul-2018 13:35:01 CEST Booted DataSenderManager.cc:427
calcDest returned invalid destination rank -1111! This event has been lost: 1
%MSG
%MSG-w _DataSenderManager:  DAQ 23-Jul-2018 13:35:04 CEST Booted DataSenderManager.cc:403
Could not get destination for seqID 4, retrying.
%MSG
%MSG-w _DataSenderManager:  DAQ 23-Jul-2018 13:35:04 CEST Booted DataSenderManager.cc:403
Could not get destination for seqID 4, retrying.
%MSG
%MSG-w _DataSenderManager:  DAQ 23-Jul-2018 13:35:04 CEST Booted DataSenderManager.cc:403
Could not get destination for seqID 4, retrying.
%MSG
%MSG-w _DataSenderManager:  DAQ 23-Jul-2018 13:35:04 CEST Booted DataSenderManager.cc:403
Could not get destination for seqID 4, retrying.
%MSG
%MSG-w _DataSenderManager:  DAQ 23-Jul-2018 13:35:04 CEST Booted DataSenderManager.cc:403
Could not get destination for seqID 4.
%MSG
%MSG-e _DataSenderManager:  DAQ 23-Jul-2018 13:35:04 CEST Booted DataSenderManager.cc:427
calcDest returned invalid destination rank -1111! This event has been lost: 4
%MSG
%MSG-w _DataSenderManager:  DAQ 23-Jul-2018 13:35:04 CEST Booted DataSenderManager.cc:403
Could not get destination for seqID 16, retrying.
%MSG
%MSG-w _DataSenderManager:  DAQ 23-Jul-2018 13:35:04 CEST Booted DataSenderManager.cc:403
Could not get destination for seqID 16, retrying.

History

#1 Updated by Ron Rechenmacher over 1 year ago

  • Priority changed from Normal to Low

At cern, and for the time being, online monitoring is going to be done from files. The rootNetOutput config is to be removed from the
eventbuilder configs, at least for the time being.

Also available in: Atom PDF