RE: E130003: The XML response contains invalid XML - svn co and log issue on some repos using https/http

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 few commits shows the error. Is there a correction method quicker than a dump and load?

Thanks
Andy

-----Original Message-----
From: Johan Corveleyn [mailto:jcorvel_at_gmail.com]
Sent: Friday, March 02, 2018 5:12 AM
To: NOCERA, ANDY <an2124_at_att.com>
Cc: users_at_subversion.apache.org
Subject: Re: E130003: The XML 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 <an2124_at_att.com> 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 httpd side.
>
> Looks like a dav error.
>
>
> [Thu Mar 01 17:42:06.060588 2018] [dav:error] [pid 116212:tid
> 140359367563008] [client 135.161.105.164:50294] Malformed node
> revision ID string [400, #160062]
>
> [Thu Mar 01 17:42:37.356665 2018] [dav:error] [pid 112152:tid
> 140359566870272] [client 135.161.105.164:50356] Malformed node
> revision ID string [400, #160062]
>
> [Thu Mar 01 17:43:42.230627 2018] [dav:error] [pid 116212:tid
> 140359556380416] [client 135.161.105.164:50496] Provider encountered
> an error while streaming a REPORT response. [400, #0]
>
> [Thu Mar 01 17:43:42.230635 2018] [dav:error] [pid 116212:tid
> 140359556380416] [client 135.161.105.164:50496] Malformed node
> revision ID string [400, #160062]
>
> [Thu Mar 01 17:44:17.410198 2018] [dav:error] [pid 116212:tid
> 140359482951424] [client 135.161.105.164:50564] Provider encountered
> an error while streaming a REPORT response. [400, #0]
>
> [Thu Mar 01 17:44:17.410222 2018] [dav:error] [pid 116212:tid
> 140359482951424] [client 135.161.105.164:50564] Malformed node
> revision ID string [400, #160062]
>
> [Thu Mar 01 17:45:56.025740 2018] [dav:error] [pid 112151:tid
> 140359598339840] [client 135.161.105.164:50770] Provider encountered
> an error while streaming a REPORT response. [400, #0]
>
> [Thu Mar 01 17:45:56.025755 2018] [dav:error] [pid 112151:tid
> 140359598339840] [client 135.161.105.164:50770] Malformed node
> revision ID string [400, #160062]
>
> [Thu Mar 01 17:46:26.431448 2018] [dav:error] [pid 112166:tid
> 140359430502144] [client 135.161.105.164:50828] Malformed node
> revision ID string [400, #160062]

Hm, that doesn't really look good. The error "Malformed node revision ID string" might point to a corruption in the repository. I've googled a bit for this error message, and it seems to have been introduced in this commit (was first release in 1.9.0):

https://urldefense.proofpoint.com/v2/url?u=http-3A__svn.apache.org_viewvc-3Fview-3Drevision-26revision-3D1622942&d=DwIFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=lHImfy5Z3mUV3q_wXtPXpg&m=rFH5IX7EXYt55-yQnCTUOrUCv4Od_w2GtobSitt66JM&s=I9CI2W0V7iYKSAgqLkGr4Fueh5T0mdesoT_0WkgTexE&e=

You said before that "svnadmin verify" did not report errors. Did you use a 1.8 svnadmin, or a 1.9 svnadmin for that? It seems to me that the verification was made more stringent in 1.9, thus detecting this kind of corruption (where a malformed nod revision ID is in the back-end data somewhere).

Maybe you should try to dump+load this repository into a new one, to see if that fixes it.

--
Johan