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

Re: Subversion 1.9.7 server on Windows, advice on setting up svnsync?

From: Bo Berglund <bo.berglund_at_gmail.com>
Date: Wed, 28 Mar 2018 12:41:49 -0500

On Wed, 28 Mar 2018 09:00:05 +0200, Johan Corveleyn
<jcorvel_at_gmail.com> wrote:

>> Transmitting file data ....... 8 long lines of dots
>> ......................svnsync: E120106: ra_serf: The server sent a
>> truncated HTTP response body.
>I'd start with going through the apache logs on both servers to look
>for more information about this error (since "The server sent a
>truncated HTTP response body." indicates to me that an error should be
>logged on that server).

Unfortunately it is not possible for me at the moment since I am

>It's also possible that some other network component has truncated
>things ... proxies, security content filters, ...

I tested the synchronize function on two repositories and they both
triggered this error, but on different revs of course.

So I used svnlook on the master server to find out what was actually
being transferred for these revs. Turns out to be in both cases an
initial import of a big "library" file set.

In the case of the cmp repo it involved 9848 files some of which are
very big. In the other case it was also an import affecting 3669 files
of a cutdown version of the library..

The first import was done by cvs2svn when I converted the CVS repo to
SVN, but the other was an import I did when I created a repo for a
consultant who should have access only to a subset of our versioned
files. So I exported these and then imported the export into the new

So I guess that the sheer size of the imports it tries to sync is what
kills it, especially when doing it over the Internet....

Is there a possibility to dump the source repos, then use the
dumpfiles to set up the mirrors and finally tell svnsync to start
syncing from the revision that is now the last in the mirror?

It would certainly make it more controlled since I could ftp the dump
files from the source to the destination and then do the svn operation
locally with no network issues like latencies and such.

I have read that one must start with the target repo at rev 0, but
then I have also read some notes that later versions of svn have
improved on this....

We use 1.9.3 on the mirror server and 1.9.7 on the master server.

Grateful for any advice here!

Bo Berglund
Developer in Sweden
Received on 2018-03-28 19:42:05 CEST

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.