Re: svnsync: E175002: REPORT request on '//!svn/rev/' failed
Nick Burkitt wrote on Fri, 14 Dec 2018 12:36 -0800: > The operation proceeds without problems until it gets to revision 71, at > which point it fails with the error "svnsync: E175002: REPORT request on > '//!svn/rev/71' failed". I've looked at all the related answers I > could find, but none of them address this specific problem. > The error code is SVN_ERR_RA_DAV_REQUEST_FAILED, which doesn't add information. > I'd be okay with losing the first 70 revisions, but I have no idea how to > get past this point. I wouldn't resort to that yet. Do you have previous backups of these revisions? Does «svn checkout %SOURCE_REPO%@71» succeed? If either of these works, you should be able to work around the error in r71. Furthermore, — > The master is on a CollabNet CloudForge account, so I have no visibility > into the server side - not even SVN version. I can view revs 69 through 72 > using the repo browser without detecting any problems. > The standard next step is to look in the server's log for errors. If you don't have access to it yourself, then you should contact your hosting provider. If you do this, you hopefully wouldn't have to discard the first 70 revisions (not to mention that based on the information available, we can't rule out the possibility that _later_ revisions will have the same error). > The client is TortoiseSVN (command line utilities): > PS E:\svn> svnsync --version > svnsync, version 1.11.0 (r1845130) > compiled Oct 30 2018, 21:50:05 on x86-microsoft-windows > > How do I go about analyzing this problem? Are there diagnostic tools? Log > files? Guys who just know the answer? As I said, my first recommendation is to talk to your hosting provider. If you do this, you might skip the middleman and ask them to run 'svnadmin dump --deltas foo' and send you the resulting file. If you they don't figure it out, _then_ would be the time to start doing fancier things (wireshark, workarounds using previous backups and/or 'svn checkout', etc). Cheers, Daniel
Re: svnsync: E175002: REPORT request on '//!svn/rev/' failed
Nick Burkitt wrote on Fri, 14 Dec 2018 12:36 -0800: > Committed revision 69. > Copied properties for revision 69. > Transmitting file data ... > Committed revision 70. > Copied properties for revision 70. > svnsync: E175002: REPORT request on '//!svn/rev/71' failed > PS E:\svn> > end > > I'd be okay with losing the first 70 revisions, but I have no idea how to > get past this point. If you run 'svnsync sync file:///E:/svn/foo' again at this point, does it fail again in the same way?
ra-serf missing from SVN Client for windows 1.11
Hi, It looks like ra-serf is missing from svn 1.11 client for windows Svn -version svn, version 1.11.0 (r1845130) compiled Nov 1 2018, 12:47:00 on x86/x86_64-microsoft-windows10.0.17134 Copyright (C) 2018 The Apache Software Foundation. This software consists of contributions made by many people; see the NOTICE file for more information. Subversion is open source software, see http://subversion.apache.org/ The following repository access (RA) modules are available: * ra_svn : Module for accessing a repository using the svn network protocol. - handles 'svn' scheme * ra_local : Module for accessing a repository on local disk. - handles 'file' scheme For 1.10 svn --version svn, version 1.10.2 (r1835932) compiled Aug 30 2018, 11:56:10 on x86/x86_64-microsoft-windows10.0.17134 Copyright (C) 2018 The Apache Software Foundation. This software consists of contributions made by many people; see the NOTICE file for more information. Subversion is open source software, see http://subversion.apache.org/ The following repository access (RA) modules are available: * ra_svn : Module for accessing a repository using the svn network protocol. - handles 'svn' scheme * ra_local : Module for accessing a repository on local disk. - handles 'file' scheme * ra_serf : Module for accessing a repository via WebDAV protocol using serf. - using serf 1.3.9 (compiled with 1.3.9) - handles 'http' scheme - handles 'https' scheme Michael Cotrut Consultant, DevCentre Canada Border Services Agency Place Vanier, 333 North River road, 17th floor, Tower A, 17th Floor 17077 Ottawa, Ontario 343-291-6097 Office
Re: ra-serf missing from SVN Client for windows 1.11
On Mon, Dec 17, 2018 at 12:54 PM Cotrut, Michael < michael.cot...@cbsa-asfc.gc.ca> wrote: > Hi, > > It looks like ra-serf is missing from svn 1.11 client for windows > > > > Svn –version > > svn, version 1.11.0 (r1845130) > >compiled Nov 1 2018, 12:47:00 on x86/x86_64-microsoft-windows10.0.17134 > > > > Copyright (C) 2018 The Apache Software Foundation. > > This software consists of contributions made by many people; > > see the NOTICE file for more information. > > Subversion is open source software, see http://subversion.apache.org/ > > > > The following repository access (RA) modules are available: > > > > * ra_svn : Module for accessing a repository using the svn network > protocol. > > - handles 'svn' scheme > > * ra_local : Module for accessing a repository on local disk. > > - handles 'file' scheme > > > > > > For 1.10 > > svn --version > > svn, version 1.10.2 (r1835932) > >compiled Aug 30 2018, 11:56:10 on x86/x86_64-microsoft-windows10.0.17134 > > > > Copyright (C) 2018 The Apache Software Foundation. > > This software consists of contributions made by many people; > > see the NOTICE file for more information. > > Subversion is open source software, see http://subversion.apache.org/ > > > > The following repository access (RA) modules are available: > > > > * ra_svn : Module for accessing a repository using the svn network > protocol. > > - handles 'svn' scheme > > * ra_local : Module for accessing a repository on local disk. > > - handles 'file' scheme > > * *ra_serf : Module for accessing a repository via WebDAV protocol using > serf.* > > * - using serf 1.3.9 (compiled with 1.3.9)* > > * - handles 'http' scheme* > > * - handles 'https' scheme* > > > The Subversion project does not provide binaries, so you should report this to whomever or wherever you obtained them. You are right that it looks like they were not built properly and/or did not include all of the libraries needed for http support. -- Thanks Mark Phippard http://markphip.blogspot.com/
RE: svnsync: E175002: REPORT request on '//!svn/rev/' failed
Hi Daniel. Thanks very much for your help! I'll try getting in touch with CloudForge. In the meantime, to address your questions: * No, I have no previous backups - this is my first attempt to create one. * Yes, I am able to check out version 71 - svn checkout %SOURCE_REPO%@71 reports no errors. * Yes, if I repeat the sync command, it fails with the same error: E:\svn>svnsync sync file:///E:/backuprepo_01 svnsync: E175002: REPORT request on '!svn/rev/71' failed Thanks again, -Nick -Original Message- From: Daniel Shahaf [mailto:d...@daniel.shahaf.name] Sent: Monday, 17 December, 2018 01:56 To: Nick Burkitt ; users@subversion.apache.org Subject: Re: svnsync: E175002: REPORT request on '//!svn/rev/' failed Nick Burkitt wrote on Fri, 14 Dec 2018 12:36 -0800: > The operation proceeds without problems until it gets to revision 71, > at which point it fails with the error "svnsync: E175002: REPORT > request on '//!svn/rev/71' failed". I've looked at all the > related answers I could find, but none of them address this specific problem. > The error code is SVN_ERR_RA_DAV_REQUEST_FAILED, which doesn't add information. > I'd be okay with losing the first 70 revisions, but I have no idea how > to get past this point. I wouldn't resort to that yet. Do you have previous backups of these revisions? Does «svn checkout %SOURCE_REPO%@71» succeed? If either of these works, you should be able to work around the error in r71. Furthermore, — > The master is on a CollabNet CloudForge account, so I have no > visibility into the server side - not even SVN version. I can view > revs 69 through 72 using the repo browser without detecting any problems. > The standard next step is to look in the server's log for errors. If you don't have access to it yourself, then you should contact your hosting provider. If you do this, you hopefully wouldn't have to discard the first 70 revisions (not to mention that based on the information available, we can't rule out the possibility that _later_ revisions will have the same error). > The client is TortoiseSVN (command line utilities): > PS E:\svn> svnsync --version > svnsync, version 1.11.0 (r1845130) > compiled Oct 30 2018, 21:50:05 on x86-microsoft-windows > > How do I go about analyzing this problem? Are there diagnostic tools? > Log files? Guys who just know the answer? As I said, my first recommendation is to talk to your hosting provider. If you do this, you might skip the middleman and ask them to run 'svnadmin dump --deltas foo' and send you the resulting file. If you they don't figure it out, _then_ would be the time to start doing fancier things (wireshark, workarounds using previous backups and/or 'svn checkout', etc). Cheers, Daniel
