Re: Unable to access repository, please help...

----- Michael & Mikaela Krueger <info@michael-krueger.org> wrote:
> Hmm...
> Ok I understand that I should upgrade to Subversion 1.3.1... I don't
> understand why I should upgrade the whole SuSE system...
>
> And will the 1.3.1 be able to recover my broken repository?

Probably not. The recovery mechanism works pretty much the same in all 1.x Subversion releases, with the exception of supporting a couple new features that newer BDB libraries implement.

Does strace or ltrace show you anything useful? Generally, people end up in this situation because they have a couple of processes running as different users acessing the BDB backend. The end effect is that log files obtain permissions that aren't suitable for the other process (generally because of the umask), and essentially locks out the other process from accessing the repository. The best advice I can give is to:
 1) Always use the same user as the process serving the repositories for administration (at least for the BDB backend)
 2) Check your permissions. The server process user should have both read and write access to all the log files, and the database itself (in /path/to/repos/db).

-John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 9 11:19:31 2006