Displaying 20 results from an estimated 1000 matches similar to: "[Bug 2208] New: 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"
2006 Feb 06
4
DO NOT REPLY [Bug 3488] New: writefd_unbuffered failed to write 4096 bytes: phase "unknown" [generator]: Broken pipe (32)
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
2004 Jun 24
0
rsync: writefd_unbuffered failed to write 32768 bytes: phase "unknown": Broken pipe
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
2008 Mar 28
4
rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe
Hi,
i installed rsync 3.0 on a Sun Solaris 10 Sparc Server and tried to
Backup the Server via BackupPC
the complete rsync command from the backup server is this:
/usr/bin/ssh -q -x -l root IP /usr/bin/rsync --numeric-ids --perms
--owner --group -D --links --hard-links --times --block-size=2048
--recursive --checksum-seed=32761 --log-file=/var/log/rsync.log
--ignore-times . /
in the log on
2005 Sep 15
1
writefd_unbuffered failed to write 32768 bytes: phase "unknown"
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:
2004 Oct 21
0
[Bug 1959] New: writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
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:
2005 Apr 21
1
[Bug 1959] writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
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
2004 Dec 02
1
[Bug 1959] writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
https://bugzilla.samba.org/show_bug.cgi?id=1959
------- Additional Comments From maarten@xolphin.nl 2004-12-01 17:59 -------
Created an attachment (id=817)
--> (https://bugzilla.samba.org/attachment.cgi?id=817&action=view)
Debug information on 'other' side
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because:
2006 Feb 24
0
DO NOT REPLY [Bug 1959] writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
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
2005 Aug 24
1
[Bug 1959] writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
https://bugzilla.samba.org/show_bug.cgi?id=1959
------- Additional Comments From wejn@box.cz 2005-08-24 05:19 -------
Strange, got this error with 2.5.7 when the destination "module" was read-only.
2.6.6 prints user-friendly info that the module is not writeable.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because:
2008 May 13
0
DO NOT REPLY [Bug 1959] writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
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
2005 Feb 27
1
[Bug 1959] writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
https://bugzilla.samba.org/show_bug.cgi?id=1959
wayned@samba.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- Additional Comments From wayned@samba.org 2005-02-27 13:54 -------
To diagnose this bug further, I need a system-call
2007 Feb 25
1
DO NOT REPLY [Bug 1959] writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
https://bugzilla.samba.org/show_bug.cgi?id=1959
------- Comment #15 from george@imagine-com.com 2007-02-25 04:41 MST -------
Created an attachment (id=2309)
--> (https://bugzilla.samba.org/attachment.cgi?id=2309&action=view)
log error file
rsync command and error massage.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail
2006 Jul 30
3
DO NOT REPLY [Bug 3979] New: writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
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:
2008 Aug 16
5
DO NOT REPLY [Bug 5695] New: rsync local timeout
https://bugzilla.samba.org/show_bug.cgi?id=5695
Summary: rsync local timeout
Product: rsync
Version: 3.0.3
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned@samba.org
ReportedBy: gabriele.tozzi@gmail.com
QAContact:
2004 Oct 21
5
[Bug 1959] writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe
https://bugzilla.samba.org/show_bug.cgi?id=1959
wayned@samba.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|major |normal
Status|NEW |ASSIGNED
------- Additional Comments From wayned@samba.org 2004-10-21 15:19
2007 Oct 04
2
rsync stops/hangs (from windows to debian)
We've been using rsync to send updates to our webservers from a central location for years. All the webservers used to be Windows 2000 Server running rsync 2.6.3. Recently I've been trying to replace them with Debian servers with rsync 2.6.9. The central file server is a Windows 2000 Server using the cwRsync binary. It was also 2.6.3 until I upgraded it to use 2.6.9 also.
The initial
2008 Jul 27
3
imap processes eating IO
[Ignore the previous e-mail, I somehow sent it when I was trying to
paste from clipboard]
I recently migrated my dovecot/postfix setup to a new machine. After
doing so, I have encountered a problem where imap processes get stuck in
a loop eating loads of IO on the machine. Looking at the trace (snippet
below), it looks like they are sitting and reading the inbox and other
folders of
2003 Jan 06
0
smbd using alot of cpu
I have an smbd process that is using alot of cpu on HP-UX 11.11 using
Samba 2.2.3a. It looks like the application on the client side is trying
to open and close a ton of files, many of which do not exist. When I do
a trace on the smbd process, I see repeated calls to lstat64 to what
looks like all of the device files on my unix server. Here is a little
bit of the trace. It goes through all of the
2007 Oct 08
2
rsync error: protocol incompatibility (code 2) at main.c(1385)
Hello,
i'm trying to backup one of my hosts with a two rsync-scripts, which are
mainly just calling on the client side
/usr/bin/rsync --server --sender -vlogDtprz --delete-excluded
--numeric-ids --exclude-from=/etc/sm-backup/rsync.exclude /
and on the server side
rsync -avz --numeric-ids -e "ssh -i $key" --delete --delete-excluded
rsync@$client:/ $DATA_PATH/$client/daily.0
2002 Jun 18
1
remote rsync process dies, local hangs
I've got an rsync job which is consistently failing, but I've been
unable to diagnose the problem. FAQ/Google/docs/etc. checked and
no luck.
Basically, it looks like the rsync process invoked on the far end
is exiting, and then the local process waits until the timeout and
exits.
Both systems are Sun boxes, Ultra 10 or better with 256+ MB of memory.
Rsync version is 2.5.0 on the local