Experimental Physics and
Industrial Control System

>Is Puppet running them inside a container?

 

No container, ProcServ is just running them on the host machine.

 

> The iocsh command ‘casr 1’ will show you what the network interfaces are that the CA server is listening on and sending beacons to.

Ah, this is the command I was looking for. The result comes up completely blank.

From: Johnson, Andrew N. <anj at anl.gov> 
Sent: Friday, August 13, 2021 12:22 PM
To: Daykin, Evan <daykin at frib.msu.edu>
Cc: EPICS tech-talk <tech-talk at aps.anl.gov>
Subject: Re: IOC up, but can't connect via channel access

 

[EXTERNAL] This email originated from outside of FRIB

Hi Evan, 

 

On Aug 13, 2021, at 10:48 AM, Daykin, Evan via Tech-talk <tech-talk at aps.anl.gov> wrote:

 

I have just restarted a set of IOCs after puppetizing their configuration. They are accessible via a Telnet ProcServ connection, and dbpf shows everything populated and defined. However, if I try to use caget, caput, etc. there is no connection. What are the possible causes of this? EPICS_CA_AUTO_ADDR_LIST seems to be set as “YES” and other IOCs I haven’t touched are still reachable.

 

Is Puppet running them inside a container? If so you need to configure that to share the host’s network (or run a CA Gateway between the host’s network and the internal container network, but I don’t really recommend doing that).

 

The iocsh command ‘casr 1’ will show you what the network interfaces are that the CA server is listening on and sending beacons to.

 

- Andreww

 

-- 

Complexity comes for free, simplicity you have to work for.