On Tuesday 20 January 2004 19:41, Gregois wrote:
> Howdy,
>
> I am having problems with PROPFIND also.
>
> I built both Apache (httpd-2.0.48) and subversion (0.36.0) from scratch on
> Fedora Core 1 machine (see below for details of build documentation).
>
> No apparent problems and subversion passes make check with 100% sucess.
>
> apache runs as user apache
>
> test repository is /usr/local/src
Just to make sure... are you sure your repo is at /usr/local/src? Seems a bit
odd.
> aliased as /svn/
>
> I had sucess in building a working Apache/SVN sever using svn-0.34.0, and
> have followed the same procedure (like verbatim according to the doc that I
> wrote along the way: see below)
>
> Using TortoiseSVN-0.23 (via network, obviously) import produces:
>
> PROPFIND request failed on /svn
> PROPFIND of '/svn': 405 Method Not Allowed (http://my.web.address)
This looks like a configuration or a permissions problem. Are you certain
that everything is owned by the apache user, and that your apache process is
running as that user?
> I initially thought that this was a compatability problem with TortoiseSVN
> so I upgraded to TortoiseSVN-0.24 with the same result.
>
> I also get the same error with RapidSVN so imagine it's a server side
> problem.
>
> Trying console mode:
>
> # svn import path/to/import/ http://my.web.address/svn/
>
> produces:
>
> subversion/libsvn_ra_dav/util.c:661: (apr_err=175002)
> svn: PROPFIND request failed on '/svn'
> subversion/libsvn_ra_dav/util.c:285: (apr_err=175002)
> svn: PROPFIND of '/svn': 405 Method Not Allowed (http://my.web.address/)
> subversion/clients/cmdline/util.c:349: (apr_err=175002)
> svn: Your commit message was left in a temporary file:
> subversion/clients/cmdline/util.c:349: (apr_err=175002)
> svn: 'svn-commit.tmp'
>
> no entries in apache error_log from any of this activity.
>
>
> Try another protocol:
>
> # svn import path/to/import/ file:///usr/local/src/
>
> Seems to work fine! At least subversion reports the commit as successful,
> revision 1.
>
> So I guess this is an apache/module problem?
Did you do this as root? Did you run this with a umask of 002? If not, then
you probably changed permissions on your repository by running the above
command.
>
> Trying to browse the repository URL now produces:
>
> [Wed Jan 21 11:27:32 2004] [error] [client 131.217.240.27] (20014)Error
> string not specified yet: Berkeley DB error while opening environment for
> filesystem /usr/local/src/db: DB_RUNRECOVERY: Fatal error, run database
> recovery
> [Wed Jan 21 11:27:32 2004] [error] [client 131.217.240.27] Could not fetch
> resource information. [500, #0] [Wed Jan 21 11:27:32 2004] [error] [client
> 131.217.240.27] Could not open the requested SVN filesystem [500, #160029]
> [Wed Jan 21 11:27:32 2004] [error] [client 131.217.240.27] (17)File exists:
> Could not open the requested SVN filesystem [500, #160029]
>
> in the apache error_log.
>
> Guessing that this was a permissions issue I ran
>
> # chown -R apache /usr/local/src
>
> to check but subsequent requests for the URL produce the same errors.
It's saying there was a fatal error, and that you need to recover the
database. This means stop all access to the repository (i.e., stop the
apache process), and run 'svnadmin recover' on the repository. If all goes
well, it'll print out the youngest revision in the repository when it's
complete. After that, you need to ensure that your permissions are still
correct, and try again.
> Things I notice:
>
> /usr/local/apr/ existed after the 0.34.0 build but does not after 0.36.0
> build. Is this to be expected?
I don't know why the directory disappeared or was even there in the first
place. But, judging by what you have below, Subversion is going to use the
libraries from your compiled apache at /usr/local/apache2/libs.
I assume you have BerkeleyDB 4.0.14 or 4.2.52? I know there have been some
troubles with 4.1.x in the past.
> [snip]
> ## restart Apache:
>
> /usr/local/apache2/bin/apachectl configtest
> /usr/local/apache2/bin/apachectl graceful
>
> At this point I can enter my web address into a browser
> and see the Subversion Revision 0: header, with (obviously)
> no files present. But the browser is reporting a 500 error as
> the title of the page.
This seems to indicate a problem with your apache setup. Can you post your
httpd.conf?
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 21 10:10:14 2004