rsync erroring out when syncing a large tree
m.watts at eris.qinetiq.com
Wed Aug 11 07:55:58 GMT 2004
-----BEGIN PGP SIGNED MESSAGE-----
> On Tue, Aug 10, 2004 at 11:28:04AM +0100, Mark Watts wrote:
> > rsync: connection unexpectedly closed (289336107 bytes read so far)
> > rsync error: error in rsync protocol data stream (code 12) at io.c(189)
> This error just means that the other side went away for some reason.
> What you need to figure out is why. The version of rsync in CVS (and in
> the "nightly" tar files) tries to grab a dying error from the other
> side, if possible, but if it crashed there is no such error to return.
> So, I'd recommend trying the CVS version of rsync to see if that gives
> you the actual error of what failed. Alternately (or additionally),
> follow the directions on the issues page to get a core dump and/or a
> system-call trace from the remote side to get extra information on what
> has gone wrong:
Unfortunatly the server(s) in question are in a different country from me and
I don't run them...
But, if I run the sync in a while (true) loop, it reconnects immediatley.
I'll try the cvs version of rsync though and see if I can get a better error.
Senior Systems Engineer
QinetiQ Trusted Information Management
Trusted Solutions and Services group
GPG Public Key ID: 455420ED
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the rsync