Project

General

Profile

Bug #22957

Message Facility host

Added by Iker de Icaza Astiz 5 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
07/17/2019
Due date:
% Done:

0%

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

Description

On SBN we are doing multi server runs on the private subnet, spawning processes on sbnd-daq33 and sbn-daq01. Setting the hostname that goes on the MessageFacility.fcl file as localhost doesn't work. To be able to pick up the messages of both hosts you need to set it to sbnd-daq33-priv or sbn-daq01-priv, I believe this depends on the node from which you start up the interface.

Is there a way in which setting localhost will recognise that it need to be private subnet? So that there's no need to edit the fcl file depending on the server you are running.

I think this might be related to Bug #22785.

History

#1 Updated by John Freeman 5 months ago

It's definitely true that setting the hostname to "localhost" in MessageFacility.fcl wouldn't work, since MessageFacility.fcl will be passed to artdaq processes on different nodes, but the hostname needs to refer to the host which is running MessageViewer. DAQInterface is a general-purpose piece of software which is used by many different experiments, so it doesn't have any direct knowledge of sbn-daq01-priv or sbnd-daq33-priv.

So, the question remains, how can you get MessageFacility.fcl to contain the hostname value you want? It seems one way to do it would be to automatically edit MessageFacility.fcl via a sed command in one of your start scripts, so that the hostname would be set to the value of the node you decided to launch DAQInterface on.

#2 Updated by Iker de Icaza Astiz 5 months ago

Thanks for the suggestion John. I've added a line to deal with this in our code.

Feel free to close.

#3 Updated by John Freeman 5 months ago

  • Status changed from New to Closed


Also available in: Atom PDF