Greetings all,
I've been working with Subversion for quite a while now, but when I came
in this morning I discovered that, seemingly without reason, my
Subversion repositories were no longer accessible, either via the
network through Apache or locally via a file:// URL. I checked the error
logs for Apache after a failed checkout transaction, and found the
following Subversion-related errorrs:
[Mon Aug 02 10:07:51 2004] [error] [client 137.22.128.120] (20014)Error
string not specified yet: Bad database version: compiled with 4.2.52,
running against 4.1.25
[Mon Aug 02 10:07:51 2004] [error] [client 137.22.128.120] Could not
fetch resource information. [500, #0]
[Mon Aug 02 10:07:51 2004] [error] [client 137.22.128.120] Could not
open the requested SVN filesystem [500, #160000]
[Mon Aug 02 10:07:51 2004] [error] [client 137.22.128.120] (2)No such
file or directory: Could not open the requested SVN filesystem [500,
#160000]
After prowling about in the documentation, I tried 'svnadmin recover' on
the faulty repository, with no success. I've checked and rechecked the
permissions (in my scheme, the parent directory for the repositories, as
well as the repositories themselves are owned by root, and a member of a
group 'svn' of which Apache is itself a member), and they're all
correct. The documentation does not suggest any other solutions for this
issue, and so I come to all of you who are a part of this email list.
In particular, I can't imagine what might have happened over a weekend
to throw our repositories into such immediate disarray.
Thanks very much in advance for your help,
~Dave
Dave Flynn
Carleton College
Associate Administrator of UNIX Systems
(507) 646-7836
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 2 17:18:26 2004