When I attempt to checkout:
svn checkout svn+ssh://serveradmin%foo@foo.com/home/87292/data/svn/repository/trunk .
I get this (unhelpful) er
This can happen due to an authentication failure. You may have cached credentials that do not match the site you're trying to access. You may need to register an SSH key with the site.
As suggested by the notalbert below, use SVN_SSH flag to get the detailed error in verbose mode
export SVN_SSH="ssh -v "
You might see some output like this on stderr
,
Add correct host key in /home/jcrawford/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /home/jcrawford/.ssh/known_hosts:4
remove with: ssh-keygen -f "/home/jcrawford/.ssh/known_hosts" -R 192.168.0.107
ECDSA host key for 192.168.0.107 has changed and you have requested strict checking.
Host key verification failed.
remove the line entry belonging to your svn server IP address, in my case it is 192.168.1.107, from the file ~/.ssh/known_hosts
I had kept getting error above with ssh trying to connect using default port 22. issue resolved after specifying correct port for the host.
One other reason for getting this "svn: Network connection closed unexpectedly" error which I came across was that the /var was full , which caused for svn in not being able to write anything to disk. so maybe first check your disk space (du -m) before proceeding with the above steps ?
I was connecting to a local network svn and this happened to me from some point on (it actually happens periodically).
All the references I have found surfing mention something related with SSH. SSH may well be the root of my problem too somehow, but I managed to overcome the problem by killing some of the svnserve processes.
I can do this because I know what is the usage of my server, but don't know the relevance of doing this in a server with more concurrence.
I suspect Joel and Andy have it right.
You can use the ssh verbose flag to help figure out these kind of problems.
export SVN_SSH="ssh -v "
svn checkout svn+ssh://serveradmin%foo/blah blah blah
I had this same error, but for committing a revision. Clearing out .ssh/known_hosts fixed the problem because the SSH keys went stale.