[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Error on Update/Checkout: Invalid XML

From: Thomas Schulze <thomas_at_dreamworlds.de>
Date: 2007-01-19 18:55:44 CET

Hello,

until some days ago I was a happy subversion user, it served our
small-scale game development very well. But some days ago we had a quite
large commit (approx. 50Mb) and since then every update or clean checkout
failes somewhere in the process:

Error: REPORT request failed on '/svn/zdf/!svn/vcc/default'
Error: The REPORT request returned invalid XML in the response: XML parse
error at line
Error: 24814: no element found (/svn/zdf/!svn/vcc/default)

It doesn't state on which file it fails, but it must be some of the new
textures added in that large checkin. I haven't found a way to display the
erroneous XML data. Isolated updates of other subfolders worked just fine.
Fresh checkout to a different dir produces the error message as well and
others have reported similar problems when updating. The only one without
problems is the machine the data was commited from.

Environment: Subversion server runs on WinXP, Apache2.0. At the time of the
first encounter, we used SVN 1.2.1. Client is SVN 1.2.1 as well, with
TortoiseSVN as frontend. In the meantime I made a copy of the repos and
then updated server and client to V1.4.2, but that didn't help. I tried
"svnadmin recover" but it didn't help, too. Propably because I don't use
the Berkeley db but the native filesystem.

I googled for the error message and found serveral hints. One was caused by
illegal characters in the commit message but this doesn't apply to us. The
log of the repos is fine, replacing the commit log entry with svnadmin
didn't change a thing. Another hint was to "just keep trying, it eventually
works", but now several days are gone and the problem persists. The
remaining threads where someone had a similar problem got no hints but
mainly "send a recipe" answers. I don't know what exactly a "recipe" is in
this context but if svnadmin can produce one I'm glad to provide it. The
repos is 350 MB in size at the moment, so it's still in a range where you
can compress it and upload it to some FTP server.

What else can I do to solve this problem? Any hint is appreciated. Thanks
in advance.

Bye, Thomas

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 19 18:56:18 2007

This is an archived mail posted to the Subversion Users mailing list.