You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by vishwajeet singh <de...@gmail.com> on 2012/03/26 11:43:16 UTC

Subversion 1.7 server & client issue : not able to commit E160013 path not found

Hi All,

I recently upgraded from subversion server from 1.6 to 1.7, everything
works fine for 1.6 client and 1.7 server.
But when I upgrade to 1.7 client my commit fails with following error

*svn: E160013: Commit failed (details follow):*
*svn: E160013: '/svn/RDR/!svn/me' path not found*

I am able to checkout and update with 1.7 client but not able to commit.

My apache version is 2.3 and OS is centos 5.4.

Any help in this regard is appreciated

Regards,
Vishwajeet Singh
+91-9657702154 | dextrous85@gmail.com | http://bootstraptoday.com
Twitter: http://twitter.com/vishwajeets | LinkedIn:
http://www.linkedin.com/in/singhvishwajeet

Re: Subversion 1.7 server & client issue : not able to commit E160013 path not found

Posted by Philip Martin <ph...@wandisco.com>.
Philip Martin <ph...@wandisco.com> writes:

> vishwajeet singh <de...@gmail.com> writes:
>
>> As thread it's not just with mod_wsgi, problem persist with fcgi, can you
>> please elaborate on reordering I tried moving wsgi module at end but that
>> did not help.
>
> Reordering may not work; it depends how the other modules work.  Fixing
> it may require code changes in the non-Subversion modules.  The error
> message:
>
>  svn: E160013: '/svn/RDR/!svn/me' path not found
>
> is exactly what happens when some other module intercepts POST requests
> intended for mod_dav_svn.

I've just added mod_wsgi 3.3-2 to my test environment and Subversion's
v2 protocol still works.  This is a Subversion commit over v2:

::1 - - [27/Mar/2012:12:04:18 +0100] "OPTIONS /obj/repo HTTP/1.1" 200 188
::1 - - [27/Mar/2012:12:04:18 +0100] "POST /obj/repo/!svn/me HTTP/1.1" 201 -
::1 - - [27/Mar/2012:12:04:18 +0100] "PROPPATCH /obj/repo/!svn/txn/16-h HTTP/1.1" 207 426
::1 - - [27/Mar/2012:12:04:18 +0100] "MKCOL /obj/repo/!svn/txr/16-h/A HTTP/1.1" 201 199
::1 - - [27/Mar/2012:12:04:18 +0100] "MERGE /obj/repo HTTP/1.1" 200 424

This is mod_wsgi request:

::1 - - [27/Mar/2012:12:04:22 +0100] "GET /myapp HTTP/1.1" 200 12

I used a very basic mod_wsgi configuration, just a line:

WSGIScriptAlias /myapp /home/pm/sw/subversion/obj/myapp.wsgi

I suggest you setup a test environment with a working Subversion config.
Gradually extend it with mod_wsgi until it stops working.  Then tell us,
and/or the mod_wsgi people, which config change causes Subversion to
fail.

-- 
Philip

Re: Subversion 1.7 server & client issue : not able to commit E160013 path not found

Posted by Philip Martin <ph...@wandisco.com>.
vishwajeet singh <de...@gmail.com> writes:

> As thread it's not just with mod_wsgi, problem persist with fcgi, can you
> please elaborate on reordering I tried moving wsgi module at end but that
> did not help.

Reordering may not work; it depends how the other modules work.  Fixing
it may require code changes in the non-Subversion modules.  The error
message:

 svn: E160013: '/svn/RDR/!svn/me' path not found

is exactly what happens when some other module intercepts POST requests
intended for mod_dav_svn.

-- 
Philip

Re: Subversion 1.7 server & client issue : not able to commit E160013 path not found

Posted by vishwajeet singh <de...@gmail.com>.
On Mon, Mar 26, 2012 at 11:48 PM, Philip Martin
<ph...@wandisco.com>wrote:

> vishwajeet singh <de...@gmail.com> writes:
>
> >> > *svn: E160013: Commit failed (details follow):*
> >> > *svn: E160013: '/svn/RDR/!svn/me' path not found*
> >
> >> "SVNAdvertiseV2Protocol off" might be a workaround.
> >>
> >> Note that there are known issues with httpd-2.4 support in svn with bdb
> >> repositories.
> >
> > I could workaround with that but than I don't get the benefits of new
> > protocol.
> >
> > Just to add I stumbled upon thins thread
> >
> http://mail-archives.apache.org/mod_mbox/httpd-users/201203.mbox/%3Cjkg3qq$a55$1@dough.gmane.org%3E
> >
> >
> > I am facing the exactly the same issue.
> >
> > I wonder why wsgi and svn would conflict and create such scenario.
>
> mod_wsgi is probably intercepting the POST request intended for
> mod_dav_svn and not passing it on.  Subversion 1.7.0 had a similar
> problem, it tried to process non-Subversion POST requests and produced
> an error.  The Subversion problem was fixed in 1.7.2.  A code change in
> mod_wsgi is probably required.  It may be possible to reorder the
> modules in the apache config file.
>

As thread it's not just with mod_wsgi, problem persist with fcgi, can you
please elaborate on reordering I tried moving wsgi module at end but that
did not help.


> --
> Philip
>



-- 
Vishwajeet Singh
+91-9657702154 | dextrous85@gmail.com | http://bootstraptoday.com
Twitter: http://twitter.com/vishwajeets | LinkedIn:
http://www.linkedin.com/in/singhvishwajeet

Re: Subversion 1.7 server & client issue : not able to commit E160013 path not found

Posted by Philip Martin <ph...@wandisco.com>.
vishwajeet singh <de...@gmail.com> writes:

>> > *svn: E160013: Commit failed (details follow):*
>> > *svn: E160013: '/svn/RDR/!svn/me' path not found*
>
>> "SVNAdvertiseV2Protocol off" might be a workaround.
>>
>> Note that there are known issues with httpd-2.4 support in svn with bdb
>> repositories.
>
> I could workaround with that but than I don't get the benefits of new
> protocol.
>
> Just to add I stumbled upon thins thread
> http://mail-archives.apache.org/mod_mbox/httpd-users/201203.mbox/%3Cjkg3qq$a55$1@dough.gmane.org%3E
>
>
> I am facing the exactly the same issue.
>
> I wonder why wsgi and svn would conflict and create such scenario.

mod_wsgi is probably intercepting the POST request intended for
mod_dav_svn and not passing it on.  Subversion 1.7.0 had a similar
problem, it tried to process non-Subversion POST requests and produced
an error.  The Subversion problem was fixed in 1.7.2.  A code change in
mod_wsgi is probably required.  It may be possible to reorder the
modules in the apache config file.

-- 
Philip

Re: Subversion 1.7 server & client issue : not able to commit E160013 path not found

Posted by vishwajeet singh <de...@gmail.com>.
On Mon, Mar 26, 2012 at 5:36 PM, Daniel Shahaf <da...@elego.de> wrote:

> "SVNAdvertiseV2Protocol off" might be a workaround.
>
> Note that there are known issues with httpd-2.4 support in svn with bdb
> repositories.
>

I could workaround with that but than I don't get the benefits of new
protocol.

Just to add I stumbled upon thins thread
http://mail-archives.apache.org/mod_mbox/httpd-users/201203.mbox/%3Cjkg3qq$a55$1@dough.gmane.org%3E


I am facing the exactly the same issue.

I wonder why wsgi and svn would conflict and create such scenario.


>
> vishwajeet singh wrote on Mon, Mar 26, 2012 at 15:13:16 +0530:
> > Hi All,
> >
> > I recently upgraded from subversion server from 1.6 to 1.7, everything
> > works fine for 1.6 client and 1.7 server.
> > But when I upgrade to 1.7 client my commit fails with following error
> >
> > *svn: E160013: Commit failed (details follow):*
> > *svn: E160013: '/svn/RDR/!svn/me' path not found*
> >
> > I am able to checkout and update with 1.7 client but not able to commit.
> >
> > My apache version is 2.3 and OS is centos 5.4.
> >
> > Any help in this regard is appreciated
> >
> > Regards,
> > Vishwajeet Singh
> > +91-9657702154 | dextrous85@gmail.com | http://bootstraptoday.com
> > Twitter: http://twitter.com/vishwajeets | LinkedIn:
> > http://www.linkedin.com/in/singhvishwajeet
>



-- 
Vishwajeet Singh
+91-9657702154 | dextrous85@gmail.com | http://bootstraptoday.com
Twitter: http://twitter.com/vishwajeets | LinkedIn:
http://www.linkedin.com/in/singhvishwajeet

Re: Subversion 1.7 server & client issue : not able to commit E160013 path not found

Posted by Daniel Shahaf <da...@elego.de>.
"SVNAdvertiseV2Protocol off" might be a workaround.

Note that there are known issues with httpd-2.4 support in svn with bdb
repositories. 

vishwajeet singh wrote on Mon, Mar 26, 2012 at 15:13:16 +0530:
> Hi All,
> 
> I recently upgraded from subversion server from 1.6 to 1.7, everything
> works fine for 1.6 client and 1.7 server.
> But when I upgrade to 1.7 client my commit fails with following error
> 
> *svn: E160013: Commit failed (details follow):*
> *svn: E160013: '/svn/RDR/!svn/me' path not found*
> 
> I am able to checkout and update with 1.7 client but not able to commit.
> 
> My apache version is 2.3 and OS is centos 5.4.
> 
> Any help in this regard is appreciated
> 
> Regards,
> Vishwajeet Singh
> +91-9657702154 | dextrous85@gmail.com | http://bootstraptoday.com
> Twitter: http://twitter.com/vishwajeets | LinkedIn:
> http://www.linkedin.com/in/singhvishwajeet

Re: Subversion 1.7 server & client issue : not able to commit E160013 path not found

Posted by Nico Kadel-Garcia <nk...@gmail.com>.
On Mon, Mar 26, 2012 at 5:43 AM, vishwajeet singh <de...@gmail.com>wrote:

> Hi All,
>
> I recently upgraded from subversion server from 1.6 to 1.7, everything
> works fine for 1.6 client and 1.7 server.
> But when I upgrade to 1.7 client my commit fails with following error
>
> *svn: E160013: Commit failed (details follow):*
> *svn: E160013: '/svn/RDR/!svn/me' path not found*
>
> I am able to checkout and update with 1.7 client but not able to commit.
>
> My apache version is 2.3 and OS is centos 5.4.
>
> Backup your system first. Second, you're running CentOS 5.4 (5.8 is out)
and HTTPD 2.3. (The official name is now HTTPD, not Apache, and RHEL
published 2.2.15, not 2.3, their version 5 operating system.) So you're
working with hand-built Apache, and may be working with hand-built
Subversion.

This way lies integration madness. Where did you get each component? The
Subversion RPM's at Repoforge were updated by me to 1.7.3, but you'll
probably want to compile them with a clean HTTPD SRPM and RPM's to get the
libraries cleanly consistent.

Third: serously consider upgrading to CentOS or Scientific Linux 6.x.
You'll be in much better shape for running modern versions of powerful,
constantly upgrading tools like current Subversion releases, rather than
trying to debug old and hand-built systems.


> Any help in this regard is appreciated
>
> Regards,
> Vishwajeet Singh
> +91-9657702154 | dextrous85@gmail.com | http://bootstraptoday.com
> Twitter: http://twitter.com/vishwajeets | LinkedIn:
> http://www.linkedin.com/in/singhvishwajeet
>