On Mon, Jan 27, 2003 at 10:35:57AM -0800, Garret Wilson wrote:
Zack Brown wrote:
It doesn't seem like the same problem to me, because the only similar
error is that I get a svn: PROPFIND of /: 405 Method Not Allowed and
Garrett gets a svn: PROPFIND of /: 403 Forbidden. But even those are
not identical.
This may have to do with how the repositories are set up. I am trying to
make the root directory a parent of all repositories (Dav svn and
SVNParentPath /usr/local/svn), so that /java would be a repository the
client is allowed to access. When the client tries to do a PROPFIND on
/, the server notes that PROPFIND is a valid method (because of Dav svn)
but that the client is not allowed to access /.
The server I'm using is set up like this:
Location /svn/kerneltraffic
DAV svn
SVNPath /svn/kerneltraffic
AuthType Basic
AuthName Kernel Traffic Subversion Repository
AuthUserFile /svn/kt.userfile
Require valid-user
/Location
If, on the other hand, nothing is setup for the root and instead a
single depository location is specified in /java (Dav svn and SVNPath
/usr/local/svn/java) and the client tries to access /, WebDAV hasn't
even been enabled for the root. Apache notes that PROPFIND isn't even a
method allowed for / before checking to see if the client has
appropriate permissions.
I still find it strange that svn ever sends a PROPFIND / in the first
place, as the repository should be in /java and that is the URL requested.
In my case, the error happened a little while after I started invoking
the svn client multiple times at once to access the same repository. I
may have been doing a 'co' at the same time as a 'ci' at one point. But
why should that matter? Theoretically there are many people using a
repository at once, and the don't all get in line to run svn. So I
discounted that as a possible culprit.
Another possibility is that the svn client was interrupted in the middle
of an operation, shortly before the problems started happening.
Aside from those two things, I believe there was nothing at all out of
the ordinary. I just suddenly couldn't access the repositories.
Actually, that's not 100% true. I can do an 'svn diff' and get real
output. But I can't do a 'ci' or 'up' or 'co'.
I'd rather not just blow away the repository and start over, since I guess
this problem may recur. I have a broken repository now (even a new 'svn co'
to an empty directory doesn't work), and that may be the best way to
track down the problem.
I've gzipped the entire server-side repository, and it's available (or
will be in about 20 minutes) at
http://zork.net/~zacko/ktsvn.tar.gz
Be warned: it's 57688K. Don't download until 4:30 PST, or you'll only get
a partial archive.
Garret
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
--
Zack Brown
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:20:40 2006