AW: E175012 and E175002 when trying to commit

2019-04-04 Thread Christoph Vogtländer
Hi Pavel, > Von: Pavel Lyalyakin [mailto:pavel.lyalya...@visualsvn.com] > Gesendet: Donnerstag, 4. April 2019 15:18 > > I see that you use VisualSVN Server. But do you use VDFS (Multisite > Repository Replication)? Do you see the following error when you commit to a > slave VDFS repository? > [[

Re: E175012 and E175002 when trying to commit

2019-04-04 Thread Pavel Lyalyakin
Hello Christoph, On Thu, Apr 4, 2019 at 12:39 PM Christoph Vogtländer < christoph.vogtlaen...@sigma-surface-science.com> wrote: > I have now a working setup with > > LimitXMLRequestBody 3200 > Timeout 36000 > > I can successfully commit the change-set using LANG=de_DE.UTF-8, > LANG=en_GB.UTF-

AW: E175012 and E175002 when trying to commit

2019-04-04 Thread Christoph Vogtländer
I have now a working setup with LimitXMLRequestBody 3200 Timeout 36000 I can successfully commit the change-set using LANG=de_DE.UTF-8, LANG=en_GB.UTF-8 or LC_TYPE=C To wrap this up: It seems there is a bug when using de_DE.UTF-8. The commit should be denied in case the XML request body is

AW: E175012 and E175002 when trying to commit

2019-04-03 Thread Christoph Vogtländer
will fail with E175012 (but with different "details"): svn: E175012: Übertragen schlug fehl (Details folgen): svn: E175012: Die Wartezeit für die Verbindung ist abgelaufen svn: E200042: Zusätzliche Fehler: svn: E175002: Unerwarteter Serverfehler 500 »Internal Server Error« auf »/svn/ThirdP

AW: E175012 and E175002 when trying to commit

2019-04-03 Thread Christoph Vogtländer
> Von: Johan Corveleyn [mailto:jcor...@gmail.com] > Gesendet: Mittwoch, 3. April 2019 10:18 > Perhaps the difference between your first and second attempt is not > caused by different language settings, but because the working copy > was in a different state? For instance, if the "base" of your wor

Re: E175012 and E175002 when trying to commit

2019-04-03 Thread Johan Corveleyn
On Tue, Apr 2, 2019 at 10:20 PM Daniel Shahaf wrote: > > Christoph Vogtländer wrote on Tue, 02 Apr 2019 09:02 +00:00: > > This is reproducible. Running with de_DE.UTF-8 (my default LANG), svn > > will try to submit the change but runs into a time-out. Running with > > en_GB.UTF-8, svn fails with e

Re: E175012 and E175002 when trying to commit

2019-04-02 Thread Daniel Shahaf
Christoph Vogtländer wrote on Tue, 02 Apr 2019 09:02 +00:00: > This is reproducible. Running with de_DE.UTF-8 (my default LANG), svn > will try to submit the change but runs into a time-out. Running with > en_GB.UTF-8, svn fails with error 413. > > Why is subversion acting differently with diffe

E175012 and E175002 when trying to commit

2019-04-02 Thread Christoph Vogtländer
to get the message in English. But, changing LANG also changed the behaviour. The client no longer tries to submit the transaction at all but fails straight away with: $> LANG=en_GB.UTF-8 svn ci -F svn-commit.tmp . svn: E175002: Commit failed (details follow): svn: E175002: Unexpected HTTP

Re: svnsync: E175002: REPORT request on '//!svn/rev/' failed

2018-12-28 Thread Daniel Shahaf
Nick Burkitt wrote on Fri, 28 Dec 2018 10:19 -0800: > I contacted CollabNet, and while they didn't find a solution to the > svnsync problem per se, they did provide instructions for creating a > local backup using "snvrdump dump" and "svnadmin load." Interesting. 'svnrdump dump' and 'svnsync sy

RE: svnsync: E175002: REPORT request on '//!svn/rev/' failed

2018-12-28 Thread Nick Burkitt
- 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 proc

RE: svnsync: E175002: REPORT request on '//!svn/rev/' failed

2018-12-17 Thread Nick Burkitt
ts 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.

Re: svnsync: E175002: REPORT request on '//!svn/rev/' failed

2018-12-17 Thread Daniel Shahaf
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

Re: svnsync: E175002: REPORT request on '//!svn/rev/' failed

2018-12-17 Thread Daniel Shahaf
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 a

svnsync: E175002: REPORT request on '//!svn/rev/' failed

2018-12-16 Thread Nick Burkitt
P_REPO%\hooks\pre-revprop-change.bat svnsync init file:///%BACKUP_REPO% %SOURCE_REPO% svnsync sync file:///%BACKUP_REPO% end The operation proceeds without problems until it gets to revision 71, at which point it fails with the error "svnsync: E175002: REPORT request

Re: svn: E175002: Unexpected HTTP status 418 ' Not Found'

2016-03-30 Thread Stefan Hett
Hi Jordi, Dear svn users We are trying to perform a commit of an added file to a folder already in the repository server. A changed file works fine, however when we try to commit an added file the following error is reported: svn: E175002: Commit failed (details follow): svn: E175002

svn: E175002: Unexpected HTTP status 418 ' Not Found'

2016-02-24 Thread Duatis Juarez, Jordi
Dear svn users We are trying to perform a commit of an added file to a folder already in the repository server. A changed file works fine, however when we try to commit an added file the following error is reported: svn: E175002: Commit failed (details follow): svn: E175002: Unexpected HTTP

RE: E175002

2015-07-13 Thread Bert Huijben
Bert From: Somashekarappa, Anup (CWM-NR) [mailto:anup.somashekara...@rbc.com] Sent: maandag 13 juli 2015 15:26 To: 'users@subversion.apache.org' Subject: E175002 Hi, We are frequently getting the below error when trying to downloading svn data from jenkins. Issue will get

E175002

2015-07-13 Thread Somashekarappa, Anup (CWM-NR)
ery=org.tmatesoft.svn.core.SVNException>: svn: E175002: OPTIONS /svn/repo/trunk failed Caused by: java.io.IOException: Remote call on channel failed at hudson.remoting.Channel.call(Channel.java:760) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:173) ... 3

Re: Error E175002 on large commit

2014-11-10 Thread Torge Riedel
Hi I am using svn_load_dirs.pl to commit a large vendor library to our svn 1.8 repo. The client is svn v.1.7.9. The script fails when it attempts to commit the files: Transmitting file data svn: E175002: Commit failed (details follow): svn: E175002: PUT of '/subversion//!svn

Error E175002 on large commit

2014-11-10 Thread David Aldrich
Hi I am using svn_load_dirs.pl to commit a large vendor library to our svn 1.8 repo. The client is svn v.1.7.9. The script fails when it attempts to commit the files: Transmitting file data svn: E175002: Commit failed (details follow): svn: E175002: PUT of '/subversion/

updated to Fedora 21 alpha, now getting "svn: E175002: Unexpected HTTP status 500 'Internal Server Error'"

2014-10-30 Thread Brian Johnson
uot; on my local machine, I got the error: svn: E175002: Unable to connect to a repository at URL 'https:///repos' svn: E175002: Unexpected HTTP status 500 'Internal Server Error' on '/repos' svn: E175002: Additional errors: svn: E175002: OPTIONS request on '/

Re: Merge fails: E175002: REPORT request on '/svn/FOO/!svn/me' failed

2014-04-16 Thread Johan Corveleyn
r : https://server/svn/FOO/path/to/merge/from working_dir > --- Merging r through r into 'working_dir' > Uworking_dir\dir1\foo.htm > ... > Cworking_dir\dir2\bar.c_bak > [Long delay] > Summary of conflicts: >Text conflicts: 5 > svn: E175002:

Merge fails: E175002: REPORT request on '/svn/FOO/!svn/me' failed

2014-04-13 Thread James Crofts
r\dir1\foo.htm ... Cworking_dir\dir2\bar.c_bak [Long delay] Summary of conflicts: Text conflicts: 5 svn: E175002: REPORT request on '/svn/FOO/!svn/me' failed Server: VisualSVN 2.5.8 Client: Windows 7 64-bit svn, version 1.8.8 (r1568071) compiled Feb 18 2014, 20:42:30 on x8

RE: svn: E175002: Server sent unexpected return value (500 Internal Server Error)

2012-01-18 Thread Fridman Galit-R58634
, Galit -Original Message- From: Daniel Shahaf [mailto:danie...@elego.de] Sent: Wednesday, January 18, 2012 12:41 PM To: Fridman Galit-R58634 Cc: users@subversion.apache.org Subject: Re: svn: E175002: Server sent unexpected return value (500 Internal Server Error) What does httpd's

Re: svn: E175002: Server sent unexpected return value (500 Internal Server Error)

2012-01-18 Thread Daniel Shahaf
is an example: > svn ci -m 'release > notes: license server' doc/release_notes.txt Authentication realm: > <http://xx:18080> > CollabNet Subversion Repository > Password for 'user': > svn: E175002: Commit failed (details follow): > svn: E175002: Unab

svn: E175002: Server sent unexpected return value (500 Internal Server Error)

2012-01-18 Thread Fridman Galit-R58634
80> CollabNet Subversion Repository Password for 'user': svn: E175002: Commit failed (details follow): svn: E175002: Unable to connect to a repository at URL 'http://xx:18080/svn/rocoo/trunk/doc' svn: E175002: Server sent unexpected return value (500 Internal Server Error

Re: E175002: Server sent unexpected return value (500 Internal Server Error) in response to POST request for '/repos/svntest/!svn/me'

2012-01-05 Thread Daniel Shahaf
Pierre Berthier wrote on Thu, Jan 05, 2012 at 10:12:56 +0100: > I have now reduced my configuration to two variations, the following > works fine: > (Thanks for the additional details, it's _much_ easier to respond usefully given them.) > I am now wondering if that should be considered a bug at

Re: E175002: Server sent unexpected return value (500 Internal Server Error) in response to POST request for '/repos/svntest/!svn/me'

2012-01-05 Thread Philip Martin
Pierre Berthier writes: > > DAV svn > SVNParentPath /srv/svn/repos/ > SVNListParentPath on > AuthzSVNAccessFile /etc/apache2/svnaccess.conf > AuthzSVNAnonymous Off > AuthzSVNAuthoritative On > SVNPathAuthz Off > > AuthType Basic > AuthNam

Re: E175002: Server sent unexpected return value (500 Internal Server Error) in response to POST request for '/repos/svntest/!svn/me'

2012-01-05 Thread Pierre Berthier
On Thu, 22 Dec 2011 22:58:44 +0100 Pierre Berthier wrote: > Hi > > after upgrading a SVN server from 1.6 to 1.7.2 (r1207936), I am > getting this error message when committing: > > svn: E175002: Commit failed (details follow): > svn: E175002: Server sent unexpected retur

Re: E175002: Server sent unexpected return value (500 Internal Server Error) in response to POST request for '/repos/svntest/!svn/me'

2012-01-04 Thread Daniel Shahaf
Pierre Berthier wrote on Wed, Jan 04, 2012 at 15:09:45 +0100: > On Thu, 22 Dec 2011 22:58:44 +0100 > Pierre Berthier wrote: > > > Hi > > > > after upgrading a SVN server from 1.6 to 1.7.2 (r1207936), I am > > getting this error message when committing: >

Re: E175002: Server sent unexpected return value (500 Internal Server Error) in response to POST request for '/repos/svntest/!svn/me'

2012-01-04 Thread Daniel Shahaf
Pierre Berthier wrote on Thu, Dec 22, 2011 at 22:58:44 +0100: > Hi > > after upgrading a SVN server from 1.6 to 1.7.2 (r1207936), I am getting > this error message when committing: > > svn: E175002: Commit failed (details follow): > svn: E175002: Server sent unexpected retur

Re: E175002: Server sent unexpected return value (500 Internal Server Error) in response to POST request for '/repos/svntest/!svn/me'

2012-01-04 Thread Pierre Berthier
On Thu, 22 Dec 2011 22:58:44 +0100 Pierre Berthier wrote: > Hi > > after upgrading a SVN server from 1.6 to 1.7.2 (r1207936), I am > getting this error message when committing: > > svn: E175002: Commit failed (details follow): > svn: E175002: Server sent unexpected retur

E175002: Server sent unexpected return value (500 Internal Server Error) in response to POST request for '/repos/svntest/!svn/me'

2011-12-22 Thread Pierre Berthier
Hi after upgrading a SVN server from 1.6 to 1.7.2 (r1207936), I am getting this error message when committing: svn: E175002: Commit failed (details follow): svn: E175002: Server sent unexpected return value (500 Internal Server Error) in response to POST request for '/repos/svntest/!svn/me&

Re: E175002: The POST request returned invalid XML in the response: XML parse error

2011-12-20 Thread Philip Martin
Mojca Miklavec writes: > I first need > to figure out how to use wireshark. Is there any chapter in SVN > documentation explaining how to troubleshoot problems with subversion > on a network level? And if not - would it be feasible to prepare one? http://subversion.apache.org/docs/community-guid

Re: E175002: The POST request returned invalid XML in the response: XML parse error

2011-12-20 Thread Daniel Shahaf
Daniel Shahaf wrote on Tue, Dec 20, 2011 at 02:43:48 +0200: > > I then added a new directory with a bunch of files and wanted to > > commit, but it complained with: > > > > > svn ci -m "some comment" > > svn: E175002: Commit failed (details follow):

Re: E175002: The POST request returned invalid XML in the response: XML parse error

2011-12-20 Thread Daniel Shahaf
Mojca Miklavec wrote on Tue, Dec 20, 2011 at 09:53:46 +0100: > On Tue, Dec 20, 2011 at 01:43, Daniel Shahaf wrote: > > Can you capture the XML response on the wire and share it here?  (with > > wireshark, or neon-debug-mask)  If it contains sensitive stuff feel free > > to share it by private mail.

Re: E175002: The POST request returned invalid XML in the response: XML parse error

2011-12-20 Thread Mojca Miklavec
On Tue, Dec 20, 2011 at 02:34, Philip Martin wrote: > Mojca Miklavec writes: > >>> svn ci -m "some comment" >> svn: E175002: Commit failed (details follow): >> svn: E175002: The POST request returned invalid XML in the response: >> XML parse erro

Re: E175002: The POST request returned invalid XML in the response: XML parse error

2011-12-20 Thread Mojca Miklavec
On Tue, Dec 20, 2011 at 01:43, Daniel Shahaf wrote: > Mojca Miklavec wrote on Mon, Dec 19, 2011 at 16:56:05 +0100: >> >> May I ask for any hints of what could go wrong and how I could debug >> the problem? I have seen various threads after searching with google, >> but none of those that I checked

Re: E175002: The POST request returned invalid XML in the response: XML parse error

2011-12-19 Thread Philip Martin
Mojca Miklavec writes: >> svn ci -m "some comment" > svn: E175002: Commit failed (details follow): > svn: E175002: The POST request returned invalid XML in the response: > XML parse error at line 3: not well-formed (invalid token) > (/suite/!svn/me) One thing that

Re: E175002: The POST request returned invalid XML in the response: XML parse error

2011-12-19 Thread Daniel Shahaf
(r1207936) >compiled Dec 9 2011, 21:54:16 > > > I then added a new directory with a bunch of files and wanted to > commit, but it complained with: > > > svn ci -m "some comment" > svn: E175002: Commit failed (details follow): > svn: E175002: The PO

E175002: The POST request returned invalid XML in the response: XML parse error

2011-12-19 Thread Mojca Miklavec
; svn ci -m "some comment" svn: E175002: Commit failed (details follow): svn: E175002: The POST request returned invalid XML in the response: XML parse error at line 3: not well-formed (invalid token) (/suite/!svn/me) May I ask for any hints of what could go wrong and how I could deb

svn: E175002: REPORT of '/repositoryname/!svn/me': SSL handshake failed: SSL error: parse tlsext (https://svn.domain.tld)

2011-12-08 Thread Balogh Péter
Hi, I've got the error message in the subject a few times, but after 1 or 2 retries, the update command succeeds. The interesting part is that the command is executed on the server, where the svn is located. Does anybody know, how to fix this? Thank you for your help, Best regards, Peter Bal

Re: E175002 error checking out from svgweb

2011-11-03 Thread ross
et's 1.6.5 commandline client on MS Windows XP. What are > your system settings? > > > This results in: > > > svn: E175002: Unable to connect to a repository at URL 'http:// > > svgweb.googlecode.com/svn/trunk' > > svn: E175002: OPTIONS of 'http:/

Re: E175002 error checking out from svgweb

2011-11-03 Thread ross
et's 1.6.5 commandline client on MS Windows XP. What are > your system settings? > > > This results in: > > > svn: E175002: Unable to connect to a repository at URL 'http:// > > svgweb.googlecode.com/svn/trunk' > > svn: E175002: OPTIONS of 'http:/

Re: E175002 error checking out from svgweb

2011-11-03 Thread Ulrich Eckhardt
hould just list the content of the repository there, to see to what extent the connection works or not. This works fine from here, using CollabNet's 1.6.5 commandline client on MS Windows XP. What are your system settings? This results in: svn: E175002: Unable to connect to a reposit

E175002 error checking out from svgweb

2011-11-03 Thread ross
I'm trying to checkout the svgweb source and using the documented svn command (slik windows 32 or 64 bit version): svn checkout http://svgweb.googlecode.com/svn/trunk/ svgweb-read-only This results in: svn: E175002: Unable to connect to a repository at URL 'http:// svgweb.googleco