从svn存储库更新返回“无法读取块大小”错误 [英] Updating from svn repository returns "Could not read chunk size" error

问题描述

使用tortoise svn client从subversion存储库进行更新时出现如下错误：

When updating from subversion repository using tortoise svn client I get error looking like that:

Could not read chunk size: An existing connection was forcibly closed by the remote host.

它不会阻止我更新，只是中断更新过程，

It doesn't prevent me from updating, just interrupts update process, so that I have to repeat update several times, before it is complete.

可能会导致此类行为以及如何解决此问题？

What can cause such behaviour and how to fix it?

推荐答案

我在几台机器上从客户端收到无法读取大块大小消息。

I was getting the "Could not read chunk size" message from clients on several machines.

错误日志：

[Fri May 07 14:26:26 2010] [error] [client 155.35.175.50] Provider encountered an error while streaming a REPORT response.  [500, #0]
[Fri May 07 14:26:26 2010] [error] [client 155.35.175.50] Problem replaying revision  [500, #24]
[Fri May 07 14:26:26 2010] [error] [client 155.35.175.50] Can't open file '/usr/site/svnrep/impc/db/revs/16122': Too many open files  [500, #24]

处理svn操作的Apache进程运行的文件描述符。在我的Ubuntu服务器上，我通过编辑 /etc/security/limits.conf 修改它，并将其添加到底部：

The Apache process handling the svn operation was running out of file descriptors. On my Ubuntu server, I fixed it by editing /etc/security/limits.conf and adding this at the bottom:

*               hard    nofile          5000
*               soft    nofile          5000

这会将文件描述符限制从1024增加到5000.然后，我登录了一个新的shell，并确认限制已通过 ulimit -n 增加。然后重新启动Apache。

Which increases the file descriptor limit from 1024 to 5000. Then I logged in on a fresh shell and confirmed that the limit got increased via ulimit -n. Then restarted Apache.

这篇关于从svn存储库更新返回“无法读取块大小”错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！