You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Greg Brown <gb...@trailbound.net> on 2008/02/03 19:55:06 UTC
svn+ssh commit closed unexpectedly
I'm encountering a strange problem with using SVN over a SSH tunnel. I've
got a SVN server set up on my local network which I connect to via svn+ssh.
Both my client machine and the server are running Ubuntu linux.
I've got public/private authentication set up and can access the server just
fine via SSH. I can also run most svn commands. log, co, up, list all work
fine. The problem comes when I try to ci. If I try to commit changes, I
constantly get the message:
svn: Commit failed (details follow):
svn: Connection closed unexpectedly
and the commit fails. Strange thing is that it has been working fine in the
past. I expect some package I upgraded has caused something to change,
which caused this to now fail, but I've no idea what could have caused this.
I set the ssh loglevel to debug3 and got the following when trying to do the
commit:
debug1: Authentication succeeded (publickey).
debug2: fd 4 setting O_NONBLOCK
debug2: fd 5 setting O_NONBLOCK
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug1: Entering interactive session.
debug2: callback start
debug2: client_session2_setup: id 0
debug1: Sending environment.
debug3: Ignored env SSH_AGENT_PID
debug3: Ignored env SHELL
debug3: Ignored env DESKTOP_STARTUP_ID
debug3: Ignored env TERM
debug3: Ignored env XDG_SESSION_COOKIE
debug3: Ignored env GTK_RC_FILES
debug3: Ignored env WINDOWID
debug3: Ignored env USER
debug3: Ignored env LS_COLORS
debug3: Ignored env SSH_AUTH_SOCK
debug3: Ignored env GNOME_KEYRING_SOCKET
debug3: Ignored env SESSION_MANAGER
debug3: Ignored env USERNAME
debug3: Ignored env PATH
debug3: Ignored env DESKTOP_SESSION
debug3: Ignored env GDM_XSERVER_LOCATION
debug3: Ignored env PWD
debug1: Sending env LANG = en_US.UTF-8
debug2: channel 0: request env confirm 0
debug3: Ignored env GNOME_KEYRING_PID
debug3: Ignored env GDM_LANG
debug3: Ignored env GDMSESSION
debug3: Ignored env HISTCONTROL
debug3: Ignored env SHLVL
debug3: Ignored env HOME
debug3: Ignored env GNOME_DESKTOP_SESSION_ID
debug3: Ignored env LOGNAME
debug3: Ignored env XDG_DATA_DIRS
debug3: Ignored env DBUS_SESSION_BUS_ADDRESS
debug3: Ignored env LESSOPEN
debug3: Ignored env WINDOWPATH
debug3: Ignored env DISPLAY
debug3: Ignored env LESSCLOSE
debug3: Ignored env COLORTERM
debug3: Ignored env XAUTHORITY
debug3: Ignored env OLDPWD
debug3: Ignored env _
debug1: Sending command: svnserve -t
debug2: channel 0: request exec confirm 0
debug2: fd 3 setting TCP_NODELAY
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel 0: rcvd adjust 131072
Sending detailed-budget.scm
Transmitting file data .debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug2: channel 0: obuf empty
debug2: channel 0: close_write
debug2: channel 0: output drain -> closed
debug1: client_input_channel_req: channel 0 rtype exit-signal reply 0
debug2: channel 0: rcvd close
debug2: channel 0: close_read
debug2: channel 0: input open -> closed
debug3: channel 0: will not send data after close
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
#0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cfd -1)
debug3: channel 0: close_fds r -1 w -1 e 6 c -1
debug1: fd 0 clearing O_NONBLOCK
debug1: fd 1 clearing O_NONBLOCK
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.3 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status -1
svn: Commit failed (details follow):
svn: Connection closed unexpectedly
Has anyone ever seen this happen? If anyone has suggestions on where I can
start poking around to try and figure out what's wrong, I'd be most
appreciative. At this point, I've tried a bunch of suggestions from various
web forums, the SVN manual, and the users mailing list but to no avail.
Thanks,
Greg
Re: svn+ssh commit closed unexpectedly
Posted by phelixxx <fe...@web.de>.
I had a similar problem, also under ubuntu, but without the SSH tunnel. As it
did for you, the dump+load method did solve the problem without discovering
the cause.
before this I had to do a svnadmin recover REPOS.
the recency of your mail could indicate that the problem has /some/
correspondence to a recent software update.
thanks, felix
Greg Brown-3 wrote:
>
> I'm encountering a strange problem with using SVN over a SSH tunnel. I've
> got a SVN server set up on my local network which I connect to via
> svn+ssh.
> Both my client machine and the server are running Ubuntu linux.
>
> I've got public/private authentication set up and can access the server
> just
> fine via SSH. I can also run most svn commands. log, co, up, list all
> work
> fine. The problem comes when I try to ci. If I try to commit changes, I
> constantly get the message:
>
> svn: Commit failed (details follow):
> svn: Connection closed unexpectedly
>
>
> and the commit fails. Strange thing is that it has been working fine in
> the
> past. I expect some package I upgraded has caused something to change,
> which caused this to now fail, but I've no idea what could have caused
> this.
>
>
--
View this message in context: http://www.nabble.com/svn%2Bssh-commit-closed-unexpectedly-tp15257467p15309441.html
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn+ssh commit closed unexpectedly
Posted by Greg Brown <gb...@trailbound.net>.
On Feb 3, 2008 2:55 PM, Greg Brown <gb...@trailbound.net> wrote:
> I'm encountering a strange problem with using SVN over a SSH tunnel. I've
> got a SVN server set up on my local network which I connect to via svn+ssh.
> Both my client machine and the server are running Ubuntu linux.
>
> I've got public/private authentication set up and can access the server
> just fine via SSH. I can also run most svn commands. log, co, up, list all
> work fine. The problem comes when I try to ci. If I try to commit changes,
> I constantly get the message:
>
> svn: Commit failed (details follow):
> svn: Connection closed unexpectedly
>
>
> and the commit fails. Strange thing is that it has been working fine in
> the past. I expect some package I upgraded has caused something to change,
> which caused this to now fail, but I've no idea what could have caused this.
>
> I set the ssh loglevel to debug3 and got the following when trying to do
> the commit:
>
> debug1: Authentication succeeded (publickey).
> debug2: fd 4 setting O_NONBLOCK
> debug2: fd 5 setting O_NONBLOCK
> debug1: channel 0: new [client-session]
> debug3: ssh_session2_open: channel_new: 0
> debug2: channel 0: send open
> debug1: Entering interactive session.
> debug2: callback start
> debug2: client_session2_setup: id 0
> debug1: Sending environment.
> debug3: Ignored env SSH_AGENT_PID
> debug3: Ignored env SHELL
> debug3: Ignored env DESKTOP_STARTUP_ID
> debug3: Ignored env TERM
> debug3: Ignored env XDG_SESSION_COOKIE
> debug3: Ignored env GTK_RC_FILES
> debug3: Ignored env WINDOWID
> debug3: Ignored env USER
> debug3: Ignored env LS_COLORS
> debug3: Ignored env SSH_AUTH_SOCK
> debug3: Ignored env GNOME_KEYRING_SOCKET
> debug3: Ignored env SESSION_MANAGER
> debug3: Ignored env USERNAME
> debug3: Ignored env PATH
> debug3: Ignored env DESKTOP_SESSION
> debug3: Ignored env GDM_XSERVER_LOCATION
> debug3: Ignored env PWD
> debug1: Sending env LANG = en_US.UTF-8
> debug2: channel 0: request env confirm 0
> debug3: Ignored env GNOME_KEYRING_PID
> debug3: Ignored env GDM_LANG
> debug3: Ignored env GDMSESSION
> debug3: Ignored env HISTCONTROL
> debug3: Ignored env SHLVL
> debug3: Ignored env HOME
> debug3: Ignored env GNOME_DESKTOP_SESSION_ID
> debug3: Ignored env LOGNAME
> debug3: Ignored env XDG_DATA_DIRS
> debug3: Ignored env DBUS_SESSION_BUS_ADDRESS
> debug3: Ignored env LESSOPEN
> debug3: Ignored env WINDOWPATH
> debug3: Ignored env DISPLAY
> debug3: Ignored env LESSCLOSE
> debug3: Ignored env COLORTERM
> debug3: Ignored env XAUTHORITY
> debug3: Ignored env OLDPWD
> debug3: Ignored env _
> debug1: Sending command: svnserve -t
> debug2: channel 0: request exec confirm 0
> debug2: fd 3 setting TCP_NODELAY
> debug2: callback done
> debug2: channel 0: open confirm rwindow 0 rmax 32768
> debug2: channel 0: rcvd adjust 131072
> Sending detailed-budget.scm
> Transmitting file data .debug2: channel 0: rcvd eof
> debug2: channel 0: output open -> drain
> debug2: channel 0: obuf empty
> debug2: channel 0: close_write
> debug2: channel 0: output drain -> closed
> debug1: client_input_channel_req: channel 0 rtype exit-signal reply 0
> debug2: channel 0: rcvd close
> debug2: channel 0: close_read
> debug2: channel 0: input open -> closed
> debug3: channel 0: will not send data after close
> debug2: channel 0: almost dead
> debug2: channel 0: gc: notify user
> debug2: channel 0: gc: user detached
> debug2: channel 0: send close
> debug2: channel 0: is dead
> debug2: channel 0: garbage collecting
> debug1: channel 0: free: client-session, nchannels 1
> debug3: channel 0: status: The following connections are open:
> #0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cfd -1)
>
> debug3: channel 0: close_fds r -1 w -1 e 6 c -1
> debug1: fd 0 clearing O_NONBLOCK
> debug1: fd 1 clearing O_NONBLOCK
> debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.3 seconds
> debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
> debug1: Exit status -1
> svn: Commit failed (details follow):
> svn: Connection closed unexpectedly
>
>
>
> Has anyone ever seen this happen? If anyone has suggestions on where I
> can start poking around to try and figure out what's wrong, I'd be most
> appreciative. At this point, I've tried a bunch of suggestions from various
> web forums, the SVN manual, and the users mailing list but to no avail.
>
> Thanks,
> Greg
>
I'm still not entirely sure what the problem was, but I ended up solving
this problem by dumping the repository and then loading that dump file into
a newly created FSFS repository. Commits work again.
Greg