SVN错误运行上下文:远程主机强行关闭了现有连接 [英] SVN error running context: An existing connection was forcibly closed by the remote host
问题描述
我已经在可悲的是，我无法再从Windows 7计算机上提交回购协议.它失败，并显示以下错误消息:
Sadly, I can't commit anymore to the repo from my Windows 7 machine; it fails with the following error message:
Transmitting file data .svn: E730054: Commit failed (details follow):
svn: E730054: Error running context: An existing connection was forcibly closed
by the remote host.
TortoiseSVN和命令行客户端都出现了此错误.
I have had this error both with TortoiseSVN and the command line client.
这些是提交失败时服务器上/var/log/apache2/access.log的内容: access.log .
错误日志中没有相同的条目.
These are the contents of /var/log/apache2/access.log on the server for the time of the failed commit: access.log.
There is no entry for the same time in the error log.
我仍然可以检查回购的内容，并且svn info http://myurl/svn/myrepo也可以正常工作.
I'm still able to check out the contents of the repo and svn info http://myurl/svn/myrepo works also fine.
带有回购协议的Debian服务器在Windows Server 2008 R2(Hyper-V-Manager 6.1)上的VM内运行.使用FortiClient 4.2.8.0307建立了从Windows计算机到Windows Server的连接.
The Debian server with the repo is running inside a VM on a Windows Server 2008 R2 (Hyper-V-Manager 6.1). The connection from my Windows machine to the Windows Server is established using FortiClient 4.2.8.0307.
昨天遇到此错误后，我从服务器上清除了svn并再次设置了存储库.这使回购接受了几个小时的提交，直到再次因相同的错误而失败.
After I ran into this error yesterday, I purged svn from the server and setup the repo again. This made the repo accept commits for a couple of hours until it failed again with the same error.
当前再次使用TortoiseSVN提交工作，但由于命令行客户端而失败.
Currently commits work again with TortoiseSVN but fail with the command line client.
E730054是什么意思，我该如何对其进行永久性修复?
What does E730054 mean and how can I fix it for good?
在此期间，我已升级为杰西，但情况并没有改善. Commits with Tortoise再次停止工作，这意味着它在发送内容"操作处挂起大约五分钟，然后打印标题中的错误.
I have upgraded to Jessie in the meantime, but the situation did not improve. Commits with Tortoise stopped working again, meaning that it hangs at the "Sending Content" action for about five minutes and then prints the error that's in the title.
结帐仍然可以顺利进行.
Checkouts still work without a hitch, though.
apache2 -v:
伺服器版本:Apache/2.4.9(Debian)
服务器内部版本:2014年3月29日21:52:01
apache2 -v:
Server version: Apache/2.4.9 (Debian)
Server build: Mar 29 2014 21:52:01
svn --version:
svn版本1.8.8(r1568071)
在i486-pc-Linux-GNU上编译于2014年4月1日，03:41:42
svn --version:
svn, version 1.8.8 (r1568071)
compiled Apr 1 2014, 03:41:42 on i486-pc-Linux-GNU
这是一个线程，其中讨论了该错误，但我无法从中得出解决问题的方法.
Here's a thread that discusses the error, but I could not conclude a solution for my problem from it.
我注意到当我要提交文件的 second 修改时会出现问题.
I noticed that the problem occurs when I want to commit the second modification of a file.
使用 svnserve 而不是apache2后，该问题永久消失. 本教程对我有帮助设置它.
The issue went away permanently after using svnserve instead of apache2. This tutorial helped me set it up.
推荐答案
在我阅读线程时，客户端站点上WEBDAV实现中的某些问题似乎使apache线程崩溃.我在1.8版之前的存储库中还有其他问题，我通过将整个存储库转储/重新加载到一个新的存储库中解决了大多数问题(使用" svnadmin upgrade "是不够的！). 1.8版之前的版本库有时在修订文件中包含损坏/过时"的数据，客户端会忽略这些数据.看来这可能导致段错误.
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
请注意，执行更新/重新加载周期可能会花费大量时间(大约1GB/h +-50％，主要取决于磁盘速度).
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.
这篇关于SVN错误运行上下文:远程主机强行关闭了现有连接的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
