[Patch Available] "AcceptEx failed"

[William A. Rowe, Jr.]

For those getting the message

[error] (32538)An operation was attempted on something that is not a
socket. : winnt_accept: AcceptEx failed. Attempting to recover.

There is an patch (as a binary download) available for testing
corresponding to the bug report;

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8325

This bug primarily affects firewall/antivirus software users.

Anyone encountering this bug, running 2.0.43 (or able to recreate the
conditions for triggering this bug, such as reinstalling or enabling
their firewall or antivirus software) is welcome to try the patch
given under the URL above.

You may download a binary module built from 2.0.43 plus the patch from

http://www.apache.org/~wrowe/acceptex_fix1.zip

which contains only the replacement libhttpd.dll (DON'T UNPACK THIS
BINARY INTO ANY RELEASE VERSION OTHER THAN 2.0.43).

1. Confirm you are getting the AcceptEx failure.
2. Stop your Apache2 server
3. Unpack libhttpsd.dll from acceptex_fix1.zip into your apache2\lib
directory.
4. Restart your server and attempt to reproduce the AcceptEx failure.

Please post your success or failure to this report. Perhaps this can
be licked after all.

[Guardian]

"William A. Rowe, Jr." <wr...@apache.sans-junk.org> wrote in message
news:3DAB8748...@apache.sans-junk.org...

Thank you Will.

Would you please let me know if it would also clear(or have any effect on)
these errors that I have been getting(regularly) on Apache 2.0.43/WinXPpro?

[warn] (720121)The semaphore timeout period has expired. : winnt_accept:
Asynchronous AcceptEx failed.
[warn] (720064)The specified network name is no longer available. :
winnt_accept: Asynchronous AcceptEx failed.

Many Thanks
G.

-----------== Posted via Newsfeed.Com - Uncensored Usenet News ==----------
http://www.newsfeed.com The #1 Newsgroup Service in the World!
-----= Over 100,000 Newsgroups - Unlimited Fast Downloads - 19 Servers =-----

[William A. Rowe, Jr.]

> Would you please let me know if it would also clear(or have any effect on)
> these errors that I have been getting(regularly) on Apache 2.0.43/WinXPpro?
>
> [warn] (720121)The semaphore timeout period has expired. : winnt_accept:
> Asynchronous AcceptEx failed.
> [warn] (720064)The specified network name is no longer available. :
> winnt_accept: Asynchronous AcceptEx failed.

Those are two seperate bugs. One is a timeout perticularity on Win32,
the other has to do with DHCP refreshes. Two different cases, but be
careful we don't start creating duplicate bug reports, someone is
already planning to file the 720064 bug. You might kick off the 720121
report. And neither bug is related to the "not a socket" bug.

Bill

[William A. Rowe, Jr.]

William A. Rowe, Jr. wrote:
>
>> Would you please let me know if it would also clear(or have any effect
>> on)
>> these errors that I have been getting(regularly) on Apache
>> 2.0.43/WinXPpro?
>>

>> [warn] (720064)The specified network name is no longer available. :
>> winnt_accept: Asynchronous AcceptEx failed.

This bug is being tracked as 13661

[Guardian]

"William A. Rowe, Jr." <wr...@apache.sans-junk.org> wrote in message

news:3DAC5531...@apache.sans-junk.org...

Thank you for the information.
I look forward to hearing about the fix :)

[Everette B.]

"William A. Rowe, Jr." <wr...@apache.sans-junk.org> wrote in message news:<3DAB8748...@apache.sans-junk.org>...

I have this problem exactly and downloaded your patch. Didn't work.
Apache running on Windows XP home addition. Apache works fine with
McAfee 7.0... uninstalled, with or withoug the patch. Any other
suggestions would be appreciated.

[Photon]

I am running Win XP sp 1, McAfee Firewall version 3.03.1 and Apache
version 2.0.43.

I swapped out the libhttpd.dll file as suggested and restarted the
server and the "...not a socket..." error has stopped. However, now
there is no response on port 80 and no information is logged by
apache. I have tried connecting to port 80 on host 127.0.0.1 with
both a web browser and telnet. Has anyone else reported this? Any
idea what might be the cause?

Thanks in advance!

"William A. Rowe, Jr." <wr...@apache.sans-junk.org> wrote in message news:<3DAB8748...@apache.sans-junk.org>...

[Everette B.]

cwo...@sbcglobal.net (Photon) wrote in message news:<57a825ed.02111...@posting.google.com>...

I tried the patch as explained but am still getting the problem. I
was able to access my server for a couple of accesses and theh it
started again, i.e. constantly writing the error message to the errors
file. I do think anyone else trying this should be reminded to
restart their machine once the patch driver is instaled. Just
restarting Apache seems to be using the DLL that was apparently in
cache or memory.