similar to: DO NOT REPLY [Bug 6175] New: write last transfer status when timeout or other error happens

Displaying 20 results from an estimated 6000 matches similar to: "DO NOT REPLY [Bug 6175] New: write last transfer status when timeout or other error happens"

2010 Mar 02
2
DO NOT REPLY [Bug 7195] New: timeout reached while sending checksums for very large files
https://bugzilla.samba.org/show_bug.cgi?id=7195 Summary: timeout reached while sending checksums for very large files Product: rsync Version: 3.0.7 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P3 Component: core AssignedTo: wayned at samba.org
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:
2008 May 21
35
DO NOT REPLY [Bug 5478] New: rsync: writefd_unbuffered failed to write 4092 bytes [sender]: Broken pipe (32)
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/show_bug.cgi?id=1959 OS/Version: Linux Status: NEW Severity: normal
2010 Oct 27
6
DO NOT REPLY [Bug 7757] New: with big file, rsync times out out when it should not; the sender is still responsive
https://bugzilla.samba.org/show_bug.cgi?id=7757 Summary: with big file, rsync times out out when it should not; the sender is still responsive Product: rsync Version: 3.0.7 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:
2010 Oct 27
0
DO NOT REPLY [Bug 2783] Random high loads during syncs (server side) / client stream errors
https://bugzilla.samba.org/show_bug.cgi?id=2783 tim.liim at alcatel-lucent.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tim.liim at alcatel-lucent.com ------- Comment #6 from tim.liim at alcatel-lucent.com 2010-10-27 00:27 CST ------- These
2011 Sep 22
3
[Bug 8475] New: memory leak around free_xattr() and rsync_xal_free(), with -aX, 200 bytes per file and per directory
https://bugzilla.samba.org/show_bug.cgi?id=8475 Summary: memory leak around free_xattr() and rsync_xal_free(), with -aX, 200 bytes per file and per directory Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core
2006 Sep 15
2
Library details - rsync 2.6.8
Hi , I have downloaded the latest rsync 2.6.8 package "rsync-2.6.8-sol8-sparc-local.gz" from solaris freeware website. After the installation of the package, i tried verify the list of dynamic dependancies, it is throwing the following problem. Any other package need to be downloaded for this ? ldd rsync libpopt.so.0 => (file not found) libiconv.so.2 =>
2009 Mar 11
5
DO NOT REPLY [Bug 6183] New: rsync error file too large (27)
https://bugzilla.samba.org/show_bug.cgi?id=6183 Summary: rsync error file too large (27) Product: rsync Version: 3.0.4 Platform: Other OS/Version: AIX Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: brossob@gmail.com QAContact:
2011 Feb 05
2
rsync not reporting diskfull error
I am involved with the development of lbackup. This message to the rsync mailing list is related to the following thread on the lbackup-disccussion mailing list : http://tinyurl.com/lbackup-discussion-diskfull Essentially, I am curious to if any one using rsync 3.0.7 on Mac OS (10.6) Server has experienced an out of disk space error and not had a message similar to the following reported : >
2010 Jun 02
1
rsync 3.0.7 network errors on MS-Windows
I am experiencing intermittent network failures on rsync 3.0.7 built using cygwin for Windows-XP (SP2). I am using GCC v4.4.2 and the latext version of cygwin. The rsync error long indicates things like: rsync: writefd_unbuffered failed to write 4092 bytes to socket [generator]: Connection reset by peer (104)rsync: read error: Connection reset by peer (104) rsync error: error in rsync
2002 Jul 02
1
Rsync: Segmentation fault
Rsync 2.5.5; transfer via ssh; sparc-sun-solaris2.5 (Ultra 1); gcc 2.8.1. Every time rsync on this box causes boundary violation. I attached two strange examples. I have a few rsync's corefiles (100MB and above) and I can examine them. I will be grateful for any help. -Mirek <-------------------------------------------------------------------------> received 966761 names done
2004 Jan 29
4
Can't Figure out why rsync job stops
I connecting to two offsite over servers, that are connected over dedicated T1 lines. I'm using the same script on both servers. One runs fine, but the other starts, gets the file list and processes a few folders. Then it will hang for about 5 minutes before sptting out the following errors: receiving file list ... 16756 files to consider dslagel/ dslagel/DRIVERS/ dslagel/DRIVERS/ATP_PKG/
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
2012 Mar 07
1
Long delays in rsync manifested by repeated entries, CentOS, rsync v2.6.8.
Hello, rsync list folks, Recently, rsyncs abort during busier times of the day, although they run error-free during non-busy hours. Problem 1 - Many rsyncs abort these errors: Read from remote host www.xxx.yyy.zzz: Connection reset by peer rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32) rsync: connection unexpectedly closed (3929920 bytes received so far)
2010 Sep 25
2
"writefd_unbuffered failed to write 4092 bytes to socket"
I'm attempting to maintain a mirror of a remote database, ~ 66Gb on a FreeBSD platform. I do not have direct access to the database except by rsync, anon. ftp etc. I'm running rsync nightly from crontab, with the cmd /usr/local/bin/rsync -avvv --port=33444 ftp.filesource.org::ftp . >> rsynclog generated the following in the cron report First error [1] rsync error: received SIGINT,
2011 Feb 18
3
DO NOT REPLY [Bug 7959] New: erro occoure ! rsync can't auto exit
https://bugzilla.samba.org/show_bug.cgi?id=7959 Summary: erro occoure ! rsync can't auto exit Product: rsync Version: 2.6.8 Platform: x86 OS/Version: Windows XP Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: 490779618 at qq.com
2005 Apr 27
7
[Bug 2654] timeout is always triggered with 2.6.4
https://bugzilla.samba.org/show_bug.cgi?id=2654 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From wayned@samba.org 2005-04-27 02:21 ------- The generator's setting of the ignore_timeout
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 Apr 01
12
DO NOT REPLY [Bug 5365] New: --backup and --xattrs are not compatible
https://bugzilla.samba.org/show_bug.cgi?id=5365 Summary: --backup and --xattrs are not compatible Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Other Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: fauthier@free.fr
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: