> Any help would be greatly appreciated, as I got lots of
> developers who are going to want to patch first thing
> in the morning. I've got a full backup from not long ago
> and I will be trying to restore that to a fresh area to
> see if that corrects it, but whether or not it does,
> this seems like it could be a bad bug.
You say that "it could be a bad bug", but it's not clear what you mean
by "it". What's the problem? You showed us a DB error about not being
able to open the 'nodes' table, followed by a successful 'svnadmin
recover'. Is the error now fixed? Does it persist? We need a better
description of what's wrong.
Here's the standard checklist:
* the repository isn't being accessed via a network share like NFS,
right? That's a big no-no.
* Was the problem simply one of permissions... that apache didn't have
full read/write access to all the database files? See next point:
* I can see that the repository is being accessed by at least three
different processes -- (1) apache, (2) a client using file:///, (3) an
administrator using 'svnadmin'. Are you doing all of these accesses
safely? As the same user? If not, are you being careful about umasks?
Look at the "Using Multiple Servers" section at the end of chapter 6 for
details about this.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Feb 1 16:20:42 2004