Lübbe Onken <l.onken@...> writes:
>
> Joe Schirmer wrote:
>
> > I'm running apache v2.0 and svn v1.3.1 on a lunix server (RHEL4).
>
> ...
>
> > But the problem is when I try to commit a modified file I get the
> following error in TortoiseSVN:
> >
> > Error: Commit failed (details follow):
> > Error: Can't create directory
> '/var/lib/svnTest01/db/transactions/1-1.txn': Permission denied
> >
> > I also get the following in my httpd/error_log in on my linux
> server:
> >
> >
> > [Thu Apr 27 18:51:37 2006] [error] [client 172.31.11.45]
> Could not create activity
> /svnTest01/!svn/act/24e30a13-f6f5-fb40-b206-a650c4c5e116. [500, #0]
> > [Thu Apr 27 18:51:37 2006] [error] [client 172.31.11.45]
> could not begin a transaction [500, #13]
> > [Thu Apr 27 18:51:37 2006] [error] [client 172.31.11.45]
> Can't create directory '/var/lib/svnTest01/db/transactions/1-1.txn':
> Permission denied [500, #13]
> > [Thu Apr 27 19:03:54 2006] [error] [client 172.31.11.45]
> Directory index forbidden by rule: /var/www/html/
> >
> > The repository is owned by apache and I've double checked the write
> permissions for apache. What else do I need to do or check on to get the
> commit to work?
>
> Generally speaking you should be better off asking this kind of question on
> the subversion users list, because it clearly indicates a server config
> problem and not a client problem. I can try to give you some hints, but I'm
> not an apache wizard.
>
> I assume that you are accessing the repository via http(s)?
>
> The path "/var/lib/svnTest01/" sounds a bit like a strange place to put a
> repository. Does apache have write access there? Did you create the
> repository as root and forgot to "chown -R" it? My suggestion is to put
> apache in a "svn" group, create a user "svn" who is member of this group as
> well and create all repositories as that user.
Thanks for the help. I'm accessing the repository via http. I did go out to
the subversion list and looked around and the only hint was to check the write
permissions for the directory, which I checked multiple times.
But I did stumble across the solution and I havn't seen it mentioned anywhere
else yet, so I'd like to follow up here in case anyone else runs into the same
problem.
Apparently the most recent releases of Fedora and Redhat Enterprise use SELinux
which enforces additional access restrictions beyond those used by the basic
filesystem for Apache. I used the system-config-securitylevel command to
configure SELinux to stop adding additional file access restrictions to my httpd
and it started working.
--Joe Schirmer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Apr 28 20:06:29 2006