similar to: Broken pipe error in local copy mode

Displaying 20 results from an estimated 20000 matches similar to: "Broken pipe error in local copy mode"

2010 Mar 10
1
writefd_unbuffered failed - Broken pipe on local rsync
I'm seeing an error that says there is a broken pipe, but the rsync command is local to one machine: /usr/bin/rsync -rltH --stats -D --delete --numeric-ids --whole-file /data/dir /backup/suse1/suse1-data-dir/ >/tmp/rsync-out 2>&1 The complete contents of the rsync-out file are: rsync: writefd_unbuffered failed to write 88 bytes [receiver]: Broken pipe (32) rsync error: error in
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
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:
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
2003 Jun 17
2
rsync error: error in rsync protocol data stream (Broken pipe)
I'm experiencing some unexpected behavior with rsync v2.5.6. After looking around it seems like several people have experienced similar problems in the past, but those appear to be old bugs that are solved now. Also doesn't appear to be any direct bugfixes made for this issue since 2.5.6. The strange thing is that things seem to work when I use ssh for transport. However now I need to
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:
2004 Oct 09
1
writefd_unbuffered failed to write - Broken pipe
I am using Rsync 2.6.3 , and have tried rsync 2.6.2 also. I am attempting to push about 990G from one machine to another. Whenever I do this, it processes about 1/3 the way through and I receive the following error during the transfer, and it stops. Could this be a problem with it running as a cron job? The command I am using is /usr/local/bin/rsync -acv --stats /data/ server::data Any
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
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
2007 Jan 08
2
rsync - 2.6.8 ( broken pipe )
Wayne, While testing rsync 2.6.8, I often receive broken pipe error, even though there is no network problem, between Active and Standby nodes. Please clarify. 2007/01/09 02:11:36 [1076] rsync: connection unexpectedly closed (342821 bytes received so far) [receiver] 2007/01/09 02:11:36 [1076] rsync: writefd_unbuffered failed to write 84 bytes [generator]: Broken pipe (32) 2007/01/09
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
2008 Feb 19
1
broken pipe
Hi All, I have a client and we are trying to create a backup for several folders on OSX 10.4.11 with rsync 3.0.0pre9. One folder copies fine but the other three generate this error and I am stumped. using: rsync -aHAX --fileflags --crtimes -v we get; sending incremental file list rsync: writefd_unbuffered failed to write 82 bytes [generator]: Broken pipe (32) rsync error: error in
2020 Aug 14
2
[PATCH nbdkit] New ondemand plugin.
This creates filesystems on demand. A client simply connects with a desired export name and a new export is created. The export is persistent (until deleted by the server admin), and clients may disconnect and reconnect. In some respects this is similar to the nbdkit-tmpdisk-plugin, or nbdkit-file-plugin with the dir= option. --- plugins/ondemand/nbdkit-ondemand-plugin.pod | 190 ++++++
2008 Jun 12
1
broken pipe when working on open files (?), MacOS X, 3.0.2/3.0.3pre2
Hello all, I have trouble to use rsync (tested with 3.0.2 and 3.0.3pre2) on MacOS X 10.3. Rsync always seems to stop when working on open files (?). Source is my laptop hard disk, destination a USB attached external drive. If I stop Firefox for instance all runs smoothly. This is how I built rsync: #!/bin/bash # VERSION=3.0.2 VERSION=3.0.3pre2 DIR="rsync-$VERSION"
2005 Sep 29
0
failed sync. Broken pipe
My rsync was working from a cron job for a long time. Suddenly, I started to get the error: rsync: writefd_unbuffered failed to write 85 bytes: phase "unknown" [receiver]: Broken pipe (32) rsync error: error in rsync protocol data stream (code 12) at /SourceCache/rsync/rsync-20/rsync/io.c(909) I am syncing to an external hard drive. It appears to be mounted properly.
2002 Jul 11
0
Quick analysis of 'Broken pipe' error at io.c(463)
This one has been biting me recently, and it seems to be completely deterministic: it utterly fails on most directories, but when it fails on one, it does so reproducibly. Also, I'm doing a simple copy from one directory on my machine to another - there is no remote server or network to fail. The drive is only 24% full. Here's my take on it: 1) The error is printed as occurring in
2009 Apr 23
0
rsync- buffer overflow/broken pipe with critical filename-lenght using cwrsync at server-side
hi everybody, i?ve a problem with rsync runnig. constellation: rsyncserver is cwrsync at win2k-machine (without cygwin-beta against long filename-problem), client is a linux-ubuntu box. log from the server: (i just change names with xxx, no special charakters) this error happens all the time again, /overflow: flags=0xba l1=240 l2=22
2000 Apr 26
2
Rapid transfers cause kernel panic
Our site has been experiencing problems with Samba causing kernel panics under heavy use. We are running Mandrake 7.0 and Samba 2.0.6. We are no longer using the distro included with Mandrake - we actually downloaded the 2.0.6 release and recompiled. Downloading from Samba shares causes no problems - and downloads are frequent and heavy - but uploading similar amounts of data leaves a catatonic
2009 Dec 21
2
rsync err. an other Broken pipe (32)
Hello, Since our server migration from OES1 (rsync-3.0.2-2.1) to OES2 (rsync-3.0.6-3.1), rsync backup do not work anymore. Here is some explanation : With a full verbose mode on the source server : rsync: writefd_unbuffered failed to write 631 bytes to socket [sender]: Broken pipe (32) rsync: connection unexpectedly closed (786 bytes received so far) [sender] _exit_cleanup(code=12,
2017 Aug 02
2
llvm-trunk errors with gcc-5.3.0 on SuSE Linux
Hi, I try to build llvm-trunk with Cmake (gcc-5.3.0 is necessary for CUDA) on my "SUSE Linux Enterprise Server 12.2 (x86_64)". svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm cd llvm/tools svn co http://llvm.org/svn/llvm-project/cfe/trunk clang svn co http://llvm.org/svn/llvm-project/polly/trunk polly cd clang/tools svn co