Experimental Physics and
Industrial Control System

Which version of Base is involved?  3.15?

If it's 7.0 then I think I have a fix in the queue (waiting on appveyor).
My attempt to fix epicsSocketEnableAddressUseForDatagramFanout() on vxWorks (which still needs confirmation)
and RTEMS had a side-effect on Linux where it seems that SO_REUSEADDR
and SO_REUSEPORT have the same effect, but are not interchangeable.

On 2/6/20 4:16 AM, Ralph Lange via Core-talk wrote:
> Dear Core-talkers,
> 
> We have been seeing an IOC lately that occasionally seems to boot fine, does not print the usual "cas warning: Configured TCP port was unavailable. [...]" messages for not being the first one on the host, but then emits a
> 
> CAS: Listen error: Address already in use
> Thread CAS-TCP (0x3337a20) suspended
> 
> and becomes CA unresponsive.
> 
> We recently changed our IOC startup to be systemd controlled and are starting all IOCs in parallel.
> Question: Is there a vulnerability for a race condition where two IOCs are under the impression of being able to use the original CA port, but one of them eventually fails to listen()?
> 
> Cheers,
> ~Ralph
> 

Attachment: signature.asc
Description: OpenPGP digital signature

Replies:

Re: Weird CAS hangup on IOC Ralph Lange via Core-talk

Re: Weird CAS hangup on IOC Andrew Johnson via Core-talk

References:

Weird CAS hangup on IOC Ralph Lange via Core-talk

Navigate by Date:

Prev: Re: Weird CAS hangup on IOC Torsten Bögershausen via Core-talk

Next: Re: Weird CAS hangup on IOC Ralph Lange via Core-talk

Index: 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: Re: Weird CAS hangup on IOC Torsten Bögershausen via Core-talk

Next: Re: Weird CAS hangup on IOC Ralph Lange via Core-talk

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020>  2021  2022  2023  2024