EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
1994  1995  1996  1997  1998  1999  2000  2001  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  2000  2001  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: Winsock errors
From: "Jeff Hill" <[email protected]>
To: "'Mark Clift'" <[email protected]>, <[email protected]>
Date: Fri, 24 Apr 2009 09:33:13 -0600

Hello Mark,

 

Ø  CAS: Client accept error was "WINSOCK Error 10004"

When the IOC core components were ported to other OS besides vxWorks for EPICS R3.14 one task that was left unfinished was a well orchestrated shutdown. Unfortunately, the only way to shutdown the original R3.13 vxWorks IOC was to press the reset switch or remove power. That situation isn’t really different in R3.14 except  that now on Linux and Windows the IOC is shutdown by abruptly terminating the IOC’s process. Many threads in the system including the database processing, the CA server, device drivers, actually nearly all of the threads in the IOC remain running when the IOC’s process exits. The message you see are the last dying gasps from the CA server threads when the WINSOCK shareable library is abruptly ripped out of memory.

 

I am consolidating to only one server code, and one side effect will be gracefully shutdown of the CA server – installed first into EPICS R3.15.

 

Jeff

 

 

From: [email protected] [mailto:[email protected]] On Behalf Of Mark Clift
Sent: Thursday, April 23, 2009 8:56 PM
To: [email protected] ([email protected])
Subject: Winsock errors

 

Hello,

 

I'm building a basic IOC under windows by doing the following:

 

makeBaseApp.pl -t ioc <name>

makeBaseApp.pl -i -t ioc <name>

 

Then I build the ioc, and run it without databases.  Upon exit I get the following errors

 

CAS: Client accept error was "WINSOCK Error 10004"
CAS: UDP recv error (errno=WINSOCK Error 10004)
..\online_notify.c: CA beacon routing (connect to "10.123.255.255:5065") error w
as "WINSOCK Error 10093"

 

or


CA cast server: Unable to fetch N characters pending

CAS: Client accept error was "WINSOCK Error 10004"
CAS: UDP recv error (errno=WINSOCK Error 10004)
CA cast server: Unable to fetch N characters pending

 

 

Has anybody had this error, and know how to fix ?

 

 

Thanks heaps,

 

 

Mark Clift.

 

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.

References:
Winsock errors Mark Clift
Navigate by Date:
Prev: Winsock error10004 Mark Clift
Next: RE: Winsock error10004 Jeff Hill
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  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Winsock errors Mark Clift
Next: Winsock error10004 Mark Clift
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  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 ·