Den ons 25 mars 2026 kl 13:03 skrev Bo Berglund <[email protected]>:

> On Wed, 25 Mar 2026 12:01:57 +0100, Daniel Sahlberg
> <[email protected]> wrote:
>
> >What are the exact error messages you get?
>
> So I connected to the Windows server via VPN and RDP and in a cmd window I
> started the syncing bat file which showed that all of the other
> repositories (11
> of them) completed within seconds except for this problem one.
>
> The log file for that repo contains a few lines concerning the failed sync:
>
> [2026-03-25_06:36:48] Starting sync for hw
> svnsync sync --sync-username syncuser https://svn.xxxxxxxxxx.com/svn/hw
> https://yyyyyyyyy/svn/hw
> Transmitting file data .. (long time to print 585 dots) ..svnsync: E120106:
> ra_serf: The server sent a truncated HTTP response body.
> [2026-03-25_06:40:15] Sync completed for hw
>
> So there seems to maybe be a timeout and the server side cannot receive
> the data
> completely?
>

Looks like a timeout, yes. It is probably not because of the .git folder
itself but rather because of the size of the revision.


>
> Is it possible to create a "dump" file on the server containing the data
> for the
> last missing revisions and which I can transfer to the Ubuntu sync server
> and
> import there without the overhead of the Internet connection?
> It looks like a timeout to me.
>

If I remember correctly the last merged revision is stored in a revision
property on r0 in the target repository. I keep a local mirror of the SVN
Book on my own server and there seems to be a few revprops here:

[[[
daniel@srv:/data/svn/svnbook$ svn proplist file:///data/svn/svnbook -v
--revprop -r0
Unversioned properties on revision 0:
  svn:date
    2002-07-07T05:08:15.628904Z
  svn:log
    I'll bet I can enter a log message for revision 0, using tweak-log.cgi.

  svn:sync-from-url
    https://svn.code.sf.net/p/svnbook/source/trunk
  svn:sync-from-uuid
    b70f5e92-ccc6-4167-9ab2-d027528d294b
  svn:sync-last-merged-rev
    6069
daniel@srv:/data/svn/svnbook$
]]]

I suppose you could just `svnadmin dump` the failing revision and then
`svnadmin load` it to the target repository and carefully `svn propset`
svn:sync-last-merged-rev to an appropriate value. Make sure you read
through and understand everything in the SVN book related to svnsync before
attempting this, test it on a testrepository and make a proper backup
before you try it for real.

Hope it works out for you!

/Daniel

[3]
https://svnbook.red-bean.com/en/1.7/svn-book.html#svn.reposadmin.maint.replication



>
>
> --
> Bo Berglund
> Developer in Sweden
>
>
Of

Reply via email to