SVN error running context: An existing connection was forcibly closed by the remote host

Question

I\'ve created an SVN repo on my Debian Wheezy build server following this tutorial. svn --version gives 1.6.17.

Sadly, I can\'t commit anymore

Answer 1

I had this problem with a single file while attempting to check in multiple files using Tortoise SVN on Windows 7 x64. Several attempts to commit the file using a variety of different versions of Tortoise SVN and the command-line version of SVN failed.

At the time, my laptop was using my home ISP internet connection. When I later went to work and attempted to commit the failing file from my employer's network, the file was committed without a problem.

I don't know why that was the case, but if you encounter this problem and find your way to this answer through a search engine query, you may want to try again – using a different internet connection. While not a solution to the problem, it may provide a temporary work-around.

Answer 2

As I was reading over the thread, it seems like some problems in the WEBDAV implementation on client site crashing the apache-thread. I had other issues with pre 1.8 repositories and I solved most of them by dump/reload the whole repository into a new one (using "svnadmin upgrade" is not sufficient!). Pre 1.8 repos have sometimes "corrupt/obsolete" data in revision files which is ignored by clients. It seems that this could cause the segfault.

You can dump/reload your repository like this:

svnadmin create newrepos
svnadmin dump oldrepos | svnadmin load newrepos

Note that it could take a tremendous amount of time to perform an update/reload cycle (approx. 1GB/h +- 50% depending mostly on disk speed).

If you have a different time, please post your time, I am doing a private research of dump/reload cycle performances.

Answer 3

I too had this issue in SVN client. I cleared the temp folders in windows. Then cleared all data including auth details from "saved data" in SVN settings. Then retried in SVN, it asked for authentication and it opened fine without any error.

Answer 4

I too faced the similar issue. SVN details: TortoiseSVN 1.12.0, Build 28568 - 64 Bit

Solution: Go to task manager and search for Tortoise SVN cache service, end this task and retry to update/commit the changes.