[Bug 13953] New: error message instead of --stats informations (in case of vanished files), using rsync 3.1.1 and rsync 3.0.9
https://bugzilla.samba.org/show_bug.cgi?id=13953 Bug ID: 13953 Summary: error message instead of --stats informations (in case of vanished files), using rsync 3.1.1 and rsync 3.0.9 Product: rsync Version: 3.1.1 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee: wa...@opencoder.net Reporter: g...@4js.com QA Contact: rsync...@samba.org Hello, The issue I'm reporting is about the stats informations usually shown (by --stats). This stats information is missing in case of vanished files. I got an error about protocol data stream instead. Probably an issue between the both version/protocol. It's appened since I have updated the rsync version on FOO (from 3.0.9 to 3.1.1). Now the rsync version between "client"/"server" are not the same. In my case, the issue only appears in case of vanished files. 1) before (no issue) on FOO rsync 3.0.9 (debian 7) on BAR rsync 3.0.9 (RHEL 7) 2) after (got the issue) on FOO rsync 3.1.1 (debian 8) on BAR rsync 3.0.9 (RHEL 7) I got this error instead of the stats informations : > rsync: writefd_unbuffered failed to write 162 bytes to socket [sender]: > Broken pipe (32) > rsync error: error in rsync protocol data stream (code 12) at io.c(1532) > [sender=3.0.9] > rsync: [generator] write error: Broken pipe (32) > rsync error: error in rsync protocol data stream (code 12) at io.c(820) > [generator=3.1.1] On my backup serveur named FOO trying to get data from a source target named BAR The minimal command seems like : rsync [...] --stats [...] BAR:/path/to/dir/ ./ if you are curious the real used command is : rsync \ --hard-links --numeric-ids --human-readable --prune-empty-dirs --archive --one-file-system --force \ --stats \ --compare-dest=/path/to/dir1 --delete --exclude-from=/path/to/file1.exclude --rsh=ssh \ BAR:/path/to/dir/ ./ Additionnal informations On 5/9/19 3:10 AM, root wrote:> Thu May 9 01:48:03 CEST 2019 > > Number of files: 1565540 > Number of files transferred: 591395 > Total file size: 1181.13G bytes > Total transferred file size: 136.68G bytes > Literal data: 129.42G bytes > Matched data: 7.33G bytes > File list size: 48.55M > File list generation time: 9.667 seconds > File list transfer time: 0.000 seconds > Total bytes sent: 37.16M > Total bytes received: 129.52G > > sent 37.16M bytes received 129.52G bytes 26.40M bytes/sec > total size is 1181.13G speedup is 9.12 > rsync warning: some files vanished before they could be transferred (code 24) > at main.c(1536) [generator=3.0.9] > > # there are some file vanished : > file has vanished: > "/path/to/files/xx" > file has vanished: > "/path/to/files/" > file has vanished: > "/path/to/files/" > file has vanished: > "/path/to/files/x"[...] On 5/15/19 3:20 AM, root wrote: > Wed May 15 02:31:00 CEST 2019 > > rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken > pipe (32) > rsync error: error in rsync protocol data stream (code 12) at io.c(1532) > [sender=3.0.9] > rsync: [generator] write error: Broken pipe (32) > rsync error: error in rsync protocol data stream (code 12) at io.c(820) > [generator=3.1.1] > > # there are some file vanished : > file has vanished: > "/path/to/files/" > file has vanished: > "/path/to/files/xx" > file has vanished: > "/path/to/files/" > file has vanished: > "/path/to/files/x" ... On 5/16/19 3:14 AM, root wrote: > Thu May 16 02:03:05 CEST 2019 > > rsync: writefd_unbuffered failed to write 162 bytes to socket [sender]: > Broken pipe (32) > rsync error: error in rsync protocol data stream (code 12) at io.c(1532) > [sender=3.0.9] > rsync: [generator] write error: Broken pipe (32) > rsync error: error in rsync protocol data stream (code 12) at io.c(820) > [generator=3.1.1] > > # there are some file vanished : > file has vanished: > "/path/to/files/" > file has vanished: > "/path/to/files/" > file has vanished: > "/path/to/files/" > file has vanished: > "/path/to/files/xx" On FOO # rsync --version rsync version 3.1.1 protocol version 31 Copyright
[Bug 12769] New: error allocating core memory buffers (code 22) depending on source file system
https://bugzilla.samba.org/show_bug.cgi?id=12769 Bug ID: 12769 Summary: error allocating core memory buffers (code 22) depending on source file system Product: rsync Version: 3.1.0 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee: way...@samba.org Reporter: mss...@fau.de QA Contact: rsync...@samba.org We run an openSuSE Leap 42.2 and an Ubuntu 14.04.5 on two servers. Copying a large number of files (in this case about 28 million) leads to different results depending on the source file system. We copy with rsync -rlptgoDAxHnP --info=progress2 --delete --link-dest=$LINK_DEST root@$SERVER:/$FOLDER /backup/rsynctest/ . Replacing --delete by --delete-delay doesn't change the behaviour as expected. The error occurs with and without the option -n, in this case it is just for testing reasons included. In case the source is located on an Ext4 file system we run into the following error message after about 26 million files copied: ERROR: out of memory in hashtable_node [sender] rsync error: error allocating core memory buffers (code 22) at util2.c(102) [sender=3.1.0] In case the source is located on an XFS file system the above command copies all files without error. Both of the file systems hold the same data as the one is the backup copy of the other. The behaviour appears as well when we use rsync via an rsync server and not via SSH and as well when we copy locally on one of the two machines. And it appears regardless of the operating system (openSuSE 42.2 or Ubuntu 14.04.5). I did not try in the last time but replaying the backup from an Ext4 showed this error at least one year ago as well. With the change to XFS on the source file system the error suddenly disappeared. As the error appears even if just doing a --dry-run it seems to be related to the way rsync handles metadata. The data size seems to be unimportant. -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 12132] New: Error on attributes when directory read-only
https://bugzilla.samba.org/show_bug.cgi?id=12132 Bug ID: 12132 Summary: Error on attributes when directory read-only Product: rsync Version: 3.1.2 Hardware: All OS: Mac OS X Status: NEW Severity: normal Priority: P5 Component: core Assignee: way...@samba.org Reporter: dan+mozi...@pasteur.fr QA Contact: rsync...@samba.org When making an rsync of a directory with mode 0555 and attributes, there is an error on any included file creation: failed: Permission denied (13) Smallest test directory: # coriolis:/tmp/test % ls -@alO total 0 drwxr-xr-x 4 dan wheel - 136 Aug 8 19:16 . drwxrwxrwt 15 root wheel - 544 Aug 8 19:01 .. dr-xr-xr-x@ 2 dan wheel - 102 Aug 8 17:54 dir+attr com.apple.FinderInfo 32 dr-xr-xr-x 2 dan wheel - 102 Aug 8 19:13 dir+noattr 0. Versions in use Note: this is note the installed version with MacOS X (2.6.9) but the latest one built from MacPorts (3.1.2). The OS is OS X 10.10.5 (on source and destination) rsync --version rsync version 3.1.2 protocol version 31 Copyright (C) 1996-2015 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes, no prealloc, file-flags, HFS-compression rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. ssh doppler /opt/local/bin/rsync --version rsync version 3.1.2 protocol version 31 Copyright (C) 1996-2015 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes, no prealloc, file-flags, HFS-compression rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. 1. Case with the directory without attributes # coriolis:/tmp/test % rsync -aArvX --rsync-path=/opt/local/bin/rsync dir+noattr doppler:/tmp sending incremental file list dir+noattr/ dir+noattr/index.xml.gz sent 102,608 bytes received 39 bytes 41,058.80 bytes/sec total size is 102,449 speedup is 1.00 2. Case with the directory with attributes # coriolis:/tmp/test % rsync -aArvX --rsync-path=/opt/local/bin/rsync dir+attr doppler:/tmp sending incremental file list dir+attr/ dir+attr/index.xml.gz rsync: mkstemp "/tmp/dir+attr/.index.xml.gz.E5wKN9" failed: Permission denied (13) sent 102,671 bytes received 127 bytes 68,532.00 bytes/sec total size is 102,449 speedup is 1.00 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1249) [sender=3.1.2] -- You are receiving this mail because: You are the QA Contact for the bug. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 10719] New: Error with cached effective process gid
https://bugzilla.samba.org/show_bug.cgi?id=10719 Summary: Error with cached effective process gid Product: rsync Version: 3.1.1 Platform: x64 OS/Version: FreeBSD Status: NEW Severity: major Priority: P5 Component: core AssignedTo: way...@samba.org ReportedBy: o...@mamontov.net QAContact: rsync...@samba.org Tere was an error in previous git commit 3b83a22057b71e7df2b960d3997fb4474910f30e: [lonerr@neon ~/src/rsync]% git show 3b83a22057b71e7df2b960d3997fb4474910f30e commit 3b83a22057b71e7df2b960d3997fb4474910f30e Author: Wayne Davison way...@samba.org Date: Wed Sep 2 08:56:34 2009 -0700 Define and use our_gid variable. In this commit effective process gid determined once (in main.c), but after client connect and daemon forked effective gid may be different (when you use the 'gid' option in config file). Now this commit was merged in 3.1.x thus broken some use cases. Simple test case: 1. Prepare destination catalog: rm -rf /tmp/dst mkdir /tmp/dst chmod 755 /tmp/dst chown nobody:nobody /tmp/dst 2. Prepare minimal rsyncd.conf: -- pid file = /var/run/rsyncd.pid uid = nobody gid = nobody read only = no use chroot = no [dst] path = /tmp/dst -- 3. Start rsyncd as standalone daemon with standard rc script. 4. Try to rsync empty file belongs to group wheel (gid==0). touch /tmp/src chown 0:0 /tmp/src rsync -av /tmp/src localhost::dst/ sending incremental file list src rsync: chgrp .src.tIDLzz (in dst) failed: Operation not permitted (1) sent 79 bytes received 111 bytes 380.00 bytes/sec total size is 0 speedup is 0.00 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.1] With this commit rollbacked - operation is restored. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 9594] New: Error transferring user and non-user xattr using --fake-super under Linux
https://bugzilla.samba.org/show_bug.cgi?id=9594 Summary: Error transferring user and non-user xattr using --fake-super under Linux Product: rsync Version: 3.1.0 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: way...@samba.org ReportedBy: succinic.anhydr...@yahoo.com QAContact: rsync...@samba.org Overview: I'm using rsync -aX as root on the sender (local) and --fake-super on the receiver (remote) to preserve attributes. I'm using version 3.1.0dev as I needed a solution to Bug 8201 (https://bugzilla.samba.org/show_bug.cgi?id=8201). I get the error could not find xattr #1 for [foo] when trying to transfer a file that has both a non-user extended attribute with a long string value AND a user extended attribute where the name of the user EA preceeds user.rsync in lexical sort order. The error is triggered only if the transfer is remote AND rsync is run as root on the local/sender side so both non-user and user attrs are transferred. Steps to reproduce: 1. sudo touch foo 2. sudo setfattr -n user.rsx -v 1 foo ## user.rsx sorts before user.rsync 3. sudo setfattr -n security.selinux -v system_u:object_r:cachefiles_var_t:s0 foo ## non-user EA with a long string value 5. sudo rsync -i -aOzAX --numeric-ids --rsync-path=rsync --fake-super foo user@remote:/tmp/ ## user does not have root access on host remote Actual Results: f+ foo [receiver] could not find xattr #1 for foo rsync error: protocol incompatibility (code 2) at xattrs.c(620) [receiver=3.1.0dev] Expected Results: no error, file and xattrs transferred successfully System details: Local/sender and remote/receiver are RHEL 6.3 with rsync 3.1.0dev -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 7124] New: Error exit causes I/O error
https://bugzilla.samba.org/show_bug.cgi?id=7124 Summary: Error exit causes I/O error Product: rsync Version: 3.1.0 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: way...@samba.org ReportedBy: m...@mattmccutchen.net QAContact: rsync...@samba.org Error exits that happen early in the rsync run appear to cause an I/O error on the client. For example, passing an unknown option: $ rsync-dev -M--blop blort rsync: on remote machine: --blop: unknown option rsync error: syntax or usage error (code 1) at pipe.c(149) [Receiver=3.1.0dev] need to read 1024 bytes, iobuf.in.buf is only 0 bytes. rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(223) [sender=3.1.0dev] This would seem to indicate that the new code to report an error exit gracefully in 3.1.0 is not working properly. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 6405] New: Error parsing commandline in version 3.0.6
https://bugzilla.samba.org/show_bug.cgi?id=6405 Summary: Error parsing commandline in version 3.0.6 Product: rsync Version: 3.0.6 Platform: Sparc OS/Version: Solaris Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: way...@samba.org ReportedBy: sa...@japes.de QAContact: rsync...@samba.org Hello, currently I'm having problems with version 3.0.6 which I don't have with version 3.0.5. This is what happens: bin/rsync -vvauxSpz rsync://xxx.xxx.com:11000::cadappl_sde/cadappl_sde/ictools/tetramax . opening connection using: ssh rsync rsync --server --sender -vvulogDtprxSze.is . //xxx.xxx.com:11000::cadappl_sde/cadappl_sde/ictools/tetramax ssh: Could not resolve hostname rsync: host/servname not known rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(600) [receiver=3.0.6] Obviuosly there is a problem extracting the hostname from the rsync://... expression. I tried this on both Solaris and Linux. Regards, Christian -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 6027] New: Error when rsync encounters empty symlinks
https://bugzilla.samba.org/show_bug.cgi?id=6027 Summary: Error when rsync encounters empty symlinks Product: rsync Version: 3.0.4 Platform: x86 OS/Version: Linux Status: NEW Severity: minor Priority: P3 Component: core AssignedTo: way...@samba.org ReportedBy: k...@kaishome.de QAContact: rsync...@samba.org Recently I needed to recover a system with a damaged file system. After fsck there were some symlinks broken, pointing to nowhere (or better pointing to an empty file name, it showed up as filename - in ls -al). Rsync fails to sync these symlinks, it just breaks with the following message: ERROR: buffer overflow in recv_file_entry Instead I wished either rsync correctly sync'ing these - or if empty symlinks cannot be created it should skip these and issue a warning but not exit with a buffer overflow. Manually deleting the broken symlinks from the source solved this (thus setting this bug to minor), but it was much work and I needed to recover rsync several times. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 6032] New: error in rsync protocol data stream
https://bugzilla.samba.org/show_bug.cgi?id=6032 Summary: error in rsync protocol data stream Product: rsync Version: 3.0.4 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: way...@samba.org ReportedBy: rm...@lexiconn.com QAContact: rsync...@samba.org Command: /usr/bin/rsync -aze /usr/local/ssh/bin/ssh --hard-links --force --ignore-errors --numeric-ids --delete --exclude=/sys --exclude=/proc --exclude=/var/named/chroot/proc --exclude=/home4 --exclude=/home5 --exclude=/backup --exclude=/var/log --exclude=/home/logs --exclude=/home2/logs/ $server:/ /home/backup/$short The error happens at the same spot during the rsync copy: Read from remote host $server: Connection reset by peer rsync: connection unexpectedly closed (16892096 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(632) [receiver=3.0.4] rsync: connection unexpectedly closed (408 bytes received so far) [generator] rsync error: unexplained error (code 255) at io.c(632) [generator=3.0.4] -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 5795] New: error in rsync protocol data stream (code 12) at io.c(632) [sender=3.0.4]
https://bugzilla.samba.org/show_bug.cgi?id=5795 Summary: error in rsync protocol data stream (code 12) at io.c(632) [sender=3.0.4] Product: rsync Version: 3.0.4 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: blocker Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] 0 424 Z% rsync -av --sparse --progress --partial /Users/yost/Documents/VMWare/winxp.vmwarevm /Volumes/x/vmware sending incremental file list winxp.vmwarevm/ winxp.vmwarevm/winxp.vmdk 1578172416 17% 11.08MB/s0:10:35 rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32) rsync: connection unexpectedly closed (32 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(632) [sender=3.0.4] 12 425 Z% rsync --version rsync version 3.0.4 protocol version 30 Copyright (C) 1996-2008 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 32-bit inums, 32-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. 0 426 Z% -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 5694] New: error when transferring a large amount of data
https://bugzilla.samba.org/show_bug.cgi?id=5694 Summary: error when transferring a large amount of data Product: rsync Version: 2.6.8 Platform: x86 OS/Version: Windows XP Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] sent 768624 bytes received 10418303180 bytes 7795788.85 bytes/sec total size is 10434467509 speedup is 1.00 rsync error: some files could not be transferred (code 23) at main.c(1298) [generator=2.6.8] I was using rsync to move the contents of a huge folder to a newly created folder on a different virtual machine (but same physical machine) and it died after transferring some data. above is the transcript it provided after the error. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
DO NOT REPLY [Bug 3430] New: Error with ACL-patch and -x on mountpoint
https://bugzilla.samba.org/show_bug.cgi?id=3430 Summary: Error with ACL-patch and -x on mountpoint Product: rsync Version: 2.6.6 Platform: Other OS/Version: FreeBSD Status: NEW Severity: minor Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] Hi, using rsync-2.6.6 with ACL patch on two freebsd systems (with dirvish) and the options -x and --acls, we get the following error: send_acl: sys_acl_get_file(mayerr/test, SMB_ACL_TYPE_ACCESS): Operation not supported and so on for 3 more cycles. Rsync is right about the fact that this SMB share mount point doesn't support acls, but I still wonder why it even tries to access it with the -x option. As far as I can tell the backups still work, but having those errors all over the logs isn't nice. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 3245] New: error messages not precise enough
https://bugzilla.samba.org/show_bug.cgi?id=3245 Summary: error messages not precise enough Product: rsync Version: 2.6.6 Platform: x86 OS/Version: Windows XP Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] Generally speaking, it seems that the structure to report an error is badly implemented, and makes the error messages not clear enough. For example, we might get a Code 23 error, but don't know anything about it. This makes misconfigurations difficult to find out and makes the mailing list far too buzy providing support to all users who don't know about that or this problem. I think that the code should be a bit rewritten as for the output of the messages. Normally we can know if there was a memory problem, a disk problem, a file that was missing when doing the copy (and which one) or anything else and it would be very helpful to print that out to the user. Also, one interesting thing would be to assert errors in the code itself so that we could know exactly where in the code the problem happened. The current code line report normally just specifies the end of a main procedure merely that the exact place of the error. Regards, Daniel -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 2357] New: error when compiling rsync under Windows Services for Unix
https://bugzilla.samba.org/show_bug.cgi?id=2357 Summary: error when compiling rsync under Windows Services for Unix Product: rsync Version: 2.6.4 Platform: All OS/Version: Windows XP Status: NEW Severity: minor Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] Error: undefined reference to `_makedev' occurs when compiling under Windows Services for Unix 3.5. To remedy, simply edit flist.c and change every occurrence of 'makedev' to 'mkdev'. Once you run make again, it compiles fine and runs on Windows with no problems (so far). -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 1633] New: error in rsync protocol data stream (code 12) at io.c(359)
https://bugzilla.samba.org/show_bug.cgi?id=1633 Summary: error in rsync protocol data stream (code 12) at io.c(359) Product: rsync Version: 2.6.3 Platform: Alpha URL: http://www.snailbook.com/faq/scp-ossh-to-ssh2.auto.html OS/Version: OSF/1 Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] Using rsync from OSF with commercial ssh.com to Solaris with Sun ssh works fine. Using rsync from Solaris with Sun (OpenSSH derived) to OSF fails with: select: Bad file number rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(359) This sounds like the scp compatibility problem between the two. Does rsync use ssh protocol 2 or protocol 1 which scp uses? Because protocol 1 is not running on the OSF machine. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
New Error
I've never seen this one before. I'm using rsync 2.6.2 on both ends. Server (Athlon, 768MB RAM) checks out just fine. The only anomoly appears to be that this process has been running for 248268.43 seconds (this is not unexpected with this particular host we're backing up). Commandline: /usr/bin/time -p /usr/bin/rsync -e /usr/bin/ssh --archive --compress --sparse --stats --delete --numeric-ids --partial--exclude /proc --exclude /mnt xxx.example.com:/ /storage/xxx.example.com/ 12 Error message: rsync: writefd_unbuffered failed to write 4092 bytes: phase unknown: Broken pipe rsync: connection unexpectedly closed (7054382421 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(836) rsync error: error in rsync protocol data stream (code 12) at io.c(342) Command exited with non-zero status 12 real 248268.43 user 464.11 sys 124.48 -- http://www.quantumlinux.com Quantum Linux Laboratories, LLC. ACCELERATING Business with Open Technology The measure of the restoration lies in the extent to which we apply social values more noble than mere monetary profit. - FDR -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
