Re: [EXTERNAL] procServ comminication with phoebus problem

[Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>]

Hi Ewen,

I think you are probably worried about these messsages after iocInit:

cas warning: Configured TCP port was unavailable.

cas warning: Using dynamically assigned TCP port 35429,

cas warning: but now two or more servers share the same UDP port.

cas warning: Depending on your IP kernel this server may not be

cas warning: reachable with UDP unicast (a host's IP in EPICS_CA_ADDR_LIST)

iocRun: All initialization complete

2023-06-02T06:34:42.607 Using dynamically assigned TCP port 56505.

Those are normal.  As long as your IOCs and your Channel Access clients are all on the same subnet then there is no problem, and the default behavior without setting EPICS_CA_AUTO_ADDR_LIST and EPICS_CA_ADDR_LIST will work fine.  If you need to run the client on a different subnet then things get more complicated.

Mark

---

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of wang Ewen via Tech-talk <tech-talk at aps.anl.gov>
Sent: Thursday, June 1, 2023 5:41 PM
To: Hartman, Steven <hartmansm at ornl.gov>
Cc: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: 回复: [EXTERNAL] procServ comminication with phoebus problem

 

Hi,

I start run annother ioc: [root@localhost iocmzexample]# procServ -n "my-ioc02" -L my-ioc.log -P 8889 -i "^D^C" /usr/local/EPICS/ioc01/iocBoot/iocmzexample/st.cmd

procServ: spawning daemon process: 4394

[root@localhost iocmzexample]# ps aux | grep procServ

root       3258  0.0  0.0  16928  1272 ?        Ss   06:09   0:00 procServ -n my-ioc -L my-ioc.log -P 8888 -i ^D^C /usr/local/EPICS/iocs/iocBoot/iocmyexample/st.cmd

root       4394  0.0  0.0  16928  1276 ?        Ss   06:34   0:00 procServ -n my-ioc02 -L my-ioc.log -P 8889 -i ^D^C /usr/local/EPICS/ioc01/iocBoot/iocmzexample/st.cmd

root       4444  0.0  0.0 112816   976 pts/2    S+   06:34   0:00 grep --color=auto procServ.

 

This is the second ioc log:
@@@ Restarting child "my-ioc02"

@@@    (as /usr/local/EPICS/ioc01/iocBoot/iocmzexample/st.cmd)

@@@ The PID of new child "my-ioc02" is: 4402

@@@ @@@ @@@ @@@ @@@

#!../../bin/linux-x86_64/mzexample

< envPaths

epicsEnvSet("IOC","iocmzexample")

epicsEnvSet("TOP","/usr/local/EPICS/ioc01")

epicsEnvSet("EPICS_BASE","/usr/local/EPICS/base")

cd "/usr/local/EPICS/ioc01"

## Register all support components

dbLoadDatabase "dbd/mzexample.dbd"

mzexample_registerRecordDeviceDriver pdbbase

## Load record instances

dbLoadTemplate "db/user.substitutions"

dbLoadRecords "db/mzexampleVersion.db", "user=root"

dbLoadRecords "db/dbSubExample.db", "user=root"

#var mySubDebug 1

#traceIocInit

cd "/usr/local/EPICS/ioc01/iocBoot/iocmzexample"

iocInit

Starting iocInit

############################################################################

## EPICS R7.0.3.1

## EPICS Base built Dec 16 2022

############################################################################

cas warning: Configured TCP port was unavailable.

cas warning: Using dynamically assigned TCP port 35429,

cas warning: but now two or more servers share the same UDP port.

cas warning: Depending on your IP kernel this server may not be

cas warning: reachable with UDP unicast (a host's IP in EPICS_CA_ADDR_LIST)

iocRun: All initialization complete

2023-06-02T06:34:42.607 Using dynamically assigned TCP port 56505.

## Start any sequence programs

#seq sncExample, "user=ewen"

[?1034hepics>

 

从 Windows 版邮件发送

 

发件人: Hartman, Steven
发送时间: 2023年6月2日 0:15
收件人: wang Ewen
抄送: tech-talk at aps.anl.gov
主题: Re: [EXTERNAL] procServ comminication with phoebus problem

 

 

On Jun 1, 2023, at 10:59 AM, wang Ewen via Tech-talk <tech-talk at aps.anl.gov> wrote:

 

[root@localhost iocmyexample]# procServ -n "my-ioc" -L my-ioc.log -P 8888 -i "^D^C" /usr/local/EPICS/iocs/iocBoot/iocmyexample/st.cmd

. . .

My phoebus setting.ini is:: 

org.phoebus.pv.ca/addr_list=192.168.238.134:8888

 

 

 

That is incorrect. In your configuration, procServ is using port 8888 to provide connection to the IOC console it serves. Channel Access is still using port 5064. Try org.phoebus.pv.ca/addr_list=192.168.238.134:5064.

You should be able to telnet to port 8888 to connect to the IOC shell via procServ. 

 

 

 

 

 

-- 

Steven Hartman

hartmansm at ornl.gov