samba-bugs | 25 Nov 23:58 2014
Picon

[Bug 10963] New: rsync to multiple destinations

https://bugzilla.samba.org/show_bug.cgi?id=10963

            Bug ID: 10963
           Summary: rsync to multiple destinations
           Product: rsync
           Version: 3.0.6
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: Dave <at> Yost.com
        QA Contact: rsync-qa <at> samba.org

-- 
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

net.rsync | 25 Nov 16:02 2014

Dealing with an unreliable remote

'Lo.

I've run into a frustrating issue when trying to synchronize a
directory hierarchy over a reliable (but slow) connection to an 
unreliable remote. Basically, I have the following:

  http://mvn-repository.io7m.com/com/io7m/

This is a set of nested directories containing binaries and sources for
projects I develop/maintain. Every time a new release is made, I deploy
the binaries and sources to an exact copy of the above hierarchy on my
local machine, and then rsync that (over SSH) to
mvn-repository.io7m.com.

  $ rsync -avz --delete --progress local/ io7m.com:/home/io7m/mvn-repository.io7m.com/

The problem:

The latest project produces one .jar file that's about 80mb.
Evidently, the hosting provider I use for io7m.com is using some sort
of process tracking system that kills processes that have been running
for too long (I think it just measures CPU time). The result of this is
that I get about 50% of the way through copying that
(comparatively) large file, and then the remote rsync process is
suddenly killed because it has been running for too long.

This would be fine, except that it seems that rsync is utterly refusing
all efforts to continue copying that file from wherever it left off. It
always restarts copying of the file from nothing and tries to copy the
full 80mb, resulting it being killed halfway through and causing much
(Continue reading)

David M. | 22 Nov 21:12 2014
Picon

rsync not transferring files

Hi there,
I am running rsync-3.0.6-12.el6.x86_64 on a centos 6.6 box. Am trying to
get files from a remote server (centos 6.5) to my local machine. It
appears to connect fine, but does not transfer any file. this is what I
am seeing

[youcantoo <at> testbox home]# rsync -avvvzh -P --stats --delete
servername::backupdir/ /home/findmoore

opening tcp connection to servername port 873
sending daemon args: --server --sender -vvlogDtprze.iLs . backupdir/
Welcome to the servername rsync server.

  You may download the distribution by using the appropriate module name.
  For example:

  rsync -avz -P --stats --delete username <at> servername::modulename/
/local/path

receiving incremental file list
recv_file_name(.)
received 1 names
recv_file_list done
get_local_name count=1 /home/findmoore
generator starting pid=2499
delta-transmission enabled
recv_generator(.,0)
delete_in_dir(.)
recv_files(1) starting
recv_generator(.,1)
(Continue reading)

samba-bugs | 21 Nov 08:46 2014
Picon

[Bug 10951] New: Emtpy parameter triggers unwanted behavior, but no error message

https://bugzilla.samba.org/show_bug.cgi?id=10951

            Bug ID: 10951
           Summary: Emtpy parameter triggers unwanted behavior, but no
                    error message
           Product: rsync
           Version: 3.1.0
          Hardware: x64
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: stian <at> wis.no
        QA Contact: rsync-qa <at> samba.org

If you add a parameter (ex. --exclude <path>) to the rsync command without a
value, you get some unwanted behavior running the command. No error message
will be triggered, and no output will be shown (especially if running the
command from remote server through a SSH session).

We were running the following command for backup of a remote server:
"/usr/bin/ssh -x -l backuppc <servername>.<domain>.lan sudo /usr/bin/rsync
--numeric-ids --perms --owner --group -D --links --hard-links --times
--block-size=2048 --recursive / --exclude --exclude /mnt --exclude
/var/log/tomcat6"

If you check after the "--recursive /" there is two "--exclude" and the first
one without a value. If we run this command there is no output from rsync
(Continue reading)

samba-bugs | 20 Nov 18:59 2014
Picon

[Bug 10950] New: rsync hangs when specifying a backup directory

https://bugzilla.samba.org/show_bug.cgi?id=10950

            Bug ID: 10950
           Summary: rsync hangs when specifying a backup directory
           Product: rsync
           Version: 3.1.0
          Hardware: x64
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: bugzilla.samba <at> familie-kinder.de
        QA Contact: rsync-qa <at> samba.org

rsync hangs after working a few minutes without any error messages.

Since I have upgraded from Ubuntu 12.04.5 to Ubuntu 14.04 rsync comes in
version 3.1.0. And since the upgrade rsync hangs if I specify a backup
directory by the parameters "--backup --backup-dir=...".
Without the both backup parameters rsync works fine as before the upgrade!

So I tried the argument "--block-size" as described in
https://bugzilla.samba.org/show_bug.cgi?id=10518#c8 although I think it is
another issue there because I don't have large vm files.
But if I specify 10 MB I get the error: "rsync: --block-size=10485760 is too
large (max: 131072)". And with 131072 rsync hangs too.

Now I tried the arguments "--protocol=30" and "--protocol=29", but rsync hangs
(Continue reading)

devzero | 19 Nov 15:10 2014
Picon

Re: Bug-report:rsync may hung if time jumps backwards

Hi, 

it seems that one already has been fixed in 3.1.0, see

https://bugzilla.samba.org/show_bug.cgi?id=9789

and

https://git.samba.org/?p=rsync.git;a=commit;h=2dc2070992c00ea6625031813f2b6c886ddc3ade

you are still using 2.6.9 ? that`s rather old (~ 8yrs?) and may have bugs and security issues already being fixed.

regards
roland

> List:       rsync
> Subject:    Bug-report:rsync may hung if time jumps backwards
> From:       yhu2 <yadi.hu () windriver ! com>
> Date:       2014-11-17 6:44:25
> Message-ID: 54699949.1020503 () windriver ! com
> [Download message RAW]
> 
> Hello eveyone!
> 
> According to below reproduce steps,you could observe a rsync hang:
> 
> 1:configure and startup rsync service and
> 
> mkdir /root/a
> mkdir /root/b
(Continue reading)

samba-bugs | 18 Nov 02:48 2014
Picon

[Bug 10941] New: include should supersede max-size

https://bugzilla.samba.org/show_bug.cgi?id=10941

            Bug ID: 10941
           Summary: include should supersede max-size
           Product: rsync
           Version: 3.0.9
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: dgermansbz <at> Real-world-systems.com
        QA Contact: rsync-qa <at> samba.org

Most of the very large files I have are distributions from elsewhere. 
I have used --max-size=10MB to skip them.
I do have some specific files that I want transferred which are greater than
10MB so I entered them in the --include-from=includes.
I expected rsync to transfer the files listed in includes but it didn't.

-- 
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

(Continue reading)

yhu2 | 17 Nov 07:44 2014

Bug-report:rsync may hung if time jumps backwards


Hello eveyone!

According to below reproduce steps,you could observe a rsync hang:

1:configure and startup rsync service and

mkdir /root/a
mkdir /root/b
dd if=/dev/zero of=/root/b/1 bs=1M count=1
dd if=/dev/zero of=/root/b/2 bs=1M count=1
dd if=/dev/zero of=/root/b/3 bs=1M count=1
dd if=/dev/zero of=/root/b/4 bs=1M count=1
dd if=/dev/zero of=/root/b/5 bs=1M count=1

2: start testcase

./change-time-loop.sh > /dev/null &
./rsync-loop.sh

After applying this patch ,this issue went away.

--- rsync-2.6.9/BUILD/rsync-2.6.9/util.c    2014-11-11 
13:02:11.495609639 +0800
+++ rsync-2.6.9/BUILD/rsync-2.6.9/util.c    2014-11-11 
13:01:37.606569696 +0800
 <at>  <at>  -1174,8 +1174,11  <at>  <at> 
   * Always returns TRUE.  (In the future it might return FALSE if
   * interrupted.)
   **/
(Continue reading)

Joe | 16 Nov 22:53 2014
Picon

Using --fuzzy

I have a lot of files (and directories) (up to a few hundred at a time)
that I get from various sources. Some time after I get them (after they
are already backed up), I often have to move them around and normalize
their names.

When I do this, rsync sees them as unrelated to the copies of these
files which are already on the backup destination. When I can't use the
--delete option for various reasons, this causes multiple copies of the
files to be saved in the backup destination.

I see that there is a --fuzzy option which, specified twice, may address
this issue.

Is there a tutorial or howto that addresses this so I can better
understand it before I start experimenting? I don't want to have to
reinvent strategies which, doubtless, already exist.

--

-- 
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

eight ∞ | 15 Nov 11:26 2014

rsync stalls at .sparsebundle directories on OS X‏‏

Hi. I try to make backups from one disk to another. I have .sparsebundle[1] directories on the source drive
(/Volumes/data/). When rsync reaches the first .sparsebundle it stalls and stays there until i ctrl+c.
I'm using OS X Yosemite and rsync version 3.1.1 protocol version 31 installed via homebrew. However, I had
this problem on OS X Lion too using rsync 3.0.9. Actually, the reason I updated to Yosemite was partly
because I thought I might get rsync working again. 

Here is the full line:
sudo rsync -vaxAXES --log-file="/Volumes/backup/__rsync/$(date +"%Y-%m-%d_%H%M%S").log"
--exclude="__rsync/" --exclude=".Trashes/" --exclude=".Spotlight-V100"
--exclude=".fseventsd/" --exclude=".DocumentRevisions-V100/" --exclude=".TemporaryItems/"
/Volumes/data/ /Volumes/backup/

I'm also seeing 32 lines of of "rsync: unpack_smb_acl: sys_acl_get_info(): Undefined error: 0 (0)"
errors directly after "sending incremental file list".

Any clues would be very welcome.

[1] https://en.wikipedia.org/wiki/Sparse_image#Sparse_bundle_disk_images
 		 	   		  
--

-- 
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

samba-bugs | 14 Nov 07:51 2014
Picon

[Bug 10936] New: Rsync path hijacking attack vulnerability

https://bugzilla.samba.org/show_bug.cgi?id=10936

            Bug ID: 10936
           Summary: Rsync  path  hijacking  attack  vulnerability
           Product: rsync
           Version: 3.1.1
          Hardware: All
                OS: All
            Status: NEW
          Severity: critical
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: gaojianfeng <at> baidu.com
        QA Contact: rsync-qa <at> samba.org

Created attachment 10433
  --> https://bugzilla.samba.org/attachment.cgi?id=10433&action=edit
Rsync  path  hijacking  attack  vulnerability.pdf (Detailed documentation)

Hi all:
    In  newest version rsync,Baidu Security Team found a vulnerability which is
similar to wget ftp CVE-2014-4877
(http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-4877).When a
clientuses parameter -a to synchronize files of the server-side(default), for
example:
rsync -avzP  127.0.0.1::share   /tmp/share
Rsync  recursive synchronous all files,An attacker can hijack the file path  by
modifying the code of the server-side,allows remote  servers to write to
arbitrary files, and consequently execute arbitrary code .
(Continue reading)


Gmane