On 31.10.2013 22:57, David Goldsmith wrote:
> I'm pretty sure I am now...however, while I was away, I got:
> Committed revision 821.
> Copied properties for revision 821.
> svnsync: E175002: MKACTIVITY request on
> fe43a60c2c2' failed: 500 Internal Server Error
> svnsync: E175002: Additional errors:
> svnsync: E175002: Error running context
> svnsync: E175002: RA layer request failed
> If I just run the command again, is it smart enough to resume where it
> left off? Is there an (undocumented) command swich I can use to
> resume where it left off? Is this even the kind of error I might hope
> to resume where it left off? Thanks!
Yes, svnsync should continue from the last revision recorded in the
revprops on revision 0 on the target. From your log, that would appear
to be revision 821; but I do suggest you verify that it is, and that
it's properly recorded in the r0 revprops:
svn info <mirror-url> | grep ^Revision:
svn propget --revprop svn:sync-last-merged-rev -r0 <mirror-url>
svn propget --revprop svn:sync-currently-copying -r0 <mirror-url>
svn propget --revprop svn:sync-lock -r0 <mirror-url>
Make sure that the revision reported by "svn info" and the one in the
svn:sync-last-merged-rev property are the same. Depending on the state
in which the command failed, you may have to clean up the
svn:sync-currently-copying and svn:sync-lock properties.
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
Received on 2013-11-01 00:20:15 CET