[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Could not read chunk size: connection was closed by server

From: Justin Johnson <justinandtonya_at_gmail.com>
Date: Fri, 18 Nov 2011 15:27:40 -0600


We are running Subversion 1.6.16 and Apache 2.2.17 on Solaris 10, with
1.6.12 clients connecting from Windows and various flavors of UNIX.
For as long as I can remember users on Windows and UNIX clients have
been getting the following error every once in a while, typically
during a checkout.

  Could not read chunk size: connection was closed by server

In the server logs the following errors appear around the same time.

  Provider encountered an error while streaming a REPORT response.  [500, #0]
  A failure occurred while driving the update report editor  [500, #130]
  Error writing base64 data: Software caused connection abort  [500, #130]

When the error happens you can generally just do an update in the
working copy and it will pick up where it left off.

The frequency of this error has been increasing lately so I'm trying
again to determine the cause. Numerous people have posted about it
online, but none of the solutions have seemed applicable to my
situation. For example, there are no signs of too many open file
descriptors and I have verified that the repositories are not corrupt.
 The time that it takes for the checkout to fail with this error shows
no linkage with our timeout settings in Apache as far as I can tell.
Sometimes it fails after about 20 seconds... other times 180 or so.
For what it's worth, the only two timeout settings we have are:

TimeOut 1800
KeepAliveTimeout 10

This page seemed potentially related, but I'm not sure. Our Solaris
box is actually a Sun zone, so there's some virtualization involved.


Does anyone have any suggestions?

Received on 2011-11-18 22:28:14 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.