I am running rsync 2.6.9 on SuSe Linux Enterprise Server 10. I got a 53.7 GB directory in one of my servers that I need to rsync over a gigabit link. But rsync runs for about 2-3 hours and fails with the following error - 2006/11/19 17:51:57 [9229] rsync: writefd_unbuffered failed to write 4 bytes [generator]: Connection reset by peer (104) 2006/11/19 17:51:57 [9229] rsync error: error in rsync protocol data stream (code 12) at io.c(1122) [generator=2.6.9] Here's my /etc/rsyncd.conf [MAIL] path = /backup/MAIL/ comment = MAIL read only = no use chroot = no timeout = 3600 transfer logging = yes log file = /var/log/rsync/mail.log Here's my command in the client-end -av --timeout=3600 --bwlimit=1000 --exclude-from=$exc --delete -b --backup-dir=$dest --volume=$vol: $source I tried changing the bandwidth limit to 200, 300 but that doesn't help. Thanks for any kind of help.
On Mon, Nov 20, 2006 at 12:47:03PM +1100, Tanvir Ahmed wrote:> 2006/11/19 17:51:57 [9229] rsync: writefd_unbuffered failed to write 4 > bytes [generator]: Connection reset by peer (104)As noted on the issue and debugging web page, this just tells us that the connection was closed. Look in the rsync daemon log file (since you appear to be using a daemon) to see if the other side of the connection has a reason for the closure. If it also has some kind of a socket- failure error, then the socket closed outside of rsync control. See the issue and debugging web page for other suggestions. ..wayne..
Apparently Analagous Threads
- Partial files cause: error in rsync protocol data stream (code 12) at io.c(584)
- IO error / connection unexpectedly closed
- writefd_unbuffered failed - Broken pipe on local rsync
- writefd_unbuffered failed to write
- writefd_unbuffered failed (when writing to micro SD cards)