On 17/04/18 17:47, just subscribed for rsync-qa from bugzilla via rsync
wrote:
> https://bugzilla.samba.org/show_bug.cgi?id=5478
>
> --- Comment #34 from David Nelson ---
> FYI. Although when rsync ver. 3.0.9 is called in Ubuntu 12.04LTS to "push"
> files to the server, e.g.,
>
> rsync / server:
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #34 from David Nelson ---
FYI. Although when rsync ver. 3.0.9 is called in Ubuntu 12.04LTS to "push"
files to the server, e.g.,
rsync / server::Backups/
it fails with the error:
rsync error: error in rsync protocol data stream (code
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #33 from michaeljoya 2013-07-10 19:26:56
UTC ---
I got this error while creating a backup copy between two drives on the same
machine. It seems that most people on this list are wrongly attributing the
problem to differing rsync version
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #32 from Scott Wood 2013-05-23 03:50:20
UTC ---
I tried the --no-ckecksum or --blocking-io, both to no avail. I now have an
admin at the other end of the connection onboard for troubleshooting. If/when
we find the cause, I'll update t
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #31 from Scott Wood 2013-05-23 02:21:10
UTC ---
(In reply to comment #30)
> Did you try with one of these options : --no-checksum --no-compress
> --blocking-io ?
>
> Just a check since you have a 4G limit : I suppose you're not rsync-i
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #30 from Loïc Gomez 2013-05-22 07:02:09
UTC ---
Did you try with one of these options : --no-checksum --no-compress
--blocking-io ?
Just a check since you have a 4G limit : I suppose you're not rsync-ing to a
FAT32 filesystem ?
--
Co
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #29 from Scott Wood 2013-05-22 06:05:43
UTC ---
As a follow up to my second question, we added the firewall rules to allow
SYN,RST,ACK,FIN and ACK traffic form the server in question and it did not
solve the problem.
--
Configure bugm
ver
resulting in the following on the client:
Read from remote host theserver: Connection reset by peer
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken
pipe (32)
rsync: connection unexpectedly closed (28 bytes received so far) [sender]
rsync error: unexplained error (code 255)
https://bugzilla.samba.org/show_bug.cgi?id=5478
Sebastian changed:
What|Removed |Added
CC||s...@open-t.co.uk
--- Comment #27 from Sebastia
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #26 from Justin Patrin 2012-11-01
19:40:37 UTC ---
Correction: this problem *mostly* went away by turning off compression. I still
get this error, 100% reproducable right around the same point in certain large
file transfers. Adding --i
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #25 from Justin Patrin 2012-10-31
01:32:36 UTC ---
FWIW, this problem went away for me by just removing -z and adding
--no-compress.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving th
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #24 from Loïc Gomez 2012-10-23 11:24:52
UTC ---
I also had the same issue and it was(In reply to comment #11)
> I need to change my answer here. The files that cause it to choke are larger
> than most, so I would have to say that as a g
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #23 from Chip Schweiss 2012-10-22 16:23:10 UTC
---
I came here when I was experiencing this problem. I later found the problem.
If you are running on Redhat/Centos 5/6, there is a long standing bug in the
kernel distributed by Redhat
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #22 from Gaute Hope 2012-10-01 10:20:42 UTC
---
(In reply to comment #21)
> After all the discussion of network matters that I saw from your thread I
> thought (as I'm working in my LAN) I could turn of openSUSE's firewall for a
> try.
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #21 from Martin Scherbaum 2012-07-13 19:14:03
UTC ---
Hello together,
although the last posting has been already done a while ago, out of respect for
the meticulous work of Eric (and Tim and Wayne) - which was a pleasure to read
for me
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #20 from Tim Taiwanese Liim
2011-10-07 21:57:54 UTC ---
I agree with Wayne and Eric that Eric's issue is outside of rsync,
somewhere in the transport.
Eric,
Have you tried to check the TCP buffers of the ssh process on both
ends? For
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #19 from Eric Shubert 2011-10-06 15:28:32 UTC ---
(In reply to comment #14)
> So, looking at your trace, it looks like the sender is waiting to write more
> data (its select lists the write and error FDs). The receiving side's 2 pids
>
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #18 from Eric Shubert 2011-09-29 20:39:54 UTC ---
(In reply to comment #17)
>
> I'm presently thinking that the problem is not with rsync itself, but with
> some
> aspect of the network connection. I'm seeing no corresponding ethernet
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #17 from Eric Shubert 2011-09-29 17:16:38 UTC ---
(In reply to comment #16)
>
> So now I'm beginning to think that the problem is (indeed) outside of the
> rsync
> code. I've examined the 2 target hosts (one that worked and one that do
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #16 from Eric Shubert 2011-09-28 20:40:15 UTC ---
I've done some further testing and would like to report my findings.
I tried the rsync to a different target host on a different IP address via a
different ISP, and lo and behold, it wor
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #15 from Eric Shubert 2011-09-23 15:55:27 UTC ---
(In reply to comment #14)
> It's a bit unclear what pid corresponds to what function, especially with both
> sides having 2 pids in the trace output. What is the command-line used?
st
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #14 from Wayne Davison 2011-09-23 02:19:04 UTC
---
It's a bit unclear what pid corresponds to what function, especially with both
sides having 2 pids in the trace output. What is the command-line used?
So, looking at your trace, it lo
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #13 from Eric Shubert 2011-09-22 19:25:19 UTC ---
(In reply to comment #12)
> I'm presently attempting to capture a corresponding strace on the source side
> to see what's going on there.
Here are matching straces from the sending and r
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #12 from Eric Shubert 2011-09-22 18:35:06 UTC ---
(In reply to comment #11)
> When the process hangs, it always times out waiting for the
> first of the two smaller chunks (after 7 reads of 4092 bytes).
>
Correction. It times out on the
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #11 from Eric Shubert 2011-09-22 16:54:14 UTC ---
(In reply to comment #9)
> (In reply to comment #8)
> > By any chance do you consider these files "big" files? I am asking
> > because I saw similar timeout when sending big files (bug77
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #10 from Eric Shubert 2011-09-20 15:39:39 UTC ---
(In reply to comment #9)
>
> I'm going to put a problem/test file on the target machine's hdd and continue
> testing with a local2local transfer.
I'm holding off on the local test for t
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #9 from Eric Shubert 2011-09-20 14:42:37 UTC ---
(In reply to comment #8)
> By any chance do you consider these files "big" files? I am asking
> because I saw similar timeout when sending big files (bug7757,
> bug7195).
Not really. Mos
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #8 from Tim Taiwanese Liim 2011-09-20
02:12:09 UTC ---
Re: Comment #7
> The error happened most frequently with files ... containing
> attached pictures.
Eric,
By any chance do you consider these files "big" files? I am asking
because
https://bugzilla.samba.org/show_bug.cgi?id=5478
Eric Shubert changed:
What|Removed |Added
CC||e...@shubes.net
--- Comment #7 from Eric Shu
444 ftp.wwzzz.org::ftp . >>
rsynclog
rsync: read error: Connection reset by peer (54)rsync:
writefd_unbuffered failed to write 4092 bytes to socket [generator]:
Broken pipe (32)
rsync error: error in rsync protocol data stream (code 12) at io.c(1530)
[generator=3.0.7]
#1805:> rsync error: rece
--- Comment #6 from tim.l...@alcatel-lucent.com 2010-10-27 00:28 CST
---
These bugs seem to be related (having similar error messages:
connection unexpectedly closed, broken pipe, timeout).
bug7757
with big file, rsync times out out when it should not; the
sender is still
On Wed, 2010-03-10 at 11:58 +, Dave Howorth wrote:
> 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/
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 f
On Sun, 2009-12-13 at 07:21 +, tom raschel wrote:
> i have to tranfer large files each 5-100 GB (mo-fri) over dsl line.
> unfortunately dsl lines are often not very stable and i got a broken pipe
> error.
> (dsl lines are getting a new ip if they are broken or at least after a
Here is some news :
I found what was the problem, just an rsync compiled in 32bits on OES1
triyng to speak with an rsync compiled in 64bits on OES2 !
After replacing the 64bits by a 32bits binary it's working fine!
Thibaud.
--
Please use reply-all for most replies to avoid omitting the mail
On Mon, Dec 21, 2009 at 8:27 AM, Aubert Thibaud wrote:
> 2009/12/21 15:50:43 [22219] unknown message 36:1587200 [generator]
That's an error from the generator complaining about the data coming
over the local pipe from the receiver. If that data is messed up,
things have to be in pretty bad shape
On Mon 21 Dec 2009, Aubert Thibaud wrote:
>
> 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.
> rsync error: error in rsync protocol data stream (code 12) at io.c(600)
> [sender=3.0.6]
> _exit_cleanup(code=12, file=io.c, line=
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
with inplace after a broken pipe is working now.
> (thx again to wayne)
>
> but it is much more slow as if a "normal" rsync job.
>
> I have read that setting the --backup option could help. (have not tried
> it
> yet)
>
> But --backup option would halve the s
Hi,
retransfer of large fail with inplace after a broken pipe is working now.
(thx again to wayne)
but it is much more slow as if a "normal" rsync job.
I have read that setting the --backup option could help. (have not tried it
yet)
But --backup option would halve the space, wh
t; if dsl line is stable the transfer is successfull (which works
>> furtunately
>> most of the time)
>>
>> 4.)
>> i am searching for a way to reduce the time to retransfer the file or
>> in
>> other words to resume the filetransfer after a broken pi
On Sat, Dec 12, 2009 at 11:21 PM, tom raschel wrote:
> so i had a look at --inplace which I thougt could do the trick, but inplace
> is updating the timestamp and if the script start a retransfer after a
> broken pipe it fails because the --inplace file is newer than the original
>
i could see at dyndns)
>
> 3)
> if dsl line is stable the transfer is successfull (which works
> furtunately
> most of the time)
>
> 4.)
> i am searching for a way to reduce the time to retransfer the file or
> in
> other words to resume the filetransfer after a bro
le the transfer is successfull (which works furtunately
most of the time)
4.)
i am searching for a way to reduce the time to retransfer the file or in
other words to resume the filetransfer after a broken pipe
(e.g. if you download a 4.4 GB Centos Image it is comfortable to resume the
transfer o
tom raschel wrote:
> Hi,
>
> i have to tranfer large files each 5-100 GB (mo-fri) over dsl line.
> unfortunately dsl lines are often not very stable and i got a broken
> pipe error.
> (dsl lines are getting a new ip if they are broken or at least after a
> reconnect every 2
Hi,
i have to tranfer large files each 5-100 GB (mo-fri) over dsl line.
unfortunately dsl lines are often not very stable and i got a broken pipe error.
(dsl lines are getting a new ip if they are broken or at least after a
reconnect every 24 hours)
i had a script which detect the rsync error
: writefd_unbuffered failed to write 4092 bytes [sender]: Broken pipe (32)
ERROR: buffer overflow in receive_file_entry [receiver]
rsync error: error allocating core memory buffers (code 22) at util.c(121)
[receiver=2.6.9]
rsync: connection unexpectedly closed (4 bytes received so far) [sender]
rsync error: error
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #5 from [EMAIL PROTECTED] 2008-07-28 20:43 CST ---
Any more info on this? You could try the latest 3.1.0dev version and try using
the --msgs2stderr option to see if it reveals a remote error that was getting
lost when things
/Volumes/Pro-Backup/Users/ar
>
> and the error log ends like this:
> ---
> send_files mapped /Users/ar/Library/Application
> Support/Firefox/Profiles/p3xm9ow4.default/secmod.db of size 16384
> calling match_sums /Users/ar/Library/Application
> Support/Firefox/Profiles/p3xm
tion Support/Firefox/Profiles/p3xm9ow4.default/secmod.db
rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32)
...
recv_generator(ar/Library/Application
Support/Firefox/Profiles/p3xm9ow4.default/extensions/
[EMAIL PROTECTED]/chrome/content,14004)
recv_generator(ar/Library/Applica
I have been making changes to the rsync-3.0.2 code to try out one simple idea
that we have.
When i run this modified code, i am getting the following error after some
data is backed up.
rsync: writefd_unbuffered failed to write 4 bytes [generator]: Broken pipe
(32)
rsync error: error in rsync
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #4 from [EMAIL PROTECTED] 2008-05-21 09:55 CST ---
Interesting. The 30-second timeout is therefore the one turned on in the error
handling to try to get a message back from the receiving side. Usually the
receiving side van
https://bugzilla.samba.org/show_bug.cgi?id=5478
--- Comment #3 from [EMAIL PROTECTED] 2008-05-21 09:30 CST ---
My intuition says that the bug more lies in "io.c" (
http://git.samba.org/?p=rsync.git;a=blob;f=io.c;hb=73cb6738b33846130c21f2903b2200fa3f1903ab
):
#define SELECT_TIMEOUT 3
https://bugzilla.samba.org/show_bug.cgi?id=5478
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|INVALID
https://bugzilla.samba.org/show_bug.cgi?id=5478
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=5478
Summary: rsync: writefd_unbuffered failed to write 4092 bytes
[sender]: Broken pipe (32)
Product: rsync
Version: 3.0.3
Platform: Other
URL: https://bugzilla.samba.org
https://bugzilla.samba.org/show_bug.cgi?id=1959
--- Comment #17 from [EMAIL PROTECTED] 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
i now tested it on a fresh installes sun with Solaris 10 sparc without
installing any patches and rsync works.
If i install all patches the error message comes.
Any idea?
Mit freundlichen Grüßen
Sebastian Kösters
systems architect
Trade Haven GmbH
In der Steele 37, 40599 Düsseldorf
T +
On Mon, Mar 31, 2008 at 10:48:18AM +0200, Sebastian Kösters wrote:
> On the sun the command (in ps ef) went away after about 2 Minutes with
> the error message I sent you.
That makes it look like a connection failure then. Perhaps a firewall
is closing an idle connection? e.g. I once had a Links
[mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 28. März 2008 17:03
An: Sebastian Kösters
Cc: rsync@lists.samba.org
Betreff: Re: rsync: writefd_unbuffered failed to write 4 bytes [sender]:
Broken pipe
On Fri, Mar 28, 2008 at 04:41:26PM +0100, Sebastian Kösters wrote:
> 2008/03/28 16:35:46 [5
On Fri, Mar 28, 2008 at 04:41:26PM +0100, Sebastian Kösters wrote:
> 2008/03/28 16:35:46 [5573] rsync: writefd_unbuffered failed to write 4 bytes
> [sender]: Broken pipe (32)
This tells you that the connection unexpectedly closed, so you should
look to see why BackupPC went away.
.
=2048
--recursive --checksum-seed=32761 --log-file=/var/log/rsync.log
--ignore-times . /
in the log on the sun i see this:
2008/03/28 16:35:46 [5573] rsync: writefd_unbuffered failed to write 4
bytes [sender]: Broken pipe (32)
2008/03/28 16:35:46 [5573] rsync error: errors with program
ARE/
I get the same error you indicate in this thread. Did you figure out what
was causing this problem? If not, what useful info can I provide?
Thanks,
Jurvis
--
View this message in context:
http://www.nabble.com/broken-pipe-tp15573670p16045801.html
Sent from the Samba - rsync mailing li
Hi Matt,
I got some more verbosity on the broken pipe (see below.) We ran the
compiled rsync on three machines. The leopard one worked, the Tiger
PPC Mac worked but this one, the Tiger Intel Mac, generates this error
on the same folder. I compiled the rsync3.0pre9 on my Tiger PPC
;
> 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 rsync protocol data stream (code 12) at
> io.c(1500) [generator=3.0.0pre9]
rsync: writefd_unbuffered failed to write 82 bytes [generator]: Broken
pipe (32)
rsync error: error in rsync protocol data stream (code 12) at
io.c(1500) [generator=3.0.0pre9]
Any thoughts on why it is broken? Rob D
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo
https://bugzilla.samba.org/show_bug.cgi?id=1959
--- Comment #16 from [EMAIL PROTECTED] 2007-02-25 10:41 MST ---
George, the first error message "Received disconnect from 20.20.10.250: 2:
Corrupted MAC on input" (which was not printed by rsync) indicates pretty
clearly that corruption
https://bugzilla.samba.org/show_bug.cgi?id=1959
--- Comment #15 from [EMAIL PROTECTED] 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
On Tue, Jan 09, 2007 at 04:31:50PM +0530, Lakshminarayanan RadhaKrishnan wrote:
> There is no other message except the following in other side of the node.
>
> 2007/01/09 06:30:18 [734] rsyncd version 2.6.8 starting, listening on port 873
I'm talking about the other end of the transfer. You're
: Lakshminarayanan RadhaKrishnan
Cc: rsync@lists.samba.org
Subject: Re: rsync - 2.6.8 ( broken pipe )
On Mon, Jan 08, 2007 at 12:28:28PM +0530, Lakshminarayanan RadhaKrishnan
wrote:
> 2007/01/09 02:11:36 [1076] rsync: connection unexpectedly closed (342821
> bytes received so far) [receiver]
Wha
On Mon, Jan 08, 2007 at 12:28:28PM +0530, Lakshminarayanan RadhaKrishnan wrote:
> 2007/01/09 02:11:36 [1076] rsync: connection unexpectedly closed (342821
> bytes received so far) [receiver]
What does the rsync on the other side report when this happens?
..wayne..
--
To unsubscribe or change opt
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
https://bugzilla.samba.org/show_bug.cgi?id=3979
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3979
[EMAIL PROTECTED] changed:
What|Removed |Added
CC|[EMAIL PROTECTED] |
--- Comment #2 from [EMAIL PR
https://bugzilla.samba.org/show_bug.cgi?id=3979
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from [EM
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
version 29.
Error messages are:
"rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" [sender]:
Broken pipe (32)
rsync error: timeout in data send/receive (code 30) at io.c(181)
rsync: connection unexpectedly closed (241914 bytes received so far) [sender]
rsync error:
https://bugzilla.samba.org/show_bug.cgi?id=3488
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3488
--- Comment #3 from [EMAIL PROTECTED] 2006-02-06 15:09 MST ---
>I'm assuming by "hung" you mean more of a "hang up", as in problem-causing item
>where rsync died, rather than "hung" as in the process keeps running but stops
>doing anyth
https://bugzilla.samba.org/show_bug.cgi?id=3488
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #2 from [EM
https://bugzilla.samba.org/show_bug.cgi?id=3488
--- Comment #1 from [EMAIL PROTECTED] 2006-02-06 12:23 MST ---
Created an attachment (id=1722)
--> (https://bugzilla.samba.org/attachment.cgi?id=1722&action=view)
Truss output.
--
Configure bugmail: https://bugzilla.samba.org/userpre
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/Versio
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
https://bugzilla.samba.org/show_bug.cgi?id=1959
--- Additional Comments From [EMAIL PROTECTED] 2005-08-24 09:41 ---
(In reply to comment #12)
> 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 w
https://bugzilla.samba.org/show_bug.cgi?id=1959
--- Additional Comments From [EMAIL PROTECTED] 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:
uilding 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 works on all of our servers except this one.
>
> Is there any way t
"send_file_entry": Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(515)
This method works on all of our servers except this one.
Is there any way to resolve it?
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this ma
https://bugzilla.samba.org/show_bug.cgi?id=1959
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=1959
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Additional Comments
of work:
Read from remote host : Connection reset by peer
rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" [sender]:
Broken pipe (32)
rsync: connection unexpectedly closed (42088 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) a
https://bugzilla.samba.org/show_bug.cgi?id=1959
--- Additional Comments From [EMAIL PROTECTED] 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://bug
--On Friday, November 19, 2004 10:13:58 -0700 [EMAIL PROTECTED] wrote:
--- Additional Comments From [EMAIL PROTECTED] 2004-11-19 10:13
--- The cited strace shows that rsync is hanging because of all the
verbose messages coming from the receiver aren't getting read by the
sender. So, just
https://bugzilla.samba.org/show_bug.cgi?id=1959
--- Additional Comments From [EMAIL PROTECTED] 2004-11-19 10:13 ---
The cited strace shows that rsync is hanging because of all the verbose messages
coming from the receiver aren't getting read by the sender. So, just reduce the
verbosi
https://bugzilla.samba.org/show_bug.cgi?id=1959
--- Additional Comments From [EMAIL PROTECTED] 2004-11-19 05:50 ---
I am experiencing similar problems on debian woody (linux 2.4.26 and after
upgrading to linux 2.4.28). This problem started suddenly after over 100 days of
clean daily o
https://bugzilla.samba.org/show_bug.cgi?id=1959
--- Additional Comments From [EMAIL PROTECTED] 2004-11-19 05:47 ---
Created an attachment (id=797)
--> (https://bugzilla.samba.org/attachment.cgi?id=797&action=view)
Command line session of rsync hanging
--
Configure bugmail: https:/
https://bugzilla.samba.org/show_bug.cgi?id=1959
--- Additional Comments From [EMAIL PROTECTED] 2004-11-19 05:48 ---
Created an attachment (id=798)
--> (https://bugzilla.samba.org/attachment.cgi?id=798&action=view)
rsync hanging strace output
--
Configure bugmail: https://bugzilla.
https://bugzilla.samba.org/show_bug.cgi?id=1959
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|NEW
--- Additional Comments From
https://bugzilla.samba.org/show_bug.cgi?id=1959
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|major |normal
Status|NEW
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
On Sat, Oct 09, 2004 at 11:39:45AM -0700, Saunders, Shawn wrote:
> 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(842)
A broken-pipe error means that the other end of
1 - 100 of 121 matches
Mail list logo
