Project

General

Profile

Bug #25383

artdaq_daqinterface doesn't respect HOSTNAME environment variable/not working with "daq" network in ICARUS

Added by Wesley Ketchum about 2 months ago. Updated 7 days ago.

Status:
Reviewed
Priority:
Normal
Assignee:
Eric Flumerfelt
Category:
-
Target version:
-
Start date:
01/11/2021
Due date:
% Done:

0%

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

Description

Getting a "Permission denied" in ICARUS DAQInterface when it tries to check for existence of DAQ log files. Believe this is due to recent change that doesn't use the HOSTNAME environment variable within daqinterface, so that it's not ssh'ing over the internal DAQ network when doing these checks. (Maybe?)

History

#1 Updated by Eric Flumerfelt about 2 months ago

  • Assignee set to Eric Flumerfelt
  • Status changed from New to Resolved

I've put some fixes on artdaq-utilities-daqinterface:bugfix/25383_MoreConsistentLocalHostnameChecks, and they resolve the problem for the mu2edaq-data network.

Wes, can you give it a try sometime?

#2 Updated by Gennadiy Lukhanin 7 days ago

  • Status changed from Resolved to Reviewed

The feature branch bugfix/25383_MoreConsistentLocalHostnameChecks was included into the release v3_09_04p1 and tested at the Icarus test-stand. Servers with multiple network interfaces still need to have the environment variable HOSTNAME defined in order work properly over the “-daq” or “-priv” network interface.

Also available in: Atom PDF