Presumably, tcpdump/wireshark of the response headers will be useful.
(no time to dive deeply into this right now, sorry)
Fridtjof Busse wrote on Tue, Mar 06, 2012 at 12:44:06 +0100:
> answering my own post:
> * Fridtjof Busse <fbusse_at_gmx.de>:
> > The httpd process starts consuming up to 4GB and then dies, killing the
> > svn client process with:
> > svn: REPORT of '/svn/prod/!svn/vcc/default': Could not read chunk size:
> > connection was closed by server
> Setting the configuration to
> SVNAllowBulkUpdates Off
> seems to solve the memory consumption problem, but makes checking the repo out completly impossible.
> SVN dies like this:
> svn: GET of '/svn/prod/!svn/ver/4634/source/python26-PyYAML/trunk/PyYAML-3.10/ext/_yaml.c': Error reading response headers: Line too long
> Apache logs this:
> [Tue Mar 06 12:39:25 2012] [error] [client <snip>] Unable to deliver content. [500, #0]
> [Tue Mar 06 12:39:25 2012] [error] [client <snip>] (104)Connection reset by peer: Could not write data to filter. [500, #0]
> [Tue Mar 06 12:39:25 2012] [error] [client <snip>] Provider encountered an error while streaming a REPORT response. [500, #0]
> [Tue Mar 06 12:39:25 2012] [error] [client <snip>] A failure occurred while driving the update report editor [500, #103]
> Any ideas?
> Please CC me, thanks.
> NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone!
> Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
Received on 2012-03-07 09:46:54 CET