Experimental Physics and
Industrial Control System

> CAS: bad message type=11
> CAS ? on ? at xxxxxx.yyyyyy.lanl.gov:5064: cmd=11 cid=4294967295 typ=0
> cnt=0 psz=40 avail=8e

The cause was discovered to be a windows system with EPICS_CA_ADDR_LIST set to include the IP address and port
number of a CA gateway. This was necessary for CA clients on that host. However, when a CA server was also started
on that same host it used the same EPICS_CA_ADDR_LIST to configure the CA server's beacon address list, and a
beacon message was sent to a CA server. The normal recipients for CA beacon messages are CA clients (indirectly
through the CA repeater). The solution was to start this CA server with an empty EPICS_CA_ADDR_LIST.

In EPICS R3.14 there is an independent variable, the EPICS_CAS_BEACON_ADDR_LIST, which can be used to configure the
CA server's beacon address list. To remain backwards compatible, the R3.14 code still defaults to using the
EPICS_CA_ADDR_LIST if EPICS_CAS_BEACON_ADDR_LIST isn't specified. Perhaps that will be a source of confusion. Open
to suggestions.

Jeff

> -----Original Message-----
> From: Gary P Carr (by way of Gary P Carr <[email protected]>)
> [mailto:[email protected]]
> Sent: Monday, August 25, 2003 3:21 PM
> To: [email protected]
> Subject: Channel Access Errors
> 
> Sorry, really mean EPICS 3.13.2, not 3.12.
> 
> We've been getting these errors on our Channel Access Proxy Gateway for
> the
> last couple of days. We are using the version of the gateway built
> against
> patched EPICS 3.12. Use the gateway to provide access to the controls
> subnet from outside the control system. Only see these errors for two
> outside hosts. Other channel access through the gateway seems to work
> fine.
> I finally blocked access for the two hosts at our firewall. Had more
> than a
> Gig of log messages just like the following:
> 
> CAS: bad message type=11
> CAS ? on ? at xxxxxx.yyyyyy.lanl.gov:5064: cmd=11 cid=4294967295 typ=0
> cnt=0 psz=40 avail=8e
> Internal failure - unexpected error processing stateless protocol
> 
> Can't find a match to any of the strings in the errors in the gateway
> code
> itself. Anyone have an idea about what they mean?

References:

Channel Access Errors Gary P Carr

Navigate by Date:

Prev: Re: Channel Access Errors Brian McAllister

Next: RE: Channel Access Errors Jeff Hill

Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  <2003>  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 

Navigate by Thread:

Prev: Channel Access Errors Gary P Carr

Next: Does DISP work for DB OUT links? Benjamin Franksen

Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  <2003>  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024