-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Everyone, I've been running into a protocol error when attempting to rsync files between to hosts over ssh. Here is the line I've been using with the verbosity cranked up: rsync -avvvv -e "ssh -l test" /localpath/to/sync xxx.xxx.xxx.xxx::module cmd=ssh -l test machine=xxx.xxx.xxx.xxx user= path=module cmd=ssh -l test xxx.xxx.xxx.xxx rsync --server --daemon . opening connection using ssh -l test xxx.xxx.xxx.xxx rsync --server - --daemon . test@xxx.xxx.xxx.xxx's password: rsync: connection unexpectedly closed (12 bytes read so far) _exit_cleanup(code=12, file=io.c, line=189): entered rsync error: error in rsync protocol data stream (code 12) at io.c(189) _exit_cleanup(code=12, file=io.c, line=189): about to call exit(12) Does anyone know what could be causing the data stream error? Thanks, - -Kevin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDZl747gLcxOJB4lcRAqR8AJ9HDSWIgestkpL8awQNWUq1AlN3WgCfW5Ac MB9kK8Hhs7fkH6LZfIn57EA=hyI8 -----END PGP SIGNATURE-----
On Mon, Oct 31, 2005 at 01:14:16PM -0500, Kevin Karwaski wrote:> rsync: connection unexpectedly closed (12 bytes read so far) > rsync error: error in rsync protocol data stream (code 12) at io.c(189)As the Issues and Debugging page mentions (see item #3 at this URL: http://rsync.samba.org/issues.html), this error just means that the other side went away. Why? They didn't tell us. Either the net connection closed due to ouside circumstances, or the remote rsync crashed/failed. The page gives you several things you can do to help you test the failure, including upgrading for better remote-error reporting (the latest is 2.6.6), enabling core dumps, and enabling remote system-call tracing. ..wayne..