Updating from svn repository returns "Could not read chunk size" error

Viewed 63921

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?

13 Answers

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 changed to an Ubuntu server and we had this same error - across multiple client PC's, OS's, and client versions.

After making sure that both the file limit settings and Apache timeout settings were as suggested.

(See http://posidev.com/blog/2009/06/04/set-ulimit-parameters-on-ubuntu/ )

I eventually solved the problem by using the apache2-mpm-prefork package rather than the apache2-mpm-worker package.

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.

Related