subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Sperling <s...@elego.de>
Subject Re: svn and svnserve hanging
Date Mon, 08 Apr 2019 13:26:15 GMT
On Mon, Apr 08, 2019 at 02:38:15PM +0200, Vincent Lefevre wrote:
> On 2019-04-08 13:57:32 +0200, Stefan Sperling wrote:
> > There is insufficient information in your report for anyone to act upon.
> > Most importantly, it is unclear which component in the chain is causing
> > the problem. Is it SVN? Is it SSH? Is it TCP?
> > Please try to find answers to these questions.
> 
> I'm using SSH connection sharing and the master (started at 12:39,
> i.e. the same master as with the hanging svn) is still working.

Interesting. Does the problem also occur if you disable SSH
connection sharing completely? Perhaps it is related?
 
> > You could use strace to figure out which system call programs are
> > sleeping in, e.g.: strace -p 48724
> 
> Unfortunately strace is not installed on the server.
> 
> Concerning the svn client, that's
> 
> strace: Process 19549 attached
> read(6,
> 
> and for the SSH client:
> 
> strace: Process 19565 attached
> restart_syscall(<... resuming interrupted restart_syscall ...>

These look as expected.

> > You could try to get some information out of SSH? Perhaps the sshd
> > server logs contain clues?
> 
> I've asked the sysadmin, but since the SSH master still works,
> I doubt that this would be related.

How can you know that? My and your guesses are only as good as any
other guesses. Until more information is surfaced which pins things
down further we simply don't know anything at all about this problem.

> I don't know how to reproduce the problem. The master is already
> started with -vvv, but there are no dates. However, I don't see
> anything suspicious.
> 
> After doing a SSH connection via the master and quitting, I get
> concerning the status:
> 
> debug3: channel 3: status: The following connections are open:
>   #1 mux-control (t16 r2 i0/0 o0/0 e[closed]/0 fd 6/6/-1 sock 6 cc -1)
>   #2 client-session (t4 r0 i0/0 o0/0 e[write]/0 fd 7/8/9 sock -1 cc 1)
>   #3 mux-control (t16 nr0 i3/0 o3/0 e[closed]/0 fd 10/10/-1 sock 10 cc -1)
> 
> #2 can only be the session of the hanging svn.

That looks alright to me.

Mime
View raw message