Chunk delimiter was invalid error.

[Ralph Lacy <rl...@crypticstudios.com>]

Greetings,

We are trying to track down a couple of problems we are having here at my company using SVN.

We have been using SVN quite happily for years, but starting a couple of weeks ago we started getting a number of errors.

Problem #1 generates errors on the client that look like this:

REPORT of '/svn/!svn/vcc/default': Chunk delimiter was invalid (http://code)

On the server side, it looks like this:

[Fri Nov 02 12:01:10 2012] [error] [client 172.31.99.13] Error writing base64 data: Software caused connection abort  [500, #103]


Problem #2 generates errors on the client that look like:

svn: E175002: Could not save file
svn: E175002: GET of '/svn/!svn/rvr/139915/dev/StarTrek/bin/browser/libcef.pdb':
Could not read response body: connection was closed by server (http://code)
svn: E175002: Error reading spooled REPORT request response

(We haven't found a corresponding error on the Server side.)

All of this seems to be somehow associated (by time correlation) to a large checkin we've done recently (some of the files were 200mb or so.)

We have tried updating to the latest available version of Subversion on the server (1.7.7), and the latest client (1.7.7).

What additional information would you need to help diagnose the issue?

I am not subscribed to the mailing list, so please be sure to CC me on responses.
rlacy@crypticstudios.com

Thanks!
-Ralph

Re: Chunk delimiter was invalid error.

[Philip Martin <ph...@wandisco.com>]

Ralph Lacy <rl...@crypticstudios.com> writes:

> Problem #1 generates errors on the client that look like this:
>
> REPORT of '/svn/!svn/vcc/default': Chunk delimiter was invalid (http://code)
>
> On the server side, it looks like this:
>
> [Fri Nov 02 12:01:10 2012] [error] [client 172.31.99.13] Error writing base64 data: Software caused connection abort  [500, #103]

http://subversion.tigris.org/issues/show_bug.cgi?id=2647

Possibly network related.  Perhaps Subversion should do better here but
it's hard until we identify the underlying problem.

> Problem #2 generates errors on the client that look like:
>
> svn: E175002: Could not save file
> svn: E175002: GET of '/svn/!svn/rvr/139915/dev/StarTrek/bin/browser/libcef.pdb':
> Could not read response body: connection was closed by server (http://code)
> svn: E175002: Error reading spooled REPORT request response
>
> (We haven't found a corresponding error on the Server side.)
>
> All of this seems to be somehow associated (by time correlation) to a large checkin we've done recently (some of the files were 200mb or so.)
>
> We have tried updating to the latest available version of Subversion on the server (1.7.7), and the latest client (1.7.7).
>
> What additional information would you need to help diagnose the issue?

Difficult to say.  Network traces might help, but really we need to know
why the server is closing the connection.

I note that the GET requests indicate that you are using the serf http
library, have you tried using neon instead?

-- 
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download