Experimental Physics and
Industrial Control System

Andrew Johnson <[email protected]> · Thu, 12 Jul 2018 15:12:22 -0500

Hi Matt,

On 07/12/2018 02:54 PM, Matt Rippa wrote:
> We ran a simple caget (once per second) from a linux host to an upgraded
> IOC. With the new rtems/3.14.12.7 <http://3.14.12.7> IOC, it often
> experiences timeouts as shown below. With our legacy vxworks/3.13.9 IOC
> there are no timeouts logged. Relevant info is shown below. The
> caRepeater is running on the linux host.

If your IOC is busy the caget default search timeout of 1 second may be
too short, have you tried using 'caget -w 5 tcs:ak:astCtx' say?

> I'm thinking that setting the linux host EPICS_CA_ADDR_LIST=YES may
> help. I'm running that test now. 

I have never seen an EPICS_CA_ADDR_LIST as long as yours, but given that
you seem to be searching multiple subnets maybe you do need that.

I don't think setting EPICS_CA_AUTO_ADDR_LIST to YES will make any
difference to this behaviour (your epicsPrtEnvParams showed it as YES
already, so unless you have explicitly changed it for the client you're
probably already searching your local subnet as well).

HTH,

- Andrew

> EPICS_CA_ADDR_LIST=172.17.2.255 172.17.3.255 172.17.102.130
> 172.17.105.20 172.16.102.130 aom-vme sbfmcao01.cl.gemini.edu
> mcao-stealth.cl.gemini.edu 172.17.106.111 172.17.105.37
> 172.17.107.50 172.17.55.101 172.17.101.101 172.17.65.255
> 172.17.102.139 172.17.102.138
> 
> linux> caget tcs:ak:astCtx
> tcs:ak:astCtx                  0
> linux> caget tcs:ak:astCtx
> Channel connect timed out: 'tcs:ak:astCtx' not found.
> linux> caget tcs:ak:astCtx
> Channel connect timed out: 'tcs:ak:astCtx' not found.
> linux> caget tcs:ak:astCtx
> tcs:ak:astCtx                  0

-- 
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System