Project

General

Profile

Bug #20348

OnlineMonitoring reports timeouts while reading events from Dispatcher.

Added by Gennadiy Lukhanin about 1 year ago. Updated about 1 year ago.

Status:
Work in progress
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
07/18/2018
Due date:
% Done:

0%

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

Description

DAQ configured to run the mediumsystem_with_routing_master test at 1Hz.

The OnlineMonitoring job reports timeouts while reading events from Dispatcher.

[mu2etrg@mu2edaq11 DAQInterfaceTest]$ art -c ./TransferInputShmem.fcl 
%MSG-i MF_INIT_OK:  Early 18-Jul-2018 13:03:56 CDT JobSetup
Messagelogger initialization complete.
%MSG
%MSG-i DeactivatedPath:  Early 18-Jul-2018 13:03:57 CDT JobSetup
Detected end path "a1" which was not found in
parameter "physics.end_paths". Path will be ignored.
%MSG
%MSG-i DeactivatedPath:  Early 18-Jul-2018 13:03:57 CDT JobSetup
Detected end path "a2" which was not found in
parameter "physics.end_paths". Path will be ignored.
%MSG
%MSG-i DeactivatedPath:  Early 18-Jul-2018 13:03:57 CDT JobSetup
Detected end path "e1" which was not found in
parameter "physics.end_paths". Path will be ignored.
%MSG
%MSG-i TransferWrapper:  DAQ 18-Jul-2018 13:03:57 CDT Booted TransferWrapper.cc:71
Attempting to register this monitor ("shmem1") with the dispatcher aggregator
%MSG
%MSG-i TransferWrapper:  DAQ 18-Jul-2018 13:03:57 CDT Booted TransferWrapper.cc:76
Response from dispatcher is "Success" 
%MSG
%MSG-i configureMessageFacility:  artdaqart 18-Jul-2018 13:03:57 CDT Booted configureMessageFacility.cc:300
Message Facility Application artdaqart configured with: debugModules:["*"] destinations:{console:{threshold:"INFO" type:"cout"}}
%MSG
%MSG-w TransferWrapper:  DAQ 18-Jul-2018 13:03:58 CDT Booted TransferWrapper.cc:142
Timeout occurred in call to transfer_->receiveFragmentFrom; will try again, status = -1
%MSG
%MSG-w TransferWrapper:  DAQ 18-Jul-2018 13:04:00 CDT Booted TransferWrapper.cc:142
Timeout occurred in call to transfer_->receiveFragmentFrom; will try again, status = -1
%MSG
%MSG-w TransferWrapper:  DAQ 18-Jul-2018 13:04:05 CDT Booted TransferWrapper.cc:142
Timeout occurred in call to transfer_->receiveFragmentFrom; will try again, status = -1
%MSG
%MSG-w TransferWrapper:  DAQ 18-Jul-2018 13:04:10 CDT Booted TransferWrapper.cc:142
Timeout occurred in call to transfer_->receiveFragmentFrom; will try again, status = -1
%MSG
%MSG-w TransferWrapper:  DAQ 18-Jul-2018 13:04:15 CDT Booted TransferWrapper.cc:142
Timeout occurred in call to transfer_->receiveFragmentFrom; will try again, status = -1
%MSG
%MSG-w TransferWrapper:  DAQ 18-Jul-2018 13:04:20 CDT Booted TransferWrapper.cc:142
Timeout occurred in call to transfer_->receiveFragmentFrom; will try again, status = -1
%MSG
%MSG-w TransferWrapper:  DAQ 18-Jul-2018 13:04:25 CDT Booted TransferWrapper.cc:142
Timeout occurred in call to transfer_->receiveFragmentFrom; will try again, status = -1
%MSG
%MSG-w TransferWrapper:  DAQ 18-Jul-2018 13:04:30 CDT Booted TransferWrapper.cc:142
Timeout occurred in call to transfer_->receiveFragmentFrom; will try again, status = -1
%MSG

Related issues

Related to artdaq - Bug #20372: SBN om attachClosed07/19/2018

History

#1 Updated by Kyle Knoepfel about 1 year ago

  • Description updated (diff)

#2 Updated by Ron Rechenmacher about 1 year ago

#3 Updated by Ron Rechenmacher about 1 year ago

increasing om art timeout seems to work. See source.timeoutInUsecs in tools/fcl/TransferInputShmem.fcl:

...
source: {

module_type: TransferInput
  1. The timeout shouldn't be much smaller than the period between events, otherwise # there's a spew of timeout messages
timeoutInUsecs: 60000000  
...

#4 Updated by Ron Rechenmacher about 1 year ago

  • Status changed from New to Work in progress
  • Priority changed from Normal to Low


Also available in: Atom PDF