You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by =?X-UNKNOWN?Q?Michael_S=FC=DF?= <ma...@ilabws.informatik.uni-leipzig.de> on 2002/09/10 13:36:02 UTC

Importing/Commiting using the net-interface not working

Hi,

I have a problem importing or commiting any changes to my subversion
repository using the web-interface. I get the following error:
 
svn: APR does not understand this error code
svn: Commit failed (details follow):
svn: 
failed to open activity db;  check repos perms.

The apache error_log shows:

[Tue Sep 10 13:10:33 2002] [error] [client 10.10.11.73] Could not create
activity /svn/repos/!svn/act/1de4403a-49aa-0310-bbea-989968142
0a9.  [500, #0]
[Tue Sep 10 13:10:33 2002] [error] [client 10.10.11.73] could not open dbm
files.  [500, #120022]
[Tue Sep 10 13:10:33 2002] [error] [client 10.10.11.73] (22)Invalid
argument: failed to open activity db;  check repos perms.  [500, #1
20022]

The obvious conclusion for me was, that the apache httpd doesn't have
enough rights to write to my repository, however the whole repository path
belongs to user nobody allready (and apache runs as nobody). Even a chmod
-R 777 to the whole path did not help.

Every other operation (checking in/out using the ra_local
interface; checking out using ra_dav) works just fine.

I am using recent developer-versions of apache and subversion, apache is
compiled using the --enable-dav --enable-so --with-dbm=db4
--with-berkeley-db configure-options. The system this whole thing runs on
is an Intel Celeron with Suse Linux 8 (and a patched 2.4.18 Kernel). If
any other information is needed I will be happy to supply it.

What am I doing wrong? Thanks in advance,

Michael


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Importing/Commiting using the net-interface not working

Posted by Ben Collins-Sussman <su...@collab.net>.
Michael Süß <ma...@ilabws.informatik.uni-leipzig.de> writes:

> [Tue Sep 10 13:10:33 2002] [error] [client 10.10.11.73] could not open dbm
> files.  [500, #120022]
> [Tue Sep 10 13:10:33 2002] [error] [client 10.10.11.73] (22)Invalid
> argument: failed to open activity db;  check repos perms.  [500, #1
> 20022]
> 
> The obvious conclusion for me was, that the apache httpd doesn't have
> enough rights to write to my repository, however the whole repository path
> belongs to user nobody allready (and apache runs as nobody). Even a chmod
> -R 777 to the whole path did not help.

Specifically, the httpd process is unable to open the files within the
'dav' subdirectory of your repository.  If they are all truly chmod'd
777, then perhaps it's a version problem... i.e. svnadmin used some
database was used to create them (gdbm? bdb?) and httpd/mod_dav_svn is
trying to use a different database library to open them via APR.

Perhaps an 'ldd svnadmin' can show you what it's using?

Another tactic is to run 'httpd -X' within gdb, and break on
dav_svn_get_txn().  You can step into apr_dbm_open() and see what's
happening.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org