Project

General

Profile

Bug #3765

Process Names Error with NetMon input/output modules

Added by Steve Foulkes about 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Navigation
Target version:
Start date:
04/25/2013
Due date:
% Done:

100%

Estimated time:
Occurs In:
Scope:
Internal
Experiment:
-
SSI Package:
Duration:

Description

The system is configured as follows:
  • Single event builder node, process name DAQ
  • Single Aggregator node, process name DAQGG
  • RootOutput in the Aggregator configured to drop 2 products
  • NetMon used to transfer data between art process in EventBuilder and Aggregator

I get the following error in the Aggregator when it receives the first event:

Tue Apr 23 14:40:05 -0500 2013: ---- EventProcessorFailure BEGIN
Tue Apr 23 14:40:05 -0500 2013:   An exception occurred during current event processing
Tue Apr 23 14:40:05 -0500 2013:   ---- ScheduleExecutionFailure BEGIN
Tue Apr 23 14:40:05 -0500 2013:     ProcessingStopped.
Tue Apr 23 14:40:05 -0500 2013:     
Tue Apr 23 14:40:05 -0500 2013:     ---- Configuration BEGIN
Tue Apr 23 14:40:05 -0500 2013:       The process name DAQ was previously used on these products.
Tue Apr 23 14:40:05 -0500 2013:       Please modify the configuration file to use a distinct process name.
Tue Apr 23 14:40:05 -0500 2013:       cet::exception going through module RootOutput/normalOutput run: 101 subRun: 1 event: 1
Tue Apr 23 14:40:05 -0500 2013:     ---- Configuration END
Tue Apr 23 14:40:05 -0500 2013:     Exception going through path my_output_modules
Tue Apr 23 14:40:05 -0500 2013:   ---- ScheduleExecutionFailure END
Tue Apr 23 14:40:05 -0500 2013:   cet::exception caught in EventProcessor and rethrown
Tue Apr 23 14:40:05 -0500 2013: ---- EventProcessorFailure END

History

#1 Updated by Marc Paterno about 6 years ago

The different layers of the system that are running art must have different process names. The exception throw above is the result of one of the later art processes discovering this was not the case.

I believe the only reasonable solution is to arrange for the process names to be distinct.

#2 Updated by Steve Foulkes about 6 years ago

Marc Paterno wrote:

The different layers of the system that are running art must have different process names. The exception throw above is the result of one of the later art processes discovering this was not the case.

I believe the only reasonable solution is to arrange for the process names to be distinct.

The process names are distinct, I still get the process name error.

#3 Updated by Christopher Green about 6 years ago

  • Description updated (diff)

#4 Updated by Christopher Green about 6 years ago

  • Category set to Navigation
  • Status changed from New to Resolved
  • Assignee set to Paul Russo
  • Target version set to 1.07.00
  • % Done changed from 0 to 100

This issue has been resolved with 0a70bfa79d37d7e21d3984ee714cd70ff396c2d6.

#5 Updated by Christopher Green about 6 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF