You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2002/07/11 21:29:45 UTC

DO NOT REPLY [Bug 10712] New: - (57)Socket is not connected AND (32)Broken pipe

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10712>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

(57)Socket is not connected AND (32)Broken pipe

           Summary: (57)Socket is not connected AND (32)Broken pipe
           Product: Apache httpd-2.0
           Version: 2.0.36
          Platform: PC
        OS/Version: FreeBSD
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: abatko@cs.mcgill.ca


Ever since I turned the LogLevel from 'warn' to 'info',
I've received thousands of the following messages in httpd-error.log

``[info] (57)Socket is not connected: core_output_filter:
writing data to the network''

``[info] (32)Broken pipe: core_output_filter: writing
data to the network''

This can't be a good thing.  Please let me know if you need any
other information to be able to diagnose the problem better.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org