On 27.09.2014 09:24, Mohsin Abbas wrote: > HI Philip Martin, > > Here is Tortoise SVN client and Apache error log portion : > > *Tortoise SVN Client Error :* > > Error: Commit failed (details follow): > Error: PUT of > Error: > '/svn/test/!svn/wrk/6f036c59-c3a8-5947-91dd-bd0f1eeccd84/SomeFolder/brands.zip': > > Error: Could not send request body: An existing connection was > forcibly closed by the > Error: remote host. > Error: (http://x.x.com) > > *Apache error.log portion :* > > [Sat Sep 27 11:21:44 2014] [error] [client x.x.x.x] mod_dav_svn > close_stream: error closing write stream [500, #185004] > [Sat Sep 27 11:21:44 2014] [error] [client x.x.x.x] Unexpected end of > svndiff input [500, #185004]
>From the above, I'm almost certain that this is not Subversion's fault. Look at the error messages: the client thinks that the server closed the connection, but the server thinks that the client closed the connection; so the only reasonable explanation is that something *between* the client and server is in fact closing the connection. This could be a proxy, or a load balancer, or even a packet inspector/firewall (see http://markmail.org/message/tazxq3jexaopcdum for example) that's forcibly closing the connection. You'll have to talk to the server/site administrators to determine what's happening. There's not much anyone else can do without knowing how not just the server, but the whole data-centre are configured. -- Brane