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

Subject: RE: TCP_NODELAY option set failed
From: "Jeff Hill" <johill@lanl.gov>
To: <mdavidsaver@bnl.gov>
Cc: tech-talk@aps.anl.gov
Date: Tue, 17 May 2011 09:57:31 -0600
> Cexp>CAS: TCP_NODELAY option set failed
>

If this happens only rarely, in isolated situations, then maybe an
explanation is that the network kernel is somehow temporarily starved for
resources, or otherwise if the situation persists then perhaps the network
kernel was somehow comprised. In a vxWorks system lacking mmu protection
there could be a number of scenarios. I nevertheless had a quick look at the
code and I don?t see any obvious causes of trouble.

Jeff
______________________________________________________
Jeffrey O. Hill           Email        johill@lanl.gov
LANL MS H820              Voice        505 665 1831
Los Alamos NM 87545 USA   FAX          505 665 5107

Message content: TSPA

With sufficient thrust, pigs fly just fine. However, this is
not necessarily a good idea. It is hard to be sure where they
are going to land, and it could be dangerous sitting under them
as they fly overhead. -- RFC 1925


> -----Original Message-----
> From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov]
> On Behalf Of Michael Davidsaver
> Sent: Tuesday, May 17, 2011 8:55 AM
> To: tech-talk@aps.anl.gov
> Cc: Chabot, Daron
> Subject: TCP_NODELAY option set failed
> 
> Cexp>
> Cexp>CAS: TCP_NODELAY option set failed
> 
> I happened to notice this error in the log of one of our IOCs.  I've not
> seen it before.  It only happened once, but seemed suitable strange to
> be worth reporting.
> 
> EPICS 3.14.11
> RTEMS 4.9.3 on a mvme3100
> 
> Also deviocstats and the new mrfioc2 timing driver.  The IOC was
> functioning correctly when I checked it.
> 
> It looks like this error comes from create_tcp_client() in
> caservertask.c when setsockopt() for the NODELAY socket option fails for
> a newly connected CA client.  Since I only see one message I assume the
> client was able to connect successfully on a retry.
> 
> Has anyone else seen this error?
> 
> 
> Thanks,
> Michael



References:
TCP_NODELAY option set failed Michael Davidsaver

Navigate by Date:
Prev: RE: Channel Access not connecting Jeff Hill
Next: RE: Handling failures in st.cmd Zelazny, Michael Stanley
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019 
Navigate by Thread:
Prev: TCP_NODELAY option set failed Michael Davidsaver
Next: Simple VME digital I/O Ralph Lange
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·