Project

General

Profile

Bug #20385

run_demo.sh gets inconsistent results for the DAQInterface port when someone else is running the demo on mu2edaq01

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

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

0%

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

Description

There is a DAQInterface instance running from John's account:

[biery@mu2edaq01 artdaqDemo]$ ps -ef | grep -i daqinterface
biery 16907 4279 0 16:27 pts/35 00:00:00 grep --color=auto -i daqinterface
jcfree 21705 1 1 Jul15 ? 01:29:04 python /home/jcfree/artdaq-utilities-daqinterface/rc/control/daqinterface.py --partition-number 0 --rpc-port 10000
jcfree 21706 1 0 Jul15 ? 00:00:00 tee -a /tmp/daqinterface_jcfree/DAQInterface_partition0.log
[biery@mu2edaq01 artdaqDemo]$ date
Sat Jul 21 16:27:22 CDT 2018

When I run run_demo.sh, the DAQInterface instance that is started in the XTERM says that it is running on port 10010.

However, the function inside of run_demo.sh is looking for a DAQInterface at port 10000. So, my half of my run_demo script is talking to the DAQInterface instance in John's account, instead of the one running in my account.

History

#1 Updated by Kurt Biery about 1 year ago

  • Priority changed from Normal to Low


Also available in: Atom PDF