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?
Check the apache error log, there should be an error logged in there with an error number. That number will help finding out why the connection was dropped.
If there's nothing in the error log, check your virus scanner/firewall settings: some of those tools will drop a connection if they think the transferred data is dangerous.
I get that also. Our server is Apache running on Windows. My client is connected with a high speed but somewhat high latency (200ms.) The other part of the puzzle is that I am running windows Vista. Turning autoscaling and rss seems to improve the situation, but does not fix it.
I was getting the "Could not read chunk size" message from clients on several machines.
The key to figuring it out was this error in the Apache error log:
[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]
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
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.
REPORT of '/svn/yunfiqun/!svn/vcc/default': Could not read chunk size: connection was closed by server (http://user11:81)
After a power failure,My repository is nearly crashed. above stated error is shown on Tortise SVN Checkout, even error is shown on 'show log', on working copy commit it also shows error.....
I think problem is same like http://toxicsoftware.com/subversion_repository_corrupted_again/
Is there any mechanism to recover corrupt repositories?
For us the problem was an a timeout on Apache. The update was taking about 15 minutes, but Apache timed out after 10 minutes, causing our SVN server to give the error you see. The final solution was to increase the timeout setting for Apache. We use VisualSVN server - for detailed instructions on how to change this setting, look here: http://adventuresindotnet.blogspot.com/2010/09/svn-trouble.html