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

Checkout over HTTP fails with seemingly random errors

From: Bryan Dyck <bdyck_at_mac.com>
Date: 2005-06-22 21:00:50 CEST

After poking somewhat methodically at this, I'm not getting anywhere,
so it's time to ask the experts. :)

First, a short leadup to the problem: I recently upgraded my
Subversion box to OS X 10.4, which of course entails rebuilding the
necessary components to get Subversion running again. I was
previously using the fink packages, but decided to be less lazy this
time around and build everything myself. My current setup includes
the following:

APR/APR-Util 0.9.6 (I built this separately to make double-certain
that Apache and Subversion use the same APR)
Neon 0.24.7 (also built separately from Subversion)
Apache 2.0.54
Subversion 1.2.0
SWIG 1.3.21 (not really relevant to this, but it's there)

I have not installed BDB, as I've had no problems with using an FSFS
backend and didn't feel there were any advantages (for me) to have
the option of a BDB backend.

After building everything and setting up Apache (with the Subversion
modules built as DSOs), I proceeded to recreate the repository and
loaded my dumpfile back in. The problems began when I did a cursory
checkout to see if everything was working properly - it wasn't. The
checkout failed, and subsequent attempts also failed with a seemingly
random assortment of errors:

svn: Invalid diff stream: [tgt] insn 1 starts beyond the target view
position

svn: Unexpected end of svndiff input

svn: REPORT request failed on '/svn/prima-survey/!svn/vcc/default'
svn: REPORT of '/svn/prima-survey/!svn/vcc/default': Chunk delimiter
was invalid

svn: Checksum mismatch for 'prima-survey/lib/log4j-1.2.9.jar';
expected: 'c2ced5f8505fe9d1cae685201e9cba07', actual:
'be72ae3be573c017a8906647c8b13dd4'

These occurred in no particular order, and sometimes at different
points in the checkout. Having not once had even a hint of a problem
with the actual operation of Subversion, this was rather disturbing
to me. The checksum failure occurred only a couple times, but that
and the REPORT failure led me to initially wonder if the repository
was corrupted, so I ran 'svnadmin verify' on it, which came back with
no errors.

Googling for the various error messages didn't really produce
anything terribly interesting, other than that other people have
apparently suffered similar problems, some of which seemed to be
traced back to a repository that had become corrupt at some point.
I'm fairly certain that my repository isn't corrupt, partly because
I've never had a problem committing to it (it's fairly young; only 31
revisions), and partly because I can run a checkout just fine if I
use a file:// URL.

Thus far, I have disabled HTTP compression in the client-side SVN
options (I built Apache with mod_deflate), and I have changed
Apache's LogLevel to debug, which hasn't produced much of note other
than this:

[info] (35)Resource temporarily unavailable: core_output_filter:
writing data to the network

and after a REPORT failure error, this:

[error] [client 192.168.1.1] Provider encountered an error while
streaming a REPORT response. [500, #0]
[error] [client 192.168.1.1] A failure occurred while driving the
update report editor [500, #190004]

One other point that might be germane is that I saved the dumpfile to
an SMB share on a Win2k box before wiping my OS X box and installing
Tiger. I've done this before, and not had a problem with it, but
there you go..

With all that out of the way, does anyone have any bright ideas as to
what I might be doing wrong, or how this can be fixed? Many thanks in
advance, and my apologies for the long-windedness.. :)

Cheers,
Bryan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 22 21:05:19 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.