You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Mark Steele <ho...@belent.com> on 1999/08/14 20:38:12 UTC

os-linux/4861: clients receiving connection reset by peer at seemingly random intervals

>Number:         4861
>Category:       os-linux
>Synopsis:       clients receiving connection reset by peer at seemingly random intervals
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sat Aug 14 11:40:00 PDT 1999
>Last-Modified:
>Originator:     hostmaster@belent.com
>Organization:
apache
>Release:        1.3.6
>Environment:
Linux ratbert 2.3.8 #3 SMP Mon Jul 26 13:26:19 EDT 1999 i686 unknown
gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
glibc 2.1
openssl-0.9.4
mod_ssl 2.3.11
Server version: Apache/1.3.6 (Unix)
Server built:   Aug 14 1999 12:15:45
./httpd -V
Server version: Apache/1.3.6 (Unix)
Server built:   Aug 14 1999 12:15:45
Server's Module Magic Number: 19990320:0
Server compiled with....
 -D EAPI
 -D HAVE_MMAP
 -D HAVE_SHMGET
 -D USE_SHMGET_SCOREBOARD
 -D USE_MMAP_FILES
 -D USE_FCNTL_SERIALIZED_ACCEPT
 -D HTTPD_ROOT="/usr/local/apache"
 -D SUEXEC_BIN="/usr/local/apache/bin/suexec"
 -D SHARED_CORE_DIR="/usr/local/apache/libexec"
 -D DEFAULT_PIDLOG="logs/httpd.pid"
 -D DEFAULT_SCOREBOARD="logs/httpd.scoreboard"
 -D DEFAULT_LOCKFILE="logs/httpd.lock"
 -D DEFAULT_XFERLOG="logs/access_log"
 -D DEFAULT_ERRORLOG="logs/error_log"
 -D TYPES_CONFIG_FILE="conf/mime.types"
 -D SERVER_CONFIG_FILE="conf/httpd.conf"
 -D ACCESS_CONFIG_FILE="conf/access.conf"
 -D RESOURCE_CONFIG_FILE="conf/srm.conf"
>Description:
At seemingly random intervals, clients receive error messages like:
Connection reset by peer
or certain parts of web pages fail to load (eg: 20% of images load, the rest show broken images). The server error logs show no indication of what's going on, and it is nowhere near being overloaded with around 8 requests/second and .0131% CPU load
>How-To-Repeat:
Due to the seemingly random nature of the problem, it is a bit difficult to reproduce. You can try: http://partyman.qc.ca
to see if you can reproduce it.
>Fix:
>From what I've been able to gather, I believe this is either a problem with glibc 2.1 or openssl. I have a few servers setup with libc5 which have never had so much as a hiccup, and I've had a few problems with different software packages and glibc 2.1
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]