-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm trying to sync a mandrakelinux tree (~120GB) but it bombs out after a while with this error: rsync: connection unexpectedly closed (289336107 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) rsync: writefd_unbuffered failed to write 4092 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(666) The exact command used is: rsync -av --stats --progress --partial --delete-after --bwlimit=2000 rsync://mirrors.usc.edu/mandrakelinux/ /export/ftp/mandrakelinux $RSYNC_PROXY is set to be a squid proxy, which is very reliable for other forms of transfer (ftp/http) It's synching to a 1.6TB raid array, which still has over 1TB free, so its not a space issue. Anyone know a) what causes this error and b) how I can get round it? Cheers, Mark. - -- Mark Watts 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) iD8DBQFBGKM0Bn4EFUVUIO0RAqsCAJ4z1Gf2P0ZBGJXsVhHamXBHRMxrRACgtV56 NbrLgC5pkaKhdX202v41JU8=l61M -----END PGP SIGNATURE-----
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: http://rsync.samba.org/issues.html ..wayne..