EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: RE: socket creation errors
From: [email protected] (Jeff Hill)
To: <[email protected]>
Cc: "EPICS-tech-talk" <[email protected]>
Date: Tue, 10 Oct 2000 18:19:42 -0600
Grahm,

You might also try reconfiguring vxWorks to allow
the IP kernel to expand its internal pool. 
In Tornado II this can be configured in their workspace
GUI by clicking the vxWorks tab and then following this 
hierarchy:

network components
	basic network components initialization
		

Next, double click "network buffer initializations" and then
select the "params" tab.

Jeff

> -----Original Message-----
> From: Graham Waters [mailto:[email protected]]
> Sent: Tuesday, October 10, 2000 4:53 PM
> To: [email protected]
> Subject: socket creation errors
> 
> 
> I am in the process of porting our epics applications from
> epics R3.13.1 under vxWorks 5.3 to epics R3.13.3 under vxWorks 5.4.
> Generally thinks went quit well with no problems building the
> epics release. However I have one application involving TCP/IP
> connections in device support. I create driver instances and a
> few sockets prior to calling iocInit without error messages.
> After iocInit generally something like the following happens. Its
> as though I gobble up all available space for socket ID's.
> 
> interrupt
> eio: reset
> 
> socket create failed: errno = 0x37  (CA_TCP): CAS: Socket creation error
> ../repeater.c: Unable to create repeater socket because 55="errno =
> 0x37"
> CAS: casts socket creation error
> filename="../taskwd.c" line number=175
> CA_TCP suspended
> CAT_UDP suspends
> 
> error number 55 seems to be "No buffer space available"
> 
> The problem goes away if,
> 1) I reduce the number of epics devices using sockets
>    (yes I did increase the value of "NUM_FILES")
> 2) Build a kernel with all WDB tasks excluded
> 
> I have seen references to "interrupt, eio: reset" in tech-talk"
> whatever causes that message seems to be benign.
> 
> Does any of this mean anything or sound familiar to anybody.
> 
> +---------------------------------------------------------------------+
> |Graham Waters, Control System Eng       phone: (604)-222-1047        |
> |TRIUMF --- University of B.C,           Fax: (604)-222-7307          |
> |Vancouver, BC, Canada                e-mail: [email protected] |
> |                                                                     |
> |http://edevel9pc.triumf.ca/homepage/graham01.html                    |
> +---------------------------------------------------------------------+
> 
> For every expert there is an equal and opposite expert
> 					- Arthur C Clark


Replies:
Re: socket creation errors Graham Waters
References:
socket creation errors Graham Waters

Navigate by Date:
Prev: RE: socket creation errors Mark Rivers
Next: Keithley 7002/2010 data aquisition Mathew Rippa
Index: 1994  1995  1996  1997  1998  1999  <20002001  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: socket creation errors Graham Waters
Next: Re: socket creation errors Graham Waters
Index: 1994  1995  1996  1997  1998  1999  <20002001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·