Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017 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
<== Date ==> <== Thread ==>

Subject: RE: CA server bind failure on Windows
From: <freddie.akeroyd@stfc.ac.uk>
To: <anj@aps.anl.gov>
Cc: tech-talk@aps.anl.gov
Date: Thu, 19 Jan 2017 16:00:51 +0000
Hi Andrew,

I can confirm the patch works fine. Though Windows bind() can return 10 possible error codes, on closer inspection anything other than EACCES or EADDRINUSE indicate something is probably wrong with either the socket descriptor itself or the network interface being connected to and so a bind retry is unlikely to lead anywhere. Thus the more conservative approach should still cover all eventualities.

Thanks,

Freddie 

-----Original Message-----
From: Andrew Johnson [mailto:anj@aps.anl.gov] 
Sent: 18 January 2017 18:24
To: Akeroyd, Freddie (STFC,RAL,ISIS)
Cc: tech-talk@aps.anl.gov
Subject: Re: CA server bind failure on Windows

Hi Freddie,

On 01/12/2017 12:04 PM, freddie.akeroyd@stfc.ac.uk wrote:
> I've had instances of both an IOC and a CAS being unable to create a 
> channel access port. The servers attempt to bind to the usual channel 
> access server port number, but rather than EADDRINUSE being returned 
> on failure they are seeing EACCES.

Ralph suggested that we adopt a slightly more conservative approach to fixing the issue, could you confirm this patch please.

Thanks,

- Andrew

--
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


References:
CA server bind failure on Windows freddie.akeroyd
Re: CA server bind failure on Windows Andrew Johnson

Navigate by Date:
Prev: Re: Problem compiling StreamDevice on Visual Studio 2015 Dirk Zimoch
Next: Re: Problem NFS mounting Centos 7 file systems from vxWorks 5.5 Andrew Johnson
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
Navigate by Thread:
Prev: Re: CA server bind failure on Windows Andrew Johnson
Next: Problems with seq 2.2.4 on Windows Mark Rivers
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
ANJ, 14 Feb 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·