Errors when switching from server to local computer

Question

I tried the following rsync command from the server and received the following error message:

rsync -e ssh -avz [e-mail] :/home/name/. . receiving file list ... done Desktop/Python_Nick/Python-2.4.1/ Desktop/Python_Nick/Python-2.4.1/Python/ Write failed: Broken pipe rsync: writefd_unbuffered failed to write 4092 bytes [generator]: Broken pipe (32) rsync error: unexplained error (code 255) at /SourceCache/rsync/rsync-42/rsync/io.c(1121) [generator=2.6.9] rsync error: received SIGUSR1 (code 19) at /SourceCache/rsync/rsync-42/rsync/main.c(1197) [receiver=2.6.9] 

Sometimes this results in the following error:

 Read from socket failed: Operation timed out rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: unexplained error (code 255) at /SourceCache/rsync/rsync-42/rsync/io.c(452) [receiver=2.6.9] 

Then sometimes the following error occurs:

 Write failed: Broken pipe rsync: connection unexpectedly closed (314764 bytes received so far) [receiver]rsync: writefd_unbuffered failed to write 4092 bytes [generator]: Broken pipe (32) rsync error: unexplained error (code 255) at /SourceCache/rsync/rsync-42/rsync/io.c(1121) [generator=2.6.9] rsync error: error in rsync protocol data stream (code 12) at /SourceCache/rsync/rsync-42/rsync/io.c(452) [receiver=2.6.9] 

I even tried to use FETCH (MAC application).
Any suggestions? LINUX is running on the server, and my local computer is MAC

Answer 1

I had a similar problem and my solution was to update rsync on my Mac.

As can be seen from point 3 in the rsync "current problems and debugging" page , "the connection is unexpectedly closed"

the error tells you that the local rsync was trying to talk to remote rsync, but the connection to that rsync now disappeared. The thing is you must understand why, and this may include some work investigations.

One of the first things suggested on this page is the rsync update. Turns out Apple didn't provide us with the latest rsync on their machines. So I upgraded the rsync version on my Mac through Macports to 3.1.1. After that, I had no problems with synchronization.

This is not a general solution, of course, but again, there seems to be no general solution for this vague error message: if this did not work, I had to try to debug it. For details on how, see the above rsync problems page.