[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Intermittent Failures While Committing

From: Jason Diamond <jason_at_injektilo.org>
Date: 2004-06-24 19:46:25 CEST

We recently migrated to a new server. After installing subversion 1.0.5
and libapache2-svn 1.0.5, I rsync'd my repositories over from the old
server (which was running 1.0.5). Probably a stupid idea but it seemed to

Now we're occassionally getting failures while trying to commit multiple

/var/log/apache2/error.log has messages like these in it:

[Wed Jun 23 19:07:08 2004] [error] [client] (20014)Error
string not specified yet: Error opening db lockfile
[Wed Jun 23 19:07:08 2004] [error] [client] Could not fetch
resource information. [500, #0]
[Wed Jun 23 19:07:08 2004] [error] [client] Could not open
the requested SVN filesystem [500, #37]
[Wed Jun 23 19:07:08 2004] [error] [client] (84)Invalid or
incomplete multibyte or wide character: Could not open the requested SVN
filesystem [500, #37]

If we break the commits up into smaller pieces, we're able to get them in.

Does this sound familiar to anyone? I obviously have the permissions set
up correctly because it works sometimes. I suspect that the new server
(which is really a Virtuozzo VM) is running out of memory which is causing
Subversion to fail at random times. Could this be the case? Is there a way
to turn on more verbose logging that could confirm this?

-- Jason

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 24 19:47:59 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.