On Wed, 2009-12-02, Bitts, Daniel wrote:
> Julian,
>
> Nice script.
>
> I found replication file: to file: worked fine,
> https: to https: same server worked fine
> https: to https: over WAN fails with:
>
> svnsync: REPORT of 'https://master.vb.inside/mastersvn': Could not
> read response body: Secure connection truncated
> (https://master.vb.inside)
Ah, so now you show us the error message :-)
> The slave was https://slave.suffolk.inside/slavesvn, and svnsync was
> executed on the master server.
>
> It's looking more like an Apache issue than an SVN issue, but still is
> puzzling because users are regularly committing large files into the
> master over the WAN link from the slave site.
Yes. Perhaps you should be looking for timeouts or data transfer limits
in the Apache config. (I know very little about Apache config.)
Is your "svnsync" process using the Neon or the Serf library to make its
HTTP connections, do you know? This might make a difference. We can find
out from the output of "svnsync --version" plus any "http-library"
option in the "~/.subversion/config" file of the home directory of the
user account under which "svnsync" runs.
Can you try using the other one (Neon or Serf), if "svnsync --version"
indicates it supports both?
- Julian
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2426700
Please start new threads on the <dev_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <dev-subscribe_at_subversion.apache.org>.
Received on 2009-12-03 14:33:19 CET