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

Re: Apparent BerkeleyDB problem accessing repo with ra_local

From: Art Haas <ahaas_at_airmail.net>
Date: 2003-12-10 22:01:47 CET

On Wed, Dec 10, 2003 at 05:18:48PM +0000, Philip Martin wrote:
> "Art Haas" <ahaas@airmail.net> writes:
> It could be a NPTL problem as Greg suggested, however
> > When trying to do 'svn ls' on the remote machine I see this:
> "remote"
> > $ svn ls file:///path/to/svnrepo
> "file:"
> > svn: Unable to open an ra_local session to URL
> > svn: Unable to open repository 'file:///path/to/svnrepo'
> > svn: Berkeley DB error while opening environment for filesystem
> > /path/to/svnrepo/db:
> > Resource temporarily unavailable
> Are you trying to use ra_local to access a repository on a network
> partition? You need to run a Subversion server to access a repository
> over a network.

I did the 'svn ls' locally to test the repo and see if it was readable
for someone accessing it locally on the remote machine. For remote access
I've got Apache configured to make the repo available, and after doing
the 'svnadmin' trick of rebuilding the files the repo is available over
the net again. On my home machine I get this:

$ svn ls http://subversion.pythoncad.org:9000/svn

I'll be investigating the problem with the BerkeleyDB files in the
coming days. I've tried downloading and building my own copy of the
db-4.0 libraries, and subversion failed with that as well. The important
thing is that the repository is again publically available.

Art Haas

Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.
-Thomas Jefferson to James Smith, 1822
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 10 22:02:31 2003

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

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