httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Hay" <Steve...@planit.com>
Subject [users@httpd] What are OS64 and OS10054 errors typically caused by (Win32)
Date Fri, 15 Oct 2010 11:59:29 GMT
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?


Mime
View raw message