You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Steve Hay <St...@planit.com> on 2010/10/15 13:59:29 UTC
[users@httpd] What are OS64 and OS10054 errors typically caused by (Win32)
I have a customer running Apache 2.2.14 / mod_perl 2.0.4 / Perl 5.10.1
on Windows Server 2003 R2 SP2 (in a VMware setup).
Their error.log (with Loglevel set to debug) has many of the following
errors in it:
(OS 64)The specified network name is no longer
available. : winnt_accept: Asynchronous AcceptEx failed.
(OS 10054)An existing connection was forcibly closed by
the remote host. : core_output_filter: writing data to the network
and we have not been able to trace the cause yet. What are these errors
typically caused by?
They also get the error:
:Apache2 IO flush: (620018) APR does not understand this
error code at -e line 0
every 3 to 4 hours, followed by either
[notice] Parent: child process exited with status 9 --
Restarting.
(at which point Apache seems to have crashed and restarted itself (which
it is configured to do in the Service Control Manager)) or
[crit] Parent: child process exited with status 2 --
Aborting.
(at which point Apache definitely crashes for good and does not restart,
despite still being configured to do so).
Any clues what the causes might be?
RE: [users@httpd] What are OS64 and OS10054 errors typically caused by (Win32)
Posted by Steve Hay <St...@planit.com>.
Eric Covener wrote on 2010-10-15:
> On Fri, Oct 15, 2010 at 7:59 AM, Steve Hay <St...@planit.com> wrote:
>> (OS 64)The specified network name is no longer
>> available. : winnt_accept: Asynchronous AcceptEx failed.
>
> Try Win32DisableAcceptEX
We have tried that already, and
EnableMMAP off
EnableSendfile off
but it all made no difference.
>
>> (OS 10054)An existing connection was forcibly closed
>> by the remote host. : core_output_filter: writing data to the network
>>
>
> You've got most of the explanation in the error already, but further
> info at http://msdn.microsoft.com/en-us/library/ms740668(v=VS.85).aspx
Still doesn't give me much to go on. Strange thing is, the latest crash happened in the middle of the night (1:17am), on a site where they are not working at that hour. The access log shows activity up to 23:32pm the night before, and then nothing else at all until about 6am when Apache was restarted (manually).
What could make Apache just fall over of its own accord in the middle of the night?
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] What are OS64 and OS10054 errors typically caused
by (Win32)
Posted by Eric Covener <co...@gmail.com>.
On Fri, Oct 15, 2010 at 7:59 AM, Steve Hay <St...@planit.com> wrote:
> (OS 64)The specified network name is no longer available. :
> winnt_accept: Asynchronous AcceptEx failed.
Try Win32DisableAcceptEX
>
> (OS 10054)An existing connection was forcibly closed by the
> remote host. : core_output_filter: writing data to the network
>
You've got most of the explanation in the error already, but further
info at http://msdn.microsoft.com/en-us/library/ms740668(v=VS.85).aspx
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org