Please don't reply to me personally. I'm resending to users@ list.
Gilbert Fine [·¶Èðºã] wrote:
> Hi,
>
> I accessing the repository using file:/// is just for administration. I
> cannot access subversion in 2 protocols, my trick seems broken.
>
> Yes, I run the command in root's crontab, which is certainly different from
> Apache's user.
Then that's why you have BDB 'hangs'. When root accesses the database,
it changes file ownership and permissions, and then the apache user is
no longer able to access the database.
> But I expect that 'svn cat' will only read files and don't modify any files.
Incorrect. Even reading data from the database causes db files to be
read and written.
To fix your problem:
1. make the repository wholly owned by apache
2. run the cronjob in the *apache user's* crontab.
3. never access the database as anyone other than the apache user
(for example, if you even run 'svnadmin recover'.)
> And after I got complains, I run "svn cat" using root users, I got the same
> error message.
>
> And, if it will mess up the files, why this occurs several hours after I set
> up the crontab? en, maybe it happened only when both Apache and the crontab
> was accessing the repository.
>
> I have no test enviroment now, because the developers need working every
> day. DB mess up will scare them.
>
> I also have hot-backup.py running in root's crontab, on several
> repositories, all are fine (except one: I mentioned in another email). Maybe
> I should change that to another user?
>
>
> Gilbert
>
>
> -----Original Message-----
> From: dev-return-56550-gfan=corp.netease.com@subversion.tigris.org
> [mailto:dev-return-56550-gfan=corp.netease.com@subversion.tigris.org] On
> Behalf Of Ben Collins-Sussman
> Sent: Sunday, September 05, 2004 11:04 PM
> To: Gilbert Fine [·¶Èðºã]
> Cc: svn-dev-list
> Subject: Re: berkeley db needs recover again and again
>
> On Sun, 2004-09-05 at 09:26, Gilbert Fine [·¶Èðºã] wrote:
>
>
>>file:///home/svn_repos/admin/svn_arkstudio.ini
>
>
> You're using two different methods of accessing the repository: apache is
> accessing it for daily work, but then this cron job is *also* accessing it
> now.
>
> I'm assuming that your repository is wholly owned by the apache user.
> Are you also running the cron job as that same apache user? If not, the
> cron job is probably messing up permissions and ownership.
>
> Read the last section in chapter 6:
>
> http://svnbook.red-bean.com/svnbook/ch06s05.html
>
> And also this FAQ:
>
> http://subversion.tigris.org/project_faq.html#stuck-bdb-repos
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 6 14:00:03 2004