I'm currently in the process of moving an older SVN 1.4 repository to
SVN 1.5. To do so, I dumped the old repository, copied the dump from one
machine to another, and loaded it up. I started up an svnserve process
on the new repository, and was initially able to access it just fine.
The svnserve is a hand-build version running on Ubuntu 8.04. I wanted
SVN 1.5, and thus had to build myself. I am currently running a non-SASL
build.
However, after using it for a few minutes (doing a few test commits,
making sure a friend could access it, etc), we noticed that it started
to get very slow. Every action, either through TortoiseSVN or Subclipse
seemed to be hanging for about a half of a minute before it would
complete. I first noticed it when trying to make a branch of trunk/ from
HEAD, which should have been an almost instant operation, especially
since I didn't switch my WC. It's not always consistent. Sometimes it
will complete fast as I expect, but sometimes it takes a bit.
I suspect that there are two problems here. Either (1) there's just some
network issues between my location and the server, or (2) the svnserve
process is hanging. I don't suspect (1). I can repro the hangs if I
checkout a local copy of repository when ssh'ed to the server. Ctrl+C
won't stop Subversion, but I can still Ctrl+Z and it's fine, so it's
*not* my ssh terminal hanging. Of course, sometimes it also works fine.
Also, the CPU of the machine isn't loaded by either the svnserve or the
svn client. We can repro it even if there is nothing else of note
running on the machine.
So ruling out (1), it might be (2). Looking at the network traffic when
it freezes up in Wireshark, it gets this far:
( success ( 2 2 ( ) ( edit-pipeline svndiff1 absent-entries
commit-revprops depth log-revprops partial-replay ) ) ) ( 2 (
edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops )
29:svn://XXX.XXXXXXXXXXXXXXX.com ) ( success ( ( CRAM-MD5 ) 16:XXXXXXXX
XXXXXXX ) ) ( CRAM-MD5 ( ) )
[URLs and realm masked to protect the innocent, but length *was*
preserved]
It always seems to stop right after the CRAM-MD5() thing. So: is this
hang a known issue with svnserve 1.5? Does anybody have any ideas how I
should diagnose this? I'm just starting it as "sudo svnserve --daemon
--root <path>". I can't find anything online about this, but it seems
quite odd.
Oh: and other 1.5 svnserves I have running on various Windows boxen run
fine configured the same as this, so this is my first time observing
this behavior.
Thanks for your time!
Jason Malinowski
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-27 08:26:29 CEST