similar to: rsync error code 12 at phase "unknown"

https://bugzilla.samba.org/show_bug.cgi?id=1959 ------- Comment #14 from aim1@westnet.com.au 2006-02-24 08:39 MST ------- I also had the same problem ocurring randomly on large file transfers between an IDE disk and a disk attached via USB2.0 using RedHat FC4 and rsync version 2.6.4 protocol version 29. Error messages are: "rsync: writefd_unbuffered failed to write 4 bytes: phase

https://bugzilla.samba.org/show_bug.cgi?id=2208 Summary: rsync failed at random file with same error rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" [sender]: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at

Hi, on HPUX 11i with ANSI/C compiler with largefile option. below rsync is on local file system. # rsync -av /prod1/* /prod1n/ building file list ... done DW/ DW/DATA/ DW/DATA/DWCOF02.DAT rsync: writefd_unbuffered failed to write 32768 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(836) rsync: writefd_unbuffered failed to write 69

Hi, I receive this error when rsyncing. I suspect this is because of network problems. But the 'Invalid argument' and 'phase unknown' makes it very unobvious. ... packages/scribus/scribus-1.2.3-0.rf.src.rpm Read from remote host rsync.sw.be: Invalid argument rsync: writefd_unbuffered failed to write 32768 bytes: phase "unknown" [sender]: Broken pipe (32) rsync:

[I'm not subscribed, please CC me on replies] Some time after 2.6.0 the --bwlimit code was enhanced, but the code now doesn't work anymore when you set the bandwidth limit for the daemon and generates error log entries like: 2005/01/13 08:17:03 [29636] rsync: writefd_unbuffered failed to write 12 \ bytes: phase "unknown" [receiver]: Success (0) 2005/01/13 08:17:03 [29636]

https://bugzilla.samba.org/show_bug.cgi?id=1959 ------- Comment #17 from kde@ost.com.sg 2008-05-13 05:25 CST ------- I experienced the same error when rsync to an external usb ide drive. When it happened, the system hanged. Following Andrew Morris with --bwlimit=8192 --timeout=600 setting got rid of system hanging. However, it causes rsync to abort after 600 seconds. The problem is due to

I'm using rsync 3.0.9-1 in Cygwin to copy several directories to 32GB micro SD cards in both WinXP and Win7. I randomly get this error message; Please help me to debug it: rsync: writefd_unbuffered failed to write 127 bytes to socket [generator]: Broken pipe (32) I'd first posted this to the Cygwin mailing list with no response after almost two weeks (and sent a reminder after one week).

https://bugzilla.samba.org/show_bug.cgi?id=3488 Summary: writefd_unbuffered failed to write 4096 bytes: phase "unknown" [generator]: Broken pipe (32) Product: rsync Version: 2.6.6 Platform: Sparc OS/Version: Solaris Status: NEW Severity: major Priority: P3 Component: core

Hi, I've installed cygwin and rsync on a vista client and want backup it to a Linux server: On client side (vista) I use rsync 3.0.4 (protocol version 30) Capabilities: 64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, no IPv6, batchfiles, inplace, append, ACLs, no xattrs, iconv, symtimes On server side (linux) I have rsync 3.0.3

I received a bug report that starting with 2.6.3, rsync fails when started from inetd with the --bwlimit option (actually, I narrowed it down to that :-). Earlier rsync versions did work. What I see from the strace output is that the rsync --daemon process sets fd 0 to ON_NONBLOCK, then does a select() on fd 0 for write (which shows it's ready for writing), and then does a write of zero

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

I am running jungledisk and this is my script: #!/bin/sh ### Backs up office data to Jungledisk using rsync LOGFILE=/var/log/backup-jd.log ## Start in rc.local or here #/usr/local/bin/jungledisk mount /mnt/s3 echo "`date +"%F %R"`: Start backup-jd" >> $LOGFILE rsync -r --inplace --size-only --bwlimit=50 /home/shares/allusers/127 /mnt/s3 echo "`date +"%F

Hi everybody, I use RSYNC under windows (cygwin) on both server and client side for syncing 2 big directories over an VPN IPSEC links.(1 GB of data for around 30 000 files). The sync shows these kind of errors for some clients. Here is the command that I use in a batch file to syncing the folders start /w /D "e:/admin/rsyncd/" rsync.exe -az --delete --exclude="SAVE"

https://bugzilla.samba.org/show_bug.cgi?id=1959 Summary: writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe Product: rsync Version: 2.6.2 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo:

https://bugzilla.samba.org/show_bug.cgi?id=3979 Summary: writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe Product: rsync Version: 2.6.8 Platform: Other OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo:

https://bugzilla.samba.org/show_bug.cgi?id=1959 ------- Additional Comments From admin@exovian.com 2005-04-21 08:46 ------- root@xxxx [~]# rsync -avz -e ssh /home/ xxxx@xxxxx:xxxx building file list ... rsync: writefd_unbuffered failed to write 4092 bytes: phase "send_file_entry": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) This method

-----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:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Using the following settings: $ export RSYNC_PROXY=www-proxy:3125 $ rsync -av --stats --progress --partial --delete-after --bwlimit=160 rsync://carroll.cac.psu.edu/mandrakelinux/ /export/ftp/mandrakelinux I'll almost certainly get this error at some point during the transfer: rsync: connection unexpectedly closed (320497666 bytes received so

Sirs; I have read your web site page current issues and debugging and I am interested in how to debug a rsync issue which ends with the following message: io timeout after 60 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(181) I have compiled rsync on a hpux 11.11 server and I am using rsync-2.6.4. The remote machine is running rsync as a deamon in inetd.

Dear all, This is just a placeholder really - I've spent quite a lot of time trying to track down the cause of a problem I'm seeing here, and have eventually got an answer. Thought it might be useful to have the solution googleable. Obviously, if someone has better ideas, I'd welcome comments. Similarly, if anyone wants detailed logs, tcpdump or strace output, I'd be happy to