[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: getting "svn: PROPFIND of xxxxx: could not connect to server" error...

From: bruce <bedouglas_at_earthlink.net>
Date: 2004-09-07 15:42:10 CEST

no prob...

i'm inclined to beleive that my issue is really with correctly setting up
the SVPath/SVNParentPath within the submission 'Location' block.

i have the following dir structure on the hard drive:

  /svnroot
    /svn
    /svntest2

i'd like to know what should be the actual values in a real/hypothetical
'location' block. i also need to know what would be the information, if i
only wanted to get a single repository using SVNPath, or multiple
repositories using SVNParentPath. and of course, i'd need to knwo the right
way to access the single/multiple respositories using 'http'.

in following the examples, i'm still getting the above errors...

my 'location' block is

LoadModule dav_module modules/mod_dav.so
LoadModule dav_svn_module modules/mod_dav_svn.so
<Location /svn1>
   DAV svn
   SVNPath /svnroot/svntest2
</Location>

i'm trying to get to the 'svntest2' repository i'd like to be able to access
it by 'http://myserver/svntest2' or 'http://myserver/svnroot/svntest2' or
'http://myserver/abc' if 'abc pointed back to the correct repository!! at
this point, i'm lost in how to make this work, and rectify the errors...

any help/assistance/etc.. would be helpful!!

regards,

-bruce

-----Original Message-----
From: John Szakmeister [mailto:john@szakmeister.net]
Sent: Tuesday, September 07, 2004 4:27 AM
To: users@subversion.tigris.org
Subject: Re: getting "svn: PROPFIND of xxxxx: could not connect to
server" error...

Sorry Bruce... didn't mean to reply directly to you. Here's the message
for the list.

On Tuesday 07 September 2004 01:59, bruce wrote:
[snip]
> the portion of the config file that deals with dav/svn is:
> LoadModule dav_module         modules/mod_dav.so
> LoadModule dav_svn_module     modules/mod_dav_svn.so
> <Location /svntest2>
>    DAV svn
>    SVNPath /svnroot

What's the layout of the directories here?  If it's:
  /svnroot
    |--- repo1/
    |--- repo2/

then you'll want SVNParentPath instead of SVNPath.  In that case your URLs
would look like:
  http://server.name/svntest2/repo1

> #
> #   # Limit write permission to list of valid users.
> #   <LimitExcept GET PROPFIND OPTIONS REPORT>
> #      # Require SSL connection for password protection.
> #      # SSLRequireSSL
> #
> #      AuthType Basic
> #      AuthName "Authorization Realm"
> #      AuthUserFile /absolute/path/to/passwdfile
> #      Require valid-user
> #   </LimitExcept>
> </Location>
>
> i rebuilt the svn apps from source and connected them to the current
> version of the berkeley db on my box... i didn't want to do a complete
> rebuild of apache as well....

This isn't a berkeley problem... it's simply not pointed to an actual
repository.  Getting SVNPath or SVNParentPath pointed to the correct
location will help fix your problem.  As a side note, make sure you get
the permissions right.  You'll need to repository to be owned by the
apache user in order for it to work correctly.

> everything appears to be as it should be... however, given that it
> doesn't work, there's an error somewhere!!! searching through google
> indicates that others have had a smiliar problem, but nothing shed any
> light onto what the issue really is.
>
> any pointers/comments/thoughts are appreciated...
>
> thanks
>
> -bruce

-John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 7 15:42:18 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.