You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Dominik Westner <li...@logicunited.com> on 2003/11/23 09:57:06 UTC
Problem after upgrading to 0.33: mod_svn not working
Hi all,
I just upgraded my subversion repository from 0.27 to 0.33.
I am running on gentoo linux with apache 2.0.48.
I have dumped and restored my repository.
Everything seems to work fine for file urls, but if I try to access the
repository through mod_svn/apache. I get the following error:
[Sun Nov 23 10:51:15 2003] [error] [client 10.0.1.2] Could not fetch
resource information. [500, #0]
[Sun Nov 23 10:51:15 2003] [error] [client 10.0.1.2] Could not open the
SVN filesystem at /home/subversion/repo
sitory [500, #160029]
[Sun Nov 23 10:51:15 2003] [error] [client 10.0.1.2] (17)File exists:
Berkeley DB error while opening environme
nt for filesystem /home/subversion/repository/db:
DB_RUNRECOVERY: Fatal error, run database recovery [500, #160029]
I verified that my repository is owned by the user apache is running.
Any ideas what could be wrong?
Thanks
Dominik
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Problem after upgrading to 0.33: mod_svn not working
Posted by Dominik Westner <li...@logicunited.com>.
HI Jostein,
thanks for your help. I have tried to do this already. It did not help.
But I have tried something else.
I have recreated my repository (dumped with version 0.27) with version
0.31 on an other machine.
Then I have copied back the repository to my machine running 0.33.
Funny enough now apache works fine.
But if I do this as root:
loki subversion # svn ls file:///home/subversion/repository
svn: Couldn't open a repository
svn: Unable to open an ra_local session to URL
svn: Unable to open repository 'file:///home/subversion/repository'
svn: Berkeley DB error
svn: Berkeley DB error while opening environment for filesystem
/home/subversion/repository/db:
Resource temporarily unavailable
I get this error no matter if I run apache or not at the same time. And
it can't be a permission problem because I am doing this as root.
This is pretty weird I think.
Dominik
On 23.11.2003, at 11:27, Jostein Chr. Andersen wrote:
> On Sunday 23 November 2003 10.57, Dominik Westner wrote:
>> I verified that my repository is owned by the user apache is running.
>>
>> Any ideas what could be wrong?
>
> Stop Apache.
>
> As root, do the following command:
> svnadmin recover /home/subversion/repository
>
> Are _every_ file in "/home/subversion/repository" owned by "apache"?,
> this command will help:
> chown -R apache:yourgroupname /home/subversion/repository
>
> Are all the files writable by at least owner (and maybe group)?
> * If user and group needs this access:
> chmod 644 /home/subversion/repository/*/*
> * If only user needs write access:
> 664 /home/subversion/repository/*/*
>
> Then "chmod 755 dav db hooks locks" (if write access for both user and
> group) or "chmod 775 dav db hooks locks" (user only) from within
> "/home/
> subversion/repository".
>
> Jostein
>
> --
> Jostein Chr. Andersen <jo...@josander.net>
> http://www.josander.net/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Problem after upgrading to 0.33: mod_svn not working
Posted by "Jostein Chr. Andersen" <jo...@josander.net>.
On Sunday 23 November 2003 10.57, Dominik Westner wrote:
> I verified that my repository is owned by the user apache is running.
>
> Any ideas what could be wrong?
Stop Apache.
As root, do the following command:
svnadmin recover /home/subversion/repository
Are _every_ file in "/home/subversion/repository" owned by "apache"?,
this command will help:
chown -R apache:yourgroupname /home/subversion/repository
Are all the files writable by at least owner (and maybe group)?
* If user and group needs this access:
chmod 644 /home/subversion/repository/*/*
* If only user needs write access:
664 /home/subversion/repository/*/*
Then "chmod 755 dav db hooks locks" (if write access for both user and
group) or "chmod 775 dav db hooks locks" (user only) from within "/home/
subversion/repository".
Jostein
--
Jostein Chr. Andersen <jo...@josander.net>
http://www.josander.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org