svnsync sync is failing

["Reddy, Raghuram IN BLR SISL" <Ra...@siemens.com>]

Hi,

     I going to sync with two repositories (Master and Slave), while svnsync sync I am getting message
..........................................................................................................................
svnsync: REPORT of 'https://chnsvm009.in002.siemens.net:8443/svn/SIPAC': Could not read chunk delimiter: Secure connection truncated (https://chnsvm009.in002.siemens.net:8443)


Regards,
Raghu.
Ext:5804

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1107758

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].

Re: svnsync sync is failing

[Jonathan Coles <jc...@rogers.com>]

svnsync failures don't get much response around here. Internet searches 
show that the problem has existed for several years. Possibly most users 
don't trigger this bug. It occurs when the revision data exceeds 
20Mbytes or so. The commits that software developers make are unlikely 
to be that large.

Perhaps I can offer a workaround.

In my case, the error message says "invalid chunk delimiter", but 
otherwise sounds similar. For the revision that failed (the last one 
reported as committed, plus one), I execute svnadmin dump on the Master 
machine to produce a dump file, like this:

svnadmin dump <repos-path> -r <failed_rev_number> --incremental --deltas 
 > dumpfile

I copy dumpfile to the Slave machine and use svnadmin load to commit it 
to the mirror repository, like this:

svnadmin load <repos-path> --ignore-uuid < dumpfile

Lastly, I edit the Slave repository's Rev 0 properties in 
<repo>/db/revprops/0 ("<-- " are my comments):

K 17
svn:sync-currently-copying
V 4    <--match the number of chars on next line
1075 <-- set to next rev, if problem, set to last
...
K 24
svn:sync-last-merged-rev
V 4    <-- match the number of chars on next line>
1074 <-- set to last rev

The subsequent svnsync sync operation will work normally, unless it 
encounters another large revision that triggers another chunk delimiter 
error.

I hope this might be useful.

Reddy, Raghuram IN BLR SISL wrote:
>
> Hi,
>
>  
>
>      I going to sync with two repositories (Master and Slave), while 
> *svnsync sync* I am getting message
>
> ..........................................................................................................................
>
> svnsync: REPORT of 
> 'https://chnsvm009.in002.siemens.net:8443/svn/SIPAC': Could not read 
> chunk delimiter: Secure connection truncated 
> (https://chnsvm009.in002.siemens.net:8443)
>
>  
>
>  
>
> Regards,
>
> Raghu.
>
> Ext:5804
>
>  
>
>  
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1125951

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].