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)
at 8:17 AM, Christopher de Vidal
wrote:
> 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 [
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 t
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.
ially a 1GBit interfacw)
which writes the data to a RAID1 configuration of 3.5" hard drives.
So, no real large files. But a not so fast NAS.
It hung up again and again with the above mentioned message "rsync:
writefd_unbuffered failed to write 4092 bytes [sender..." for different f
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
eer'
44755: 4552.251465543 0.000424099 write(2,"rsync: read error: Connection
reset by peer (54)",48) ERR#32 'Broken pipe'
44179: 5266.607818450 0.000371296 write(2,"rsync: writefd_unbuffered failed
to write 4092 bytes to socket ["...,92) = 48 (0x30)
responsive
bug2783
Random high loads during syncs (server side) / client stream errors
rsync: connection unexpectedly closed (2761332 bytes received so far)
[generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(365)
bug5478
rsync: writefd_unbuffered failed
Hi,
If you are able to rsync over ssh, this connection may be more robust than
plain rsync protocol. See
http://www.mail-archive.com/rsync@lists.samba.org/msg26280.html
Best regards,
Vitorio
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change
error: received SIGINT, SIGTERM, or SIGHUP (code 20)
> at rsync.c(562) [generator=3.0.7]
Something on the local machine sent rsync a signal. Try to figure out
what.
> Subsequent runs =>
>
> [2]
> rsync: read error: Connection reset by peer (54)rsync: writefd_unbuffered
> f
d 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]
rsync error: received SIGUSR1 (code 19) at main.c(1288) [receiver=3.0.7]
fr
>/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 rsync protocol data stream (code 12) at io.c(1122)
> [receiver=2.6.9]
>
>
ile are:
rsync: writefd_unbuffered failed to write 88 bytes [receiver]: Broken
pipe (32)
rsync error: error in rsync protocol data stream (code 12) at io.c(1122)
[receiver=2.6.9]
Q3 on http://samba.anu.edu.au/rsync/issues.html implies that the error
message necessarily involves a remote rsync. Does anybod
On Mon, Apr 27, 2009 at 12:19:10PM +0200, Stefan-Michael Guenther wrote:
> rsync: close failed on
> "/media/nas/daily.0/samba/Bereiche/Auslieferung/Software/NT2/2012/2012-69-RA-1L.0968
>
> (XY_I)/2006-11-16/XY_app.968/Logdb/.XYlog.mdb.REP380": Input/output error (5)
That's an OS error when rsyn
--numeric-ids --relative --delete-excluded
/samba /media/nas
The process crashes when it tries to copy *.mdb files (15-600MB):
rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32)
rsync: close failed on
"/media/nas/daily.0/samba/Bereiche/Auslieferung/Software/NT2/2012/20
Am Freitag 05 Dezember 2008 schrieb MATV:
> Hello,
> (Sorry, my english is no good)
>
> I've been searching for solutions but I don't find it.
>
> I'm using last version of cygwin (1.5.25-15) on Windows 2003 Server for
> transfer a Virtual Machine Backup (<2 GB .vmdk files; VCBMOUNTER) to a
> rem
OUTPUT over LAN
2008/12/05 14:02:25 [4012] opening tcp connection to 192.168.1.50 port 873
2008/12/05 14:02:25 [4012] building file list
2008/12/05 14:03:23 [4012] rsync: writefd_unbuffered failed to write 4 bytes
[sender]: Software caused connection abort (113)
2008/12/05 14:03:23 [4012] rsync:
e protocol version 28
> instead 30?
File::RsyncP only supports protocol 28.
> 2. What is meaning by "rsync: writefd_unbuffered failed to write 4 bytes
> [sender]: Connection reset by peer (104)"
That typically means the network connection dropped. See the third item
on http://r
3633-1717398822-1000/$RQUUPR3/U2 The
best of 1980-1990/(1998)The Best Of 1980 - 1990/05 - Sunday Bloody
Sunday.mpc
2008/10/17 10:30:28 [1432] rsync: writefd_unbuffered failed to write 4 bytes
[sender]: Connection reset by peer (104)
2008/10/17 10:30:28 [1432] rsync error: error in rsync proto
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
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
On Mon, May 05, 2008 at 08:12:43AM +1000, Ramkumar Santoshi wrote:
> once i compile rsync, the 'rsync' in the current dir should be ok for this?
Right.
> can you please explain each step from then?
I listed the steps in the prior email, but here they are with a little
more detail:
Enable core d
ok, perhaps we can go back to the start so i know where we are...
once i compile rsync, the 'rsync' in the current dir should be ok for this?
can you please explain each step from then?
much appreciated.
On Sat, May 3, 2008 at 1:00 AM, Wayne Davison <[EMAIL PROTECTED]> wrote:
> On Fri, May 02
On Fri, May 02, 2008 at 12:38:12PM +1000, Ramkumar Santoshi wrote:
> I'm pretty sure i grabbed the one from the build dir. Is there any way i
> can tell?
You can look at the size and/or see if "file rsync" output "stripped" or
"not stripped".
..wayne..
--
Please use reply-all for most replies t
3.0, it stops during a transfer.
>
> That's an incomplete version. The last release was 3.0.2.
>
> > 2008/04/28 20:48:46 [3149] rsync: writefd_unbuffered failed to write 4
> bytes [sender]: Broken pipe (32)
>
> That just tells you that the receiver went away. Run
On Tue, Apr 29, 2008 at 10:05:07AM +1000, Ramkumar Santoshi wrote:
> On Mac OS10.4, using rsync 3.0, it stops during a transfer.
That's an incomplete version. The last release was 3.0.2.
> 2008/04/28 20:48:46 [3149] rsync: writefd_unbuffered failed to write 4 bytes
> [sender]: B
error log below. Is there anywhere else i can check for
> errors?
>
> Also, what's the characters mean in the logfile, such as:
> >f..tpog RAID_One/data/file
>8.39M 100%4.12MB/s0:00:01 (xfer#3478,
> to-check=1224/8633)
>
> Any help much appr
o-check=1224/8633)
Any help much appreciated.
Andrew
Logfile:
2008/04/28 20:48:46 [3149] rsync: writefd_unbuffered failed to write 4 bytes
[sender]: Broken pipe (32)
2008/04/28 20:48:46 [3149] rsync: connection unexpectedly closed (735103
bytes received so far) [sender]
2008/04/28 20:48:46 [3149]
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
On Thu, 2007-12-13 at 09:48 -0500, Scott Parry wrote:
> I have enclosed the log for you to take a look at.
> I am running this from the root account.
Ah, this part beginning on line 30371 seems to be the root of the
problem:
22250 write(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"
erytime i run i get this error, it driving me nuts! any ideas would be
> appreciated.
> rsync: writefd_unbuffered failed to write 32768 bytes [sender]: Broken pipe
> (32)
> rsync: connection unexpectedly closed (30 bytes received so far) [sender]
> rsync error: error in rsync protocol
c -r --inplace --size-only --bwlimit=50 /home/shares/allusers/127 /mnt/s3
echo "`date +"%F %R"`: Finish backup-jd" >> $LOGFILE
umount /mnt/s3
Everytime i run i get this error, it driving me nuts! any ideas would be
appreciated.
rsync: writefd_unbuffered failed to write 3276
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
rs:
rsync: writefd_unbuffered failed to write 4092 bytes [generator]:
Operation not permitted (1)
rsync error: error in rsync protocol data stream (code 12) at
io.c(1124) [generator=2.6.8]
rsync error: received SIGUSR1 (code 19) at main.c(1095) [receiver=2.6.8]
I tried to google them, but couldn&
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
ribus/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: connection unexpectedly closed (796308 bytes received so far)
> [s
be: Invalid argument
rsync: writefd_unbuffered failed to write 32768 bytes: phase "unknown"
[sender]: Broken pipe (32)
rsync: connection unexpectedly closed (796308 bytes received so far)
[sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(434)
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
https://bugzilla.samba.org/show_bug.cgi?id=1959
--- Additional Comments From [EMAIL PROTECTED] 2005-04-21 08:46 ---
[EMAIL PROTECTED] [~]# rsync -avz -e ssh /home/ [EMAIL PROTECTED]:
building file list ... rsync: writefd_unbuffered failed to write 4092 bytes:
phase
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
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
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
as
a cron job?
The command I am using is /usr/local/bin/rsync –acv --stats
/data/ server::data
Any ideas, or is this insufficient info, if so, let me know
what you need.
rsync: writefd_unbuffered
failed to write 32768 bytes: phase "unknown": Broken pipe rsync
error: erro
1 - 100 of 111 matches
Mail list logo
