On Fri, Mar 16, 2018 at 4:57 PM, Philip Martin wrote:
> Daniel Shahaf writes:
>
>> Philip Martin wrote on Fri, 16 Mar 2018 13:44 +:
>>
>> Changing "0" to "48" would also have broken the and
>> offsets in that revision file, so how come 'verify' worked after
>> that change?
>
> In the exampl
Daniel Shahaf writes:
> Philip Martin wrote on Fri, 16 Mar 2018 13:44 +:
>
> Changing "0" to "48" would also have broken the and
> offsets in that revision file, so how come 'verify' worked after
> that change?
In the examples he gave it looks like the root node itself is being
edited. Th
Philip Martin wrote on Fri, 16 Mar 2018 13:44 +:
> "NOCERA, ANDY" writes:
>
> > I used dump and load to debug the malformed node revision ID. Here
> > are my steps and what learned. Looks like the revs' file text: entry
> > has a zero instead of size. By just editing the size, verify worke
"NOCERA, ANDY" writes:
> I used dump and load to debug the malformed node revision ID. Here
> are my steps and what learned. Looks like the revs' file text: entry
> has a zero instead of size. By just editing the size, verify worked.
> No other change was required. The question is can we corr
[ cc += dev@ ]
NOCERA, ANDY wrote on Thu, 15 Mar 2018 22:35 +:
> Folks,
>
> I used dump and load to debug the malformed node revision ID. Here are
> my steps and what learned. Looks like the revs' file text: entry has
> a zero instead of size.
To be clear, you mean the fourth field.
dmin: E160062: Malformed node revision ID string
Can we edit the revs 'text:" entry instead of a dump a load?
-Original Message-
From: Johan Corveleyn [mailto:jcor...@gmail.com]
Sent: Wednesday, March 07, 2018 6:27 AM
To: NOCERA, ANDY
Cc: users@subversion.apache.org
Subject: Re
On Tue, Mar 6, 2018 at 5:21 PM, NOCERA, ANDY wrote:
> John,
>
> Good feedback.
>
> Svnadmin 1.9 verify is showing the error also. I did a dump and load and it
> resolved that repo.Having reviewed my repos, it looks like around 30%
> have this issue. Not sure what we could have done wrong
response contains invalid XML - svn co and log
issue on some repos using https/http
On Thu, Mar 1, 2018 at 11:52 PM, NOCERA, ANDY wrote:
> I disabled ssl to simplify. I noticed that svn log sometimes stops with an
> error, sometimes it just stops although there is an error in the lo
On Thu, Mar 1, 2018 at 11:52 PM, NOCERA, ANDY wrote:
> I disabled ssl to simplify. I noticed that svn log sometimes stops with an
> error, sometimes it just stops although there is an error in the log. I
> think I need to review the build.Not sure if it’s the SVN side of the
> build or the
[400, #160062]
From: Paul Hammant [mailto:p...@hammant.org]
Sent: Wednesday, February 28, 2018 8:28 AM
To: NOCERA, ANDY
Cc: Andreas Krey ; Michael Rohan ;
users@subversion.apache.org
Subject: Re: E130003: The XML response contains invalid XML - svn co and log
issue on some repos using https
Cc: Andreas Krey ; Michael Rohan ;
users@subversion.apache.org
Subject: Re: E130003: The XML response contains invalid XML - svn co and log
issue on some repos using https/http
As you work toward a conclusion, Andy, do you think there was a different error
message that could have driven you to root cause more quickly?
As you work toward a conclusion, Andy, do you think there was a different
error message that could have driven you to root cause more quickly?
Nice catch
svn co https://scm-uat.web.att.com:6022/svn/asgard svn: E130003: The XML
response contains invalid XML
[an2124@hlth509 test3]$ svn co https://scm-uat.web.att.com:6022/svn/asgard/
svn: E130003: The XML response contains invalid XML
curl -k -u an2124 --insecure https://scm
"NOCERA, ANDY" writes:
> svn co https://xxx.com:6022/svn/asgard
> svn: E130003: The XML response contains invalid XML
If you have the socat proxy available then you can use that to log the
traffic and see the failing XML:
https://subversion.apache.org/docs/community-guide/de
On Wed, 28 Feb 2018 03:21:01 +, NOCERA, ANDY wrote:
> My cert is not valid at this point, I had turned off ssl and had the same
> error. I wasn???t sure how to get beyond the 301 on a curl
You ask for .../asgard, and get redirected to .../asgard/ (note the slash at
the end). Try that.
And
nently
The document has moved https://scm-uat.web.att.com:6022/svn/asgard/";>here.
From: Michael Rohan [mailto:mro...@stonepillar.com]
Sent: Tuesday, February 27, 2018 10:11 PM
To: Paul Hammant
Cc: NOCERA, ANDY ; users@subversion.apache.org
Subject: Re: E130003: The XML response contains
There are several repos work fine and even different version is this repo.
From: Paul Hammant [mailto:p...@hammant.org]
Sent: Tuesday, February 27, 2018 9:44 PM
To: NOCERA, ANDY
Cc: users@subversion.apache.org
Subject: Re: E130003: The XML response contains invalid XML - svn co and log
issue
Hi,
Might be interesting to see what sort of document you are getting:
$ curl https://scm-uat.web.att.com:6022/svn/asgard
Might need "-k" on that command depending on what sort of certs are in
place.
Take care,
Michael.
On Tue, Feb 27, 2018 at 6:44 PM, Paul Hammant wrote:
> Do you get the sa
Do you get the same error with a testfile.txt resource in a freshly created
(and Apache mounted) Subversion repo?
Paul,
Here is the information regarding the logs,
Thanks
Andy
CMD:
svn co https://scm-uat.web.att.com:6022/svn/asgard
svn: E130003: The XML response contains invalid XML
ERROR LOG
[Tue Feb 27 21:31:25.717954 2018] [ssl:info] [pid 18302:tid 140359493441280]
[client IPADDRESS:55820] AH01964
See what you can see on the server-side Apache logs -
https://unix.stackexchange.com/questions/115972/how-do-i-find-where-apache-keeps-the-log-files
(and others; or adjust for your Linux).
-r r1114 having latest
r1115 checkout fail. I was able to checkout 1114 and commit to 1116, however
that didn't fix it, Svnadmin verify returns no errors.
Please advise,
Andy
svn co https://xxx.com:6022/svn/asgard
svn: E130003: The XML response contains invalid XML
svn -v -rr1014 log
On Fri, Apr 24, 2015 at 12:13:53AM -0700, OlePinto wrote:
> Bert Huijben-5 wrote
> > Just to be sure: you get this error during an update?
> >
> > Not during a commit?
>
> Yes, a merge exactly. I even get it if I try the merge with --record-only. I
> was surprised to know that the client download
if we don't use DHCP) we see a
change in NTEContextList. I have two cards, an inactive TeamViewerVPN
Adapter and the real Ethernet card. They had values of 3 and 2 that, after
the enchantment and restart become 2 and 3.
--
View this message in context:
http://subversion.1072662.n5.nabble.com/
> -Original Message-
> From: OlePinto [mailto:olepinto+...@gmail.com]
> Sent: woensdag 22 april 2015 16:25
> To: users@subversion.apache.org
> Subject: RE: The XML response contains invalid XML
>
> Bad news: it has happened again. I haven't installed anything
nformation, traces or whatever, feel free to ask
and I'll try to oblige.
--
View this message in context:
http://subversion.1072662.n5.nabble.com/The-XML-response-contains-invalid-XML-tp186929p193077.html
Sent from the Subversion Users mailing list archive at Nabble.com.
test (no
change).
--
View this message in context:
http://subversion.1072662.n5.nabble.com/The-XML-response-contains-invalid-XML-tp186929p193061.html
Sent from the Subversion Users mailing list archive at Nabble.com.
> -Original Message-
> From: OlePinto [mailto:olepinto+...@gmail.com]
> Sent: dinsdag 21 april 2015 12:20
> To: users@subversion.apache.org
> Subject: Re: The XML response contains invalid XML
>
> We have finally fixed it, although we sadly do not really know what the
successful and failed transactions.
I randomly get also "E125012: Invalid character in hex checksum"; maybe it
has any relation to the former, maybe not.
Any idea? Any other test or information that could be useful?
--
View this message in context:
http://subversion.1072662.n5.nabble.c
.
Did it help anyone else?
--
View this message in context:
http://subversion.1072662.n5.nabble.com/The-XML-response-contains-invalid-XML-tp186929p193059.html
Sent from the Subversion Users mailing list archive at Nabble.com.
Seems like SVN is confused about the Repository Name.
Rename the Repository and the try the check out.
The name you are using was used before by SVN and it is confusing the XML
file.
--
View this message in context:
http://subversion.1072662.n5.nabble.com/The-XML-response-contains-invalid-XML
I am seeing the same thing.
Here's my problem:
I had a sub directory in my repo that contained a library that was 2 levels
deep. (eg. directory structure ProjectA/lib/releases)
I deleted the lib directory and replaced it with an external that had a
slightly different structure (lib/releases/v1
Ryan Schmidt [mailto:subversion-2...@ryandesign.com]
Sent: Thursday, 6 February 2014 1:08 PM
To: Daren Hawes
Cc: Subversion Users
Subject: Re: The XML response contains invalid XML
On Feb 5, 2014, at 00:05, Daren Hawes wrote:
> I was hoping someone has seen this error before. It randomly happens
On Feb 5, 2014, at 00:05, Daren Hawes wrote:
> I was hoping someone has seen this error before. It randomly happens when we
> SVN Checkout.
>
> We have a Windows 2012 Server with SVN 1.8.5 installed. We use Visual SVN
> 1.8.4 to manage this Server.
>
> The Sub Version data folder is on a NA
I've seen a problem something like this that stemmed from using a broken
migration tool. Data migrated from some other version control system,
into Subversion yielded some characters not properly encoded the way the
client expects it. I suspect something similar (except for properties of
a file
On 2/4/14, 10:05 PM, Daren Hawes wrote:
> I was hoping someone has seen this error before. It randomly happens when we
> SVN Checkout.
>
>
>
> We have a Windows 2012 Server with SVN 1.8.5 installed. We use Visual SVN
> 1.8.4
> to manage this Server.
>
>
>
> The Sub Version data folder is o
36 matches
Mail list logo
