Ok, I took NFS out of the equation (made a local copy of the repo) and the
same error persists.
Truss -f of the apache instance does not show a call to open an
"activities.db" - my repo dav dirs only have a activities.pag and
activities.dir files - no db file.
Ldd shows the mod_dav_svn is linked to the libapr from subversion-1.2.0 and
it in turn is
libc.so.1 => /lib/libc.so.1
libgcc_s.so.1 => /usr/local/lib/libgcc_s.so.1
libdl.so.1 => /lib/libdl.so.1
Can you suggest another test ?
Thanks for you help,
Data Center Services
Sr. System Administrator
Information Resources & Technology
School of Medicine Stanford University
From: Ben Collins-Sussman [mailto:email@example.com]
Sent: Monday, July 04, 2005 9:12 AM
To: Fletcher Cocquyt
Subject: Re: svn: Can't close activity db: Error string not specified yet
On Jul 4, 2005, at 9:35 AM, Fletcher Cocquyt wrote:
> [Mon Jul 04 07:23:44 2005] [error] [client 127.0.0.1] Can't close
> db: Error string not specified yet [500, #20014]
Regardless of whether you're using a BerkeleyDB or FSFS repository,
the mod_dav_svn server module keeps a private DBM database of
"activity" objects in the repos/conf/dav/ directory. It uses
whatever DBM that the APR library happens to link to on your system,
and makes generic db calls through APR's abstracted API.
> 5227: open("/export/svn/repos/conf/dav/activities.dir", O_RDWR|
> 0666) = 14
> 5227: open("/export/svn/repos/conf/dav/activities.pag", O_RDWR|
> 0666) = 15
I don't know what the problem is, other than to guess that somehow
the apr_dbm_open() function is failing to open the activities.db file
over NFS. It could be an NFS bug, or it could be some strange
interoperablity bug between your particular NFS implementation and
whatever DBM is being invoked by APR.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Jul 5 00:45:21 2005