httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Warnier ...@ice-sa.com>
Subject Re: [users@httpd] core_output_filter errors... 404s on the site.
Date Fri, 06 Nov 2009 08:19:02 GMT
Vasiliy Boulytchev wrote:
> Dear Apache Users...
> 
> We are seeing this in our web logs... along with users receiving 404s on the
> site... The site is a php/mysql application.
> 
> [Fri Nov 06 00:52:31 2009] [info] [client 67.195.115.125] (32)Broken pipe:
> core_output_filter: writing data to the network
> [Fri Nov 06 00:52:32 2009] [info] [client 67.195.115.125] (32)Broken pipe:
> core_output_filter: writing data to the network
> [Fri Nov 06 00:52:32 2009] [info] [client 67.195.115.125] (32)Broken pipe:
> core_output_filter: writing data to the network
> [Fri Nov 06 00:52:32 2009] [info] [client 67.195.115.125] (32)Broken pipe:
> core_output_filter: writing data to the network
> [Fri Nov 06 00:52:33 2009] [info] [client 67.195.115.125] (32)Broken pipe:
> core_output_filter: writing data to the network
> [Fri Nov 06 00:52:34 2009] [info] [client 65.55.106.230] (104)Connection
> reset by peer: core_output_filter: writing data to the network
> [Fri Nov 06 00:52:36 2009] [info] [client 67.195.114.249] (32)Broken pipe:
> core_output_filter: writing data to the network
> [Fri Nov 06 00:52:37 2009] [info] [client 65.55.106.203] (104)Connection
> reset by peer: core_output_filter: writing data to the network
> [Fri Nov 06 00:52:37 2009] [info] [client 74.69.0.152] (32)Broken pipe:
> core_output_filter: writing data to the network
> [Fri Nov 06 00:55:52 2009] [info] [client 74.100.12.135] (32)Broken pipe:
> core_output_filter: writing data to the network
> [Fri Nov 06 00:56:18 2009] [info] [client 74.100.12.135] (32)Broken pipe:
> core_output_filter: writing data to the network
> [Fri Nov 06 00:57:26 2009] [info] [client 93.23.15.202] (70007)The timeout
> specified has expired: core_output_filter: writing data to the network
> [Fri Nov 06 00:57:37 2009] [info] [client 122.249.242.130] (70007)The
> timeout specified has expired: core_output_filter: writing data to the
> network
> [Fri Nov 06 00:58:50 2009] [info] [client 65.48.150.43] (32)Broken pipe:
> core_output_filter: writing data to the network
> [Fri Nov 06 00:58:58 2009] [info] [client 112.135.234.199] (104)Connection
> reset by peer: core_output_filter: writing data to the network
> [Fri Nov 06 00:59:09 2009] [info] [client 93.23.15.202] (32)Broken pipe:
> core_output_filter: writing data to the network
> [Fri Nov 06 00:59:33 2009] [info] [client 112.135.234.199] (104)Connection
> reset by peer: core_output_filter: writing data to the network
> 
> 
Forget the user-experienced 404 messages for a moment..

What you are seeing in the logs above is nothing really exceptional.
It means what it says : the server tried to send a response to the 
client, but the client was not there anymore.
That can happen when a user clicks the CANCEL or BACK button, or clicks 
on another link before this page is fully loaded.
A lot of users do that, all the time.  They just can not stop themselves 
from clicking all over.
Particularly if your site is slow to send the response to the user.

And in your log above, sometimes there are a few seconds between such 
events, and sometimes a few minutes.

This being said, it can also be that there is some problem in your 
network : for example a router or switch or firewall which closes the 
connections when it should not.

You need to run a tool like wireshark on a user station, to find out 
what happens, and how come the connection gets closed before pages are 
finished loading.

Now about the user 404 status.
You need to check in your access log, and error log, if the 404 
responses happen together with the broken pipes.
I think a 404 is a server response which means "the requested 
object/page does not exist".  It seems a bit strange that this would 
occur together with a broken connection.  I mean, if the server can send 
a 404 response to the client, then obviously the connection is not broken.
Or else, where does that 404 response come from ? a proxy ?
Installing a browser add-on like HttpFox (for Firefox) or Fiddler2 (for 
IE) would also help, on the client side, to see precisely what happens.

---------------------------------------------------------------------
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


Mime
View raw message