Occasional svn: E170013: Unable to connect to a repository at URL 'https://svn.....' svn: E730054: Error running context

Question

I need help with svn errors E170013 and E730054:

When executing the command "svn checkout..." in command line, I get the error

svn: E170013: Unable to connect to a repository at URL 'https://svn.....'
svn: E730054: Error running context: An existing connection was forcibly closed
by the remote host.

However, if I run the same command right after (only in the next 3 minutes), the command is executed successfully without errors, and the source code is checked out successfully.

Otherwise after 3 minutes (approximately), if I want to checkout again I need to run the svn checkout command, get the errors E170013 and E730054, then run the same command again and the svn checkout works again.

It seems to me that after a certain period of time (3min in my case) the socket between the svn client and svn server is closed, and trying to checkout and/or getting these errors is what actually triggers the connection to be reopened again.

In other words, my issue is that in order to perform an svn checkout, the first will always fail, and only next trys will succeed. After a period of time I need to repeat the same steps again and always do two "svn checkout" so the second one works.

My interpretation may be wrong but this is the behavior I get. I hope you got my issue.

I would like please to understand why such svn behavior, what causes these errors and how can I solve the issue.

SVN server version: 1.8.13 (r1667537) compiled Mar 20 2015, 11:32:18 on x86_64-unknown-linux-gnu 

SVN client version: 1.9.3 (r1718519) compiled Dec 22 2015, 09:12:06 on x86_64-microsoft-windows6.2.9200

SVN Client running on Windows Server 2008 R2 and SVN server in linux machine. 

Please feel free to ask any question. I would be happy to provide you more information.

Thank you so much in advance.

Answer 1

I finally found the solution.

Instead of writing down the link https://svn..... in the svncheckout command, I used the numeric IP address (e.g. 192.168.73.39) of the server instead of its hostname and it worked.

I hope this helps someone.