Bug 32744 - (104)Connection reset by peer:ap_content_length_filter: apr_bucket_read() failed
Summary: (104)Connection reset by peer:ap_content_length_filter: apr_bucket_read() failed
Status: RESOLVED INVALID
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_auth (show other bugs)
Version: 2.0.52
Hardware: PC Linux
: P2 major (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL: http://yukongis.ca/bin/view/Sandbox/B...
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-17 07:12 UTC by matt wilkie
Modified: 2004-12-17 03:32 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description matt wilkie 2004-12-17 07:12:24 UTC
Hi All,

I hope you folks can help get to the bottom of "(104)Connection reset by
peer:ap_content_length_filter: apr_bucket_read() failed" errors in the apache
error log.

The error occurs when two conditions are met: 1) htaccess authentication is
turned on, and 2) a skin other than classic is being used.

Additionally, when the error condition is present, a Mozilla/Firefox user will
likely have their comment added although they may have to add comment or saved
their edit more than once (perhaps resulting in duplicate postings). An Internet
Explorer user on the other hand will probably not be able to comment or edit at
all -- after pressing the button the browser sits there 'receiving' indefinately.

The server environment is is Linux kernel 2.6.9, Apache/2.0.52, perl 5.8.3, and
TWiki 01 Sep 2004 $Rev: 1742 $. Mod_perl, speedycgi etc are not used or loaded.

I have STDERR redirected to a log file, but it doesn't produce any errors
related to this.

I am not the administrator of this machine, e.g. I cannot restart the apache
server, but I do have read access to the relevant configs if necessary and can
poke around via ssh.

A page which demonstrates the problem can be seen at:
http://yukongis.ca/bin/view/Sandbox/BucketFailure
and the same page using a skin which doesn't exhibit the problem:
http://yukongis.ca/bin/view/Sandbox/BucketFailure?skin=classic

Thank you in advance for any assistance you may be able to provide. 

I've spent a few hours on irc://irc.freenode.net/#apache where there was some
indication it might be a problem with authentication being asked for on linked
css files. There is nothing in my configuration to ask for authorisation on
these though. There are many other sites with very similar configurations to
mine which haven't reported this problem.

I did find an irc log of one person using Apache2 and TWiki which mentioned this
error. It went away when he changed from the worker config to pre-fork. This is
not an option for my host.

I've also sent a message very similar to this one to the apache users mailing
list, which didn't get a single reply.

Modules: (from apachectl -e debug)

[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module vhost_alias_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module env_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module log_config_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module mime_magic_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module mime_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module negotiation_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module status_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module info_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module include_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module autoindex_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module dir_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module cgid_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module asis_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module imap_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module actions_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module speling_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module userdir_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module alias_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module access_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module auth_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module auth_anon_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module auth_dbm_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module cern_meta_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module expires_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module headers_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module usertrack_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module unique_id_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module setenvif_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module ssl_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module rewrite_module
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module jk2_module
[Thu Dec 16 21:47:51 2004] [debug]
/tmp/jakarta-tomcat-connectors-4.1.24-src/jk/native2/server/apache2/mod_jk2.c(344):
mod_jk Create config for default server (null)\n
[Thu Dec 16 21:47:51 2004] [debug] mod_so.c(247): loaded module php5_module
Comment 1 matt wilkie 2004-12-17 07:16:09 UTC
the httpd.conf and .htaccess file is posted at
http://yukongis.ca/bin/view/Sandbox/BucketFailure. I can duplicate those here if
you like.
Comment 2 Nick Kew 2004-12-17 12:32:21 UTC
> The error occurs when two conditions are met: 1) htaccess authentication is
> turned on, and 2) a skin other than classic is being used.

That's enough to tell us it's an application problem somewhere.  Apache has no
notion of a "skin", classic or otherwise.  Look to whatever it is that gives you
"skins".  Except ... it seems to be a local issue ...

FWIW it worked for me, but showed config issues (authentication on submit, and
an apparent redirect) and badly mangled HTML.  Please reopen if you can fix your
problems and identify an issue in Apache.