Re: SVN Commit Failed For Data larger Than 2 GB [How To Resolve]

Branko ÄŒibej <brane_at_wandisco.com> writes:

>> [Sat Sep 27 11:21:44 2014] [error] [client x.x.x.x] mod_dav_svn
>> close_stream: error closing write stream [500, #185004]
>> [Sat Sep 27 11:21:44 2014] [error] [client x.x.x.x] Unexpected end of
>> svndiff input [500, #185004]
>
> From the above, I'm almost certain that this is not Subversion's fault.
> Look at the error messages: the client thinks that the server closed the
> connection, but the server thinks that the client closed the connection;
> so the only reasonable explanation is that something *between* the
> client and server is in fact closing the connection.

Error 185004 is SVN_ERR_SVNDIFF_UNEXPECTED_END and that could be caused
by some proxy/router closing the connection. But it could also be
caused by a Subversion bug that causes the client to write invalid
svndiff data. It's not trivial to distinguish one from the other, we
would need access to all the commit data to decode the svndiff. Another
way would be to attempt the commit from the server itself over HTTP to
localhost, if this works the problem is most likely the network.

-- 
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*