Re: SSH+SVN - svn: Connection closed unexpectedly

On Wed, 05 Jan 2005 15:37:52 +0100, Vincent Ducret
<Vincent.Ducret@sun.com> wrote:
> Each svn command started from the Solaris client, e.g.
> svn list svn+ssh://192.168.3.33/repo/projectXXX,
> got the following message:
> "svn: Connection closed unexpectedly"
> after the SSH authentication step

I've had similar symptoms several times, when setting up svn+ssh for
use with TortoiseSVN, so my solution may be applicable here :)

Basically SSH can be invoked two ways:

1) ssh user@host

   Which simply connects and starts an interactive shell. This of
course ensures you get all your environment variables as per expected
and thus probably have svn and (importantly) svnserve in your path.

2) ssh user@host command

   Which connects and runs the given command. This is the way that
Subversion connects (where the command is 'svnserve'). This way,
however, does not start an interactive shell, and may therefore have
less than the full environement; specifically the path may not include
svn and svnserve.

You need to test the command

   ssh 192.168.3.33 svnserve

Does is terminate with

A) an error message from svnserve (something along the lines of "You
must specify one of -d, -i, -t or -X. Type 'svnserve --help' for
usage.") or with

B) an error message from ssh (something along the lines of "svnserve:
Command not found").

If (A) then your problem isn't the path and I can't help you. If (B)
then your problem probably is the path and you need to make sure that
the path to svnserve is present for such logins. (How you do that, on
a Solaris box, I do not know, unfortunately...)

Hope this helps.

- Uffe

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 6 00:39:52 2005