I'm running svnserve under Win2000 server with Berkley database. There
are three repositories hosted. The database has been fine for ~2 years
now. I've upgraded on several occasions migrating from v1.0.1-2, v1.1.4,
and 1.3.0 (with changing the db over to use Berkley 4.3).
On occasions the svnserve application would abort without warning, say
about once every month or more (repository me), every 6 months
(repository ee) and only ever once (repository sw). Certainly liveable
and the message was always 'abnormal program termination'. On occasion
I'd have to do a recover, but there were never any of the panics
mentioned in the troubleshooting guide and the data all seemed to be
there so I was never overly concerned.
However, after upgrading svnserve to 1.3.0 these 'crashes' have appeared
to occur much more frequently. Unfortunately they now occur about every
10th access of the repositories (via the TortoiseSVN repobrowser; there
are no failures during commit, or update transactions).
Interestingly I cannot cause the crash using the command line client
(svn ls "svn://x.x.x.x/me" [even repeatedly from a batch file]) and only
see it if access is via tortoiseSVN's repobrowser. The way to reproduce
the crash is repeatedly and randomly jump all over the repo browser
window clicking on folders to open them up. I can crash the svnserve in
as little as three clicks and at worst it takes about 20-30 clicks. I
know that means it's probably TSVN, but I also fail to see why the
server should be this vulnerable unless TSVN is doing something really
illegal. Even the most recent version of TSVN (126.96.36.19919) brings the
most recent version of svnserve (1.3.1) down.
I have now upgraded the server to 1.3.3, cleared all the dead logs, and
removed the failed transactions (of which their weren't that many). The
number of failed transactions was not correlated with the crashability
of the repository. It still happens though so I'm concerned about where
exactly the problem may be - could it even be the database itself?
N.B. I've cross posted this to the TSVN and SVN groups because although
it is a TSVN initiated crash, I think the SVN server should be more
resilient to this type of attack.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu May 25 10:12:18 2006