EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: RE: Winsock error10004
From: "Mark Rivers" <[email protected]>
To: "Mark Clift" <[email protected]>, "J. Lewis Muir" <[email protected]>, "Jeff Hill" <[email protected]>
Cc: [email protected]
Date: Wed, 29 Apr 2009 13:02:04 -0500
Mark,
 
I just built and ran the "example" application on win32-x86.  I sometimes get the same error you were getting.  I just started and exited the IOC 3 times and got a different set of errors each time.

epics> exit
CAS: Client accept error was "WINSOCK Error 10004"
CA cast server: Unable to fetch N characters pending

epics> exit
CAS: UDP recv error (errno=WINSOCK Error 10004)
CAS: Client accept error was "WINSOCK Error 10004"
CA cast server: Unable to fetch N characters pending
CAS: UDP recv error (errno=WINSOCK Error 10093)
 
epics> exit
CAS: UDP recv error (errno=WINSOCK Error 10004)
CAS: Client accept error was "WINSOCK Error 10004"
..\online_notify.c: CA beacon routing (connect to "164.54.160.255:5065") error was "WINSOCK Error 10093"
CA cast server: Unable to fetch N characters pending
CAS: UDP recv error (errno=WINSOCK Error 10093)
 
 
So I don't think you have a configuration problem, I think that the behavior on exit is not reproducible and sometimes results in these errors.
 
Mark
 

________________________________

From: Mark Clift [mailto:[email protected]]
Sent: Sun 4/26/2009 6:34 PM
To: Mark Rivers; J. Lewis Muir; Jeff Hill
Cc: [email protected]
Subject: RE: Winsock error10004



Hi Guys,

Thanks so much for the comments.

I believe I have a local issue here that is not related to any of the community software.  I added the epicsExit(0) call to the IOC's that are in areaDetector, and then began receiving errors with these on exit also.  A second Windows box was then configured (on a different network), and it did not show the same symptoms.  Also, Mark Rivers' did not see errors on exit with the areaDetector IOC's with the epicsExit(0) added in.

Fresh install time.! :)

Thanks again.

Best Regards,

Mark Clift.

________________________________________
From: Mark Rivers [[email protected]]
Sent: Saturday, 25 April 2009 4:36 AM
To: J. Lewis Muir; Jeff Hill
Cc: Mark Clift; [email protected]
Subject: RE: Winsock error10004

Thanks to Lewis for pointing our that the areaDetector main programs were not calling epicsExit(0).  They should have been, and that was causing a problem on Linux, where typing exit would NOT exit, it would hang.  The only way to kill the IOC was to type ^C.

I just added the epicsExit(0) call, and it fixes that problem on Linux.  I also checked that it does not introduce the problem Mark Clift is seeing on win32-x86, those IOCs continue to exit cleanly with no errors.  I am building everything statically on both win32-x86 and linux-x86.

Mark


________________________________

From: [email protected] on behalf of J. Lewis Muir
Sent: Fri 4/24/2009 11:01 AM
To: Jeff Hill
Cc: 'Mark Clift'; [email protected]
Subject: Re: Winsock error10004



On 4/24/09 11:42 AM, Jeff Hill wrote:
>> * Strangely, the ioc's that build under areaDetector 1-4 using
>>   win32-x86, do not have this error on exit and run fine.
>
> One possible difference could be systems with and without SMP
> (multi-core cpu or not). Alternatively, statically built or not might
> change the order of process rundown as executed by windows (i.e.
> threads stopped first versus shareable libraries unmapped from memory
> first).

Another possible difference is that the areaDetector IOCs don't invoke
epicsExit before returning from their main function; other IOCs do.

Lewis
This message and any attachments may contain proprietary or confidential information. If you are not the intended recipient or you received the message in error, you must not use, copy or distribute the message. Please notify the sender immediately and destroy the original message. Thank you.



Replies:
RE: Winsock error10004 Mark Clift
References:
Winsock error10004 Mark Clift
RE: Winsock error10004 Jeff Hill
Re: Winsock error10004 J. Lewis Muir
RE: Winsock error10004 Mark Rivers
RE: Winsock error10004 Mark Clift

Navigate by Date:
Prev: RE: dbCaPutLinkCallback crash in 3.14.10 on cygwin; PROBLEM SOLVED Mark Rivers
Next: Re: dbCaPutLinkCallback crash in 3.14.10 on cygwin; PROBLEM SOLVED Tim Mooney
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Winsock error10004 Mark Clift
Next: RE: Winsock error10004 Mark Clift
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 31 Jan 2014 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·