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
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 to cause it. A real
simple repo is mine and has only a
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
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 httpd side.
Looks like a dav error.
[Thu Mar 01
I have seen a different result from svn log and I can cherry pick around and
see some expected output.
The curl output below has… "~$ployment%20to%20Test.doc">~$ployment to
Test.dochttps://scm-uat.web.att.com:6022/svn/asgard
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
"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:
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.
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
curl -k -u an2124 --insecure https://scm-uat.web.att.com:6022/svn/asgard
Enter host password for user 'an2124':
301 Moved Permanently
Moved Permanently
The
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
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 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).
15 matches
Mail list logo