You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Eugene Eric Kim <ee...@blueoxen.org> on 2004/02/19 09:35:43 UTC

commits not working with SVNParentPath

I recently installed Subversion 0.37 on Apache 2.0.48, and am having
trouble getting it to work properly when using SVNParentPath.  After
doing some extensive experiments, I did a Google search and found a
similar report, but no responses, so I thought I'd prod again to see
if I could get some help:

  http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=595

When I configure Subversion using SVNPath to specify the absolute path
of the repository, everything works beautifully.  However, when I
switched to SVNParentPath, things go awry.  Checkout works okay, but
commits fail with the following message:

  svn: Commit failed (details follow):
  svn:
  Could not open the requested SVN filesystem

The error_log reports:

[Thu Feb 19 01:15:37 2004] [error] [client 68.120.139.204] (20014)Error string not specified yet: Can't open file '/data/svn/repos/error/format': No such file or directory
[Thu Feb 19 01:15:37 2004] [error] [client 68.120.139.204] Could not fetch resource information.  [500, #0]
[Thu Feb 19 01:15:37 2004] [error] [client 68.120.139.204] Could not open the requested SVN filesystem  [500, #2]
[Thu Feb 19 01:15:37 2004] [error] [client 68.120.139.204] (7)Argument list too long: Could not open the requested SVN filesystem  [500, #2]

Also, when I try a "make check BASE_URL=..." to run the tests, all of
the tests starting with basic-tests.py fail.

What I find very strange about the error message is the first line;
Subversion is trying to access a file in the parent path that doesn't
exist.  This same behavior was reported in the other message I cited
above.

Configuration is as follows:

* Parent path is /data/svn/repos.  I tried both leaving this directory
  alone, and also creating a repository in it using svnadmin; both
  resulted in the same error.  The repository below is /data/svn/test.
  I created this using svnadmin.

* Apache config is:

    ErrorLog /data/svn/logs/error_log
    CustomLog /data/svn/logs/access_log combined
    <Location />
        DAV svn
        SVNParentPath /data/svn/repos
        SetOutputFilter DEFLATE
    </Location>

  I actually have some auth stuff there, but I removed it for the sake
  of testing.

Suggestions?  Thanks.

-Eugene

-- 
Was I helpful?  Let others know.

http://svcs.affero.net/rm.php?r=eekim&p=EnablingOnlineCommunities

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

Re: commits not working with SVNParentPath

Posted by John Szakmeister <jo...@szakmeister.net>.
On Thursday 19 February 2004 15:41, Eugene Eric Kim wrote:
> On Thu, Feb 19, 2004 at 05:47:13AM -0500, John Szakmeister wrote:
> > All I can suggest for the moment is to go back, and repeat the process. 
> > Make sure you have the permissions correct and that you're using the
> > correct URLs. Also, the only difference that I really saw between my
> > httpd configuration and yours was the inclusion of the deflate output
> > filter.  Can you remove that while we try this again?  Oh, and did you
> > make sure to restart apache after making the configuration changes?  I
> > assume so, but I had to ask.
>
> Tried that, but it didn't help.
>
> I did solve the problem, however.  All of the httpd.conf I quoted was
> in an Apache location block:
>
>   <Location />
>   ...
>   </Location>
>
> When I changed the location to something non-root (in this case,
> "/svn", it worked:
>
>   <Location /svn>
>   ...
>   </Location>
>
> This is an acceptable solution for me, but it still seems to be a bug.
> Any thoughts as to why this happens?

I'm not sure why that happens... I'll have to try that with my setup and see 
if I can cause the same thing to happen.  I'm fairly certain that I was 
running my repos at home with a root location block though.  I'll take a look 
at this, but it will probably be a few days before doing so.

> And many thanks, John, for stepping through the problem with me in the
> wee hours of the morning. :-)  Much appreciated.

No problem.  What else am I going to do at 3AM? :-)

-John

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

Re: commits not working with SVNParentPath

Posted by Eugene Eric Kim <ee...@blueoxen.org>.
On Thu, Feb 19, 2004 at 05:47:13AM -0500, John Szakmeister wrote:

> All I can suggest for the moment is to go back, and repeat the process.  Make 
> sure you have the permissions correct and that you're using the correct URLs.  
> Also, the only difference that I really saw between my httpd configuration 
> and yours was the inclusion of the deflate output filter.  Can you remove 
> that while we try this again?  Oh, and did you make sure to restart apache 
> after making the configuration changes?  I assume so, but I had to ask.

Tried that, but it didn't help.

I did solve the problem, however.  All of the httpd.conf I quoted was
in an Apache location block:

  <Location />
  ...
  </Location>

When I changed the location to something non-root (in this case,
"/svn", it worked:

  <Location /svn>
  ...
  </Location>

This is an acceptable solution for me, but it still seems to be a bug.
Any thoughts as to why this happens?

And many thanks, John, for stepping through the problem with me in the
wee hours of the morning. :-)  Much appreciated.

-Eugene

-- 
Was I helpful?  Let others know.

http://svcs.affero.net/rm.php?r=eekim&p=EnablingOnlineCommunities

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

Re: commits not working with SVNParentPath

Posted by John Szakmeister <jo...@szakmeister.net>.
> Also, have you checked the apache error log at all?  It usually has more
> information about the error that occurred.

Duh, your original post had a snippet from it... it's still too early in the 
morning. :-)

All I can suggest for the moment is to go back, and repeat the process.  Make 
sure you have the permissions correct and that you're using the correct URLs.  
Also, the only difference that I really saw between my httpd configuration 
and yours was the inclusion of the deflate output filter.  Can you remove 
that while we try this again?  Oh, and did you make sure to restart apache 
after making the configuration changes?  I assume so, but I had to ask.

If you still have troubles, let me know and we can step through this all 
offline.

-John


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

Re: commits not working with SVNParentPath

Posted by John Szakmeister <jo...@szakmeister.net>.
On Thursday 19 February 2004 05:08, Eugene Eric Kim wrote:
> On Thu, Feb 19, 2004 at 04:54:55AM -0500, John Szakmeister wrote:
[snip]
> > What was your command line to checkout the repository?  I'm assumming had
> > setup http://my.server.com/ as the repository itself (using SVNPath). 
> > The you changed the configuration to use SVNParentPath?  If so, then the
> > location of the repository has moved.  Assuming the name of the repo was
> > test, the new URL should be http://my.server.com/test.  You need to use
> > svn switch --relocate to rewrite the URL for the working copy.
>
>   svn co http://my.server.com/test
>
> I deleted the old working copy and started from scratch before I did
> this.

Okay.

> > > What I find very strange about the error message is the first line;
> > > Subversion is trying to access a file in the parent path that doesn't
> > > exist.  This same behavior was reported in the other message I cited
> > > above.
> >
> > If you changed the directive and nothing else, then I'd expect to see
> > this as an error.  Your working copy still thinks the repository is in
> > the old location.
>
> I don't think this is the problem, as I'm using a fresh working copy.

Sounds good.

> > > * Parent path is /data/svn/repos.  I tried both leaving this directory
> > >   alone, and also creating a repository in it using svnadmin; both
> > >   resulted in the same error.  The repository below is /data/svn/test.
> > >   I created this using svnadmin.
> >
> > Uh, do you mean the repository below is '/data/svn/repos/test'?
>
> That's right; sorry.

Okay.

> > If what I've said doesn't provide any insight, let me know.  I've
> > currently got several repositories hosted at home using SVNParentPath and
> > 16 at work... none of which have ever had problems in this configuration.
>
> Did you create a repository in the parent directory using svnadmin
> create?  Based on my understanding of how this all works, it shouldn't
> be necessary, but the docs are a little unclear on this.  Neither way
> works for me in any case.

No, your don't need to make the parent directory a repository (and I would 
avoid doing that).  Here's kind of a script of what I did:

mkdir /usr/local/svn
svnadmin create /usr/local/svn/my-repo1
svnadmin create /usr/local/svn/my-repo2
svnadmin create /usr/local/svn/my-repo3
chown -R wwwrun:svn /usr/local/svn/*

This has worked fine for me.  Did you make sure to set the permissions on your 
repository?

Also, have you checked the apache error log at all?  It usually has more 
information about the error that occurred.

-John

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

Re: commits not working with SVNParentPath

Posted by Eugene Eric Kim <ee...@blueoxen.org>.
On Thu, Feb 19, 2004 at 04:54:55AM -0500, John Szakmeister wrote:

> > When I configure Subversion using SVNPath to specify the absolute path
> > of the repository, everything works beautifully.  However, when I
> > switched to SVNParentPath, things go awry.  Checkout works okay, but
> > commits fail with the following message:
> >
> >   svn: Commit failed (details follow):
> >   svn:
> >   Could not open the requested SVN filesystem
> 
> What was your command line to checkout the repository?  I'm assumming had 
> setup http://my.server.com/ as the repository itself (using SVNPath).  The 
> you changed the configuration to use SVNParentPath?  If so, then the location 
> of the repository has moved.  Assuming the name of the repo was test, the new 
> URL should be http://my.server.com/test.  You need to use svn switch 
> --relocate to rewrite the URL for the working copy.

  svn co http://my.server.com/test

I deleted the old working copy and started from scratch before I did
this.

> > What I find very strange about the error message is the first line;
> > Subversion is trying to access a file in the parent path that doesn't
> > exist.  This same behavior was reported in the other message I cited
> > above.
> 
> If you changed the directive and nothing else, then I'd expect to see this as 
> an error.  Your working copy still thinks the repository is in the old 
> location.

I don't think this is the problem, as I'm using a fresh working copy.

> > * Parent path is /data/svn/repos.  I tried both leaving this directory
> >   alone, and also creating a repository in it using svnadmin; both
> >   resulted in the same error.  The repository below is /data/svn/test.
> >   I created this using svnadmin.
> 
> Uh, do you mean the repository below is '/data/svn/repos/test'?

That's right; sorry.

> If what I've said doesn't provide any insight, let me know.  I've currently 
> got several repositories hosted at home using SVNParentPath and 16 at work... 
> none of which have ever had problems in this configuration.

Did you create a repository in the parent directory using svnadmin
create?  Based on my understanding of how this all works, it shouldn't
be necessary, but the docs are a little unclear on this.  Neither way
works for me in any case.

-Eugene

-- 
Was I helpful?  Let others know.

http://svcs.affero.net/rm.php?r=eekim&p=EnablingOnlineCommunities

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

Re: commits not working with SVNParentPath

Posted by John Szakmeister <jo...@szakmeister.net>.
On Thursday 19 February 2004 04:35, Eugene Eric Kim wrote:
> I recently installed Subversion 0.37 on Apache 2.0.48, and am having
> trouble getting it to work properly when using SVNParentPath.  After
> doing some extensive experiments, I did a Google search and found a
> similar report, but no responses, so I thought I'd prod again to see
> if I could get some help:
>
>   http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=595
>
> When I configure Subversion using SVNPath to specify the absolute path
> of the repository, everything works beautifully.  However, when I
> switched to SVNParentPath, things go awry.  Checkout works okay, but
> commits fail with the following message:
>
>   svn: Commit failed (details follow):
>   svn:
>   Could not open the requested SVN filesystem

What was your command line to checkout the repository?  I'm assumming had 
setup http://my.server.com/ as the repository itself (using SVNPath).  The 
you changed the configuration to use SVNParentPath?  If so, then the location 
of the repository has moved.  Assuming the name of the repo was test, the new 
URL should be http://my.server.com/test.  You need to use svn switch 
--relocate to rewrite the URL for the working copy.

> The error_log reports:
>
> [Thu Feb 19 01:15:37 2004] [error] [client 68.120.139.204] (20014)Error
> string not specified yet: Can't open file '/data/svn/repos/error/format':
> No such file or directory [Thu Feb 19 01:15:37 2004] [error] [client
> 68.120.139.204] Could not fetch resource information.  [500, #0] [Thu Feb
> 19 01:15:37 2004] [error] [client 68.120.139.204] Could not open the
> requested SVN filesystem  [500, #2] [Thu Feb 19 01:15:37 2004] [error]
> [client 68.120.139.204] (7)Argument list too long: Could not open the
> requested SVN filesystem  [500, #2]
>
> Also, when I try a "make check BASE_URL=..." to run the tests, all of
> the tests starting with basic-tests.py fail.
>
> What I find very strange about the error message is the first line;
> Subversion is trying to access a file in the parent path that doesn't
> exist.  This same behavior was reported in the other message I cited
> above.

If you changed the directive and nothing else, then I'd expect to see this as 
an error.  Your working copy still thinks the repository is in the old 
location.

> Configuration is as follows:
>
> * Parent path is /data/svn/repos.  I tried both leaving this directory
>   alone, and also creating a repository in it using svnadmin; both
>   resulted in the same error.  The repository below is /data/svn/test.
>   I created this using svnadmin.

Uh, do you mean the repository below is '/data/svn/repos/test'?

> * Apache config is:
>
>     ErrorLog /data/svn/logs/error_log
>     CustomLog /data/svn/logs/access_log combined
>     <Location />
>         DAV svn
>         SVNParentPath /data/svn/repos
>         SetOutputFilter DEFLATE
>     </Location>
>
>   I actually have some auth stuff there, but I removed it for the sake
>   of testing.
>
> Suggestions?  Thanks.

If what I've said doesn't provide any insight, let me know.  I've currently 
got several repositories hosted at home using SVNParentPath and 16 at work... 
none of which have ever had problems in this configuration.

-John

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

Re: commits not working with SVNParentPath

Posted by Michael Bussmann <bu...@mb-net.net>.
Hi,

[ References and in-reply-to headers have been reconstructed manually ]

On 2004-02-19 Eugene Eric Kim <ee...@blueoxen.org> reported some problems
with subversion (0.37) when using the SVNParentPath-directive in apache
2.0.48.  A (imho) similar problem has been reported as issue 1934.

I couldn't reproduce this problem in my production subversion repository
yet using "commit", but I got the very same response when I tried to create
a tag.  Setting up a test repository I could even reproduce the problem
Eugene had:

| [Mon Jun 28 13:13:28 2004] [info] [client 128.7.27.131] Access granted: 'bus' CHECKOUT testrepo:/
| [Mon Jun 28 13:13:28 2004] [info] [client 128.7.27.131] Access granted: 'bus' PROPFIND testrepo:/t1
| [Mon Jun 28 13:13:28 2004] [info] [client 128.7.27.131] Access granted: 'bus' GET error:/HTTP_NOT_FOUND.html.var
| [Mon Jun 28 13:13:28 2004] [error] [client 128.7.27.131] (20014)Error string not specified yet: Can't open file '/home/svn/error/format': No such file or directory
| [Mon Jun 28 13:13:28 2004] [error] [client 128.7.27.131] Could not fetch resource information.  [500, #0]
| [Mon Jun 28 13:13:28 2004] [error] [client 128.7.27.131] Could not open the requested SVN filesystem  [500, #2]
| [Mon Jun 28 13:13:28 2004] [error] [client 128.7.27.131] (7)Argument list too long: Could not open the requested SVN filesystem  [500, #2]
| [Mon Jun 28 13:13:29 2004] [info] [client 128.7.27.131] Access granted: 'bus' DELETE testrepo:

(Note I'm using subversion 1.0.5 on apache 2.0.49)

Now I think I found a solution (or a workaround that doesn't require you to
change the <Location> directive to something other than /, if there is at
least one other virtual host)

It seems svn asks the server for a non-existant file (t1 in my case), so
apache answers with a redirection to an error file (/error/blah).  However,
since everything within / should be considered a potential SVN repository
(Location /), the following request for the error document is interepreted
as a svn request.

I got around this by simply adding a redirection for error documents.

| <VirtualHost ...>
| 	...
|         CustomLog               /var/log/apache2/svn.log combined
|         RedirectMatch   permanent ^/error       http://www.mb-net.net/error
| 
| 	<Location />
|                 DAV             svn
|                 SVNParentPath   /home/svn
|                 ...
|         </Location>
| </VirtualHost>

Of course, http://www.mb-net.net/error should be replaced with another
(virtual) host on the server :-)

It's not an elegant solution but it worked for me.

HTH

Cheers,
MB

-- 
Michael Bussmann <bu...@mb-net.net>
BOFH excuse #296:

The hardware bus needs a new token.

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