Apache 2 problem (32)Broken pipe: core_output_filter: writing data to the network

Add this into your apache config file:

Code:

EnableSendfile Off

Ref: http://httpd.apache.org/docs/2.0/mod/core.html#enablesendfile

Sometimes when you compile Apache it will set this to on, even though your OS doesn't really support it. Turning it off should solve the problem if this was the case.

 

Are you experiencing actual problems or are you just reading this from a log and assuming there is a problem?

Connection reset by peer is a standard internet error.

It happens when a users connection to the server is cut in the middle of whatever they were doing. Lots of things can cause this, easiest one is closing the browser window/tab before the page load is complete.

It usually is nothing to be concerned about.

 

@hostultra: Thanks for the input, I know that is a normal log message under normal circumstances. Thought I was experiencing same thing as Dog was - practically every user giving that error message, including myself. Log was filling up and didn't seem normal.

After looking around I saw their notice about recent compilations and sometimes falsely reading SendFile as compatible when it wasn't. Made the change here and it cut down my errors by well over half. Still seeing some but nowhere near the volume I was previously experiencing.

 

i have php 5.2.4 and apache 2.6.6. my httpd.conf did NOT include the EnableSendfile parameter either (as well as KeepAlive, etc. I had to put these parameters by myself and i have NO clue if they are actually working. If anyone knows how can i test it, i would appreciate it). Although i put it inside httpd.conf with value off, and restarted apache (after running /usr/local/cpanel/bin/apache_conf_distiller --update --main) i keep getting the same error in my logs. [Thu Nov 01 15:01:19 2007] [info] [client 127.0.0.1] (32)Broken pipe: core_output_filter: writing data to the network

This is annoying since i get about an extra 2-3mb log per day. How can that be fixed for good?

 

[Thu Nov 01 20:27:04 2007] [info] [client 219.89.165.119] (104)Connection reset by peer: core_output_filter: writing data to the network
[Thu Nov 01 20:27:04 2007] [info] [client 219.89.165.119] (104)Connection reset by peer: core_output_filter: writing data to the network
[Thu Nov 01 20:27:05 2007] [info] [client 219.89.165.119] (104)Connection reset by peer: core_output_filter: writing data to the network
[Thu Nov 01 20:27:05 2007] [info] [client 89.44.192.232] (104)Connection reset by peer: core_output_filter: writing data to the network


same thing here, with enablesendfile off .... i would really love to know more about this.

 

does anyone have a solution for that?? its getting really annoying..

 

I'm running WHM 11.2.0, cPanel 11.11.0-S16999, CENTOS Enterprise 4.5 i686 - WHM X v3.1.0, Apache version 2.2.6 (Unix), PHP version 5.2.2, and MySQL version 5.0.27-standard.

I'm having the same problem with literally hundreds of these broken pipe messages per day but the twist for me is that many of them are generated by 127.0.0.1, which is the server itself:

EnableSendFile and KeepAlive were missing from my httpd.conf, too, but adding them doesn't seem to solve the problem. If it's an error in compiling Apache, would re-compiling help? I've searched the forums, Apache's site, and Google without finding a solution. Anyone?

Thanks

 

In my case, the server has been using so many resources it was crashing every day, so I have been trying to remove unnecessary services and fix anything that might be increasing the load on the server.

It seems like if a lot of these broken pipe messages are generated by the server itself abandoning connections, it would be worth pursuing.

 

same applies for me. this things is eating up too much of my resoucrces and generates an error file that grows by 3-5mb every day. i understand that its not really a problem. but why would i want this thing to cause me a huge error log and make it difficult for me to trace more serious problems?

 

Here's what solved the broken pipe problem for me:

Recompile Apache with PHP version 5.2.2 and "versioning" unchecked and "Reset Apache Config to Default" checked.

My broken pipe messages are gone. Of course, now I have a new error message:

That's next on my list.

I went the route of a recompile because the httpd.conf I had didn't resemble the ones I read about here on the forums and was missing the KeepAlive and EnableSendFile.

So far, no crashes, but it's too early to tell if that's permanent.

 

let me know how that goes.. this file keeps growing and growing, and it makes it sooo hard to trace problems.. anyways, i hope there is a fix soon for that.

 

Okay, here's the fix for the

message.

Use SSH to log in to your server as root. Use your favorite editor to edit /usr/local/apache/conf/httpd.conf. Find the section that looks like this:

Code:

#<Location /server-status>
#    SetHandler server-status
#    Order deny,allow
#    Deny from all
#    Allow from .example.com
#</Location>

In my case, as you can see above, it was commented out. The guys at cPanel told me to add the following:

Then restart Apache. It got rid of the messages for me as it allowed Apache to find the necessary file.

I suspect, though I don't know this for sure, that if you're using an older version of Apache and getting a similar error message, but for "server-status" instead of "whm-server-status" you might get the same result; i.e., fix the message, by just un-commenting the existing location setting.