Aron Rotteveel | 27 Mar 12:29 2015
Picon

Re: rsync 3.0.9 segmentation fault

Yes, I removed "--no-inc-recursive", without success.

--
Best regards / Met vriendelijke groet,

Aron Rotteveel

2015-03-27 12:24 GMT+01:00 Kevin Korb <kmk <at> sanitarium.net>:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Have you tried removing --no-inc-recursive yet?

On 03/27/2015 07:19 AM, Aron Rotteveel wrote:
> Hi Roland,
>
> Thanks for the reply. Memory usage on both machines seem fine. The
> server has 4GB's of RAM, of which about 3GB is used during the file
> list build and about 1.5GB is used during the actual transfer. The
> client has 16GB of RAM with a peak usage of 8.5GB.
>
> I just tried three transfers in a row and it consistently breaks at
> a certain point, after which I get the "ERROR: out of memory in
> flist_expand [sender]" error. There is not much special to mention
> regarding the file on which it breaks: it's a 22KB JPEG file with
> no special attributes.
>
> The backup server is running Debian 7.8, the client runs on CentOS
> 5.11.
>
> A `find . | wc -l` in the backup directory results in 7434013
> files.
>
> -- Best regards / Met vriendelijke groet,
>
> Aron Rotteveel
>
> 2015-03-19 20:10 GMT+01:00 <devzero <at> web.de
> <mailto:devzero <at> web.de>>:
>
> Hi Aron,
>
> i hope it`s ok for you if i bring this back on-list. Your issue
> and the way or possible fix to resolve it may be interesting for
> others too (that may include future searches etc)
>
> so with 3.1.1 we are a step further....
>
> i don`t really have a clue what`s happening here but my next step
> would be taking a closer look on how the memory usage of rsync on
> the client and server grows.
>
> you could log it like this: while true;do ps -eo
> vsz,rss,sz,rsync|grep cron;sleep 10;done >logfile
>
> does it grow continuously? does the oom situation reproducibly
> happen at a certain size ? what`s the client and server platform?
> how many files? (-> https://rsync.samba.org/FAQ.html#5 ! )
>
> regards roland
>
> *Gesendet:* Donnerstag, 19. März 2015 um 12:24 Uhr *Von:* "Aron
> Rotteveel" <rotteveel.aron <at> gmail.com
> <mailto:rotteveel.aron <at> gmail.com>> *An:* devzero <at> web.de
> <mailto:devzero <at> web.de> *Betreff:* Re: rsync 3.0.9 segmentation
> fault In addition to my last message:
>
> * Client (sender) has 16GB's or RAM, of which only 6.5GB is used
> during peak. * I tried using --no-inc-recursive, but it does not
> solve the issue.
>
> What currrently is puzzling me is the question of why I am
> receiving these errors when my server seems to have plenty of
> memory to spare.
>
> -- Best regards / Met vriendelijke groet,
>
> Aron Rotteveel
>
> 2015-03-19 11:52 GMT+01:00 Aron Rotteveel
> <rotteveel.aron <at> gmail.com>:
>
> Hi Roland,
>
> I just upgrade both the client and host to 3.1.1 and seem to memory
> related issues now:
>
> ERROR: out of memory in make_file [sender] rsync error: error
> allocating core memory buffers (code 22) at util2.c(102)
> [sender=3.1.1] [sender] _exit_cleanup(code=22, file=util2.c,
> line=102): about to call exit(22) [Receiver] _exit_cleanup(code=22,
> file=io.c, line=1633): about to call exit(22)
> ----------------------------------------------------------------------------
>
>
rsnapshot encountered an error! The program was invoked with
> these options: /usr/bin/rsnapshot -c \
> /home/remotebackup/hosts/<redacted>/rsnapshot.conf sync
> ----------------------------------------------------------------------------
>
>  -- Best regards / Met vriendelijke groet,
>
> Aron Rotteveel
>
> 2015-03-18 23:43 GMT+01:00 <devzero <at> web.de>:
>
> Hi,
>
> rsync 3.0.9 is quite ancient, more than 3 years old. A lot of bugs
> have been fixed since then.
>
> Is there a chance to update to the latest rsync version and retry
> with that ?
>
> regards Roland
>
> *Gesendet:* Dienstag, 17. März 2015 um 11:51 Uhr *Von:* "Aron
> Rotteveel" <rotteveel.aron <at> gmail.com> *An:* rsync <at> lists.samba.org
> *Betreff:* rsync 3.0.9 segmentation fault Hi,
>
> I am experiencing segfaults when transferring files via rsync
> though sudo. Setup:
>
> - Backupserver initiates the rsync command with --delete -vvv
> --no-inc-recursive --numeric-ids --delete-excluded --relative
> --rsync-path=/home/backupuser/rsync-wrapper.sh - rsync-wrapper.sh
> (on the client) contains /usr/bin/sudo /usr/bin/rsync "$ <at> "; - user
> "backupuser" has sudo access to the rsync command - Both host and
> client are running 3.0.9
>
> The transfer starts and some files are actually transferred. Once a
> certain file is reached (plain PHP file, no special characters or
> any other peculiarities) it segfaults.
>
> rsync host output:
>
> [sender]
> make_file(<redacted>/libraries/phputf8/mbstring/strlen.php,*,2)
> rsync: connection unexpectedly closed (51261222 bytes received so
> far) [Receiver] rsync error: unexplained error (code 139) at
> io.c(605) [Receiver=3.0.9] [Receiver] _exit_cleanup(code=12,
> file=io.c, line=605): about to call exit(139)
> ----------------------------------------------------------------------------
>
>
rsnapshot encountered an error! The program was invoked with
> these options: /usr/bin/rsnapshot -c \
> /home/remotebackup/hosts/<redacted>/rsnapshot.conf sync
> ----------------------------------------------------------------------------
>
>
ERROR: /usr/bin/rsync returned 139 while processing
> backupuser <at> <redacted>:/backup/
>
> Client output when using gdb to debug the coredump:
>
> warning: no loadable sections found in added symbol-file
> system-supplied DSO at 0x7fff015fd000 Core was generated by
> `/usr/bin/rsync --server --sender -vvvlogDtprRe.Lsf --numeric-ids .
> /backup'. Program terminated with signal 11, Segmentation fault. #0
> 0x00000035cda7b441 in memcpy () from /lib64/libc.so.6
>
> Any help would be greatly appreciated. Please let me know if
> additional info is required to properly debug this issue. -- Best
> regards / Met vriendelijke groet,
>
> Aron Rotteveel -- 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
>
>
>
>

- --
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
        Kevin Korb                      Phone:    (407) 252-6853
        Systems Administrator           Internet:
        FutureQuest, Inc.               Kevin <at> FutureQuest.net  (work)
        Orlando, Florida                kmk <at> sanitarium.net (personal)
        Web page:                       http://www.sanitarium.net/
        PGP public key available on web site.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlUVPe8ACgkQVKC1jlbQAQdJfQCdFpMSsACi2df9P8eJZQAi4qeB
xA8Amwbpj9PGpzeQfrd4VnAytU9dN1uc
=1Ayf
-----END PGP SIGNATURE-----

--

-- 
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
devzero | 19 Mar 20:10 2015
Picon

Aw: Re: rsync 3.0.9 segmentation fault

Hi Aron,
 
i hope it`s ok for you if i bring this back on-list. Your issue and the way or possible fix to resolve it may be interesting for others too (that may include future searches etc)
 
so with 3.1.1 we are a step further....
 
i don`t really have a clue what`s happening here but my next step would be taking a closer look on how the memory usage of rsync on the client and server grows.
 
you could log it like this:
while true;do ps -eo vsz,rss,sz,rsync|grep cron;sleep 10;done >logfile
 
does it grow continuously? does the oom situation reproducibly happen at a certain size ?
what`s the client and server platform?
how many files? (-> https://rsync.samba.org/FAQ.html#5 ! )
 
regards
roland
 
Gesendet: Donnerstag, 19. März 2015 um 12:24 Uhr
Von: "Aron Rotteveel" <rotteveel.aron <at> gmail.com>
An: devzero <at> web.de
Betreff: Re: rsync 3.0.9 segmentation fault
In addition to my last message:
  • Client (sender) has 16GB's or RAM, of which only 6.5GB is used during peak.
  • I tried using --no-inc-recursive, but it does not solve the issue.
What currrently is puzzling me is the question of why I am receiving these errors when my server seems to have plenty of memory to spare.
 
--
Best regards / Met vriendelijke groet,

Aron Rotteveel
 
2015-03-19 11:52 GMT+01:00 Aron Rotteveel <rotteveel.aron <at> gmail.com>:
Hi Roland,
 
I just upgrade both the client and host to 3.1.1 and seem to memory related issues now:
 
ERROR: out of memory in make_file [sender]
rsync error: error allocating core memory buffers (code 22) at util2.c(102) [sender=3.1.1]
[sender] _exit_cleanup(code=22, file=util2.c, line=102): about to call exit(22)
[Receiver] _exit_cleanup(code=22, file=io.c, line=1633): about to call exit(22)
----------------------------------------------------------------------------
rsnapshot encountered an error! The program was invoked with these options:
/usr/bin/rsnapshot -c \
    /home/remotebackup/hosts/<redacted>/rsnapshot.conf sync
----------------------------------------------------------------------------
 
--
Best regards / Met vriendelijke groet,

Aron Rotteveel
 
2015-03-18 23:43 GMT+01:00 <devzero <at> web.de>:
Hi,
 
rsync 3.0.9 is quite ancient, more than 3 years old. A lot of bugs have been fixed since then.
 
Is there a chance to update to the latest rsync version and retry with that ?
 
regards
Roland
 
Gesendet: Dienstag, 17. März 2015 um 11:51 Uhr
Von: "Aron Rotteveel" <rotteveel.aron <at> gmail.com>
An: rsync <at> lists.samba.org
Betreff: rsync 3.0.9 segmentation fault
Hi,
 
I am experiencing segfaults when transferring files via rsync though sudo.
Setup:
 
- Backupserver initiates the rsync command with --delete -vvv --no-inc-recursive --numeric-ids --delete-excluded --relative --rsync-path=/home/backupuser/rsync-wrapper.sh
- rsync-wrapper.sh (on the client) contains /usr/bin/sudo /usr/bin/rsync "$ <at> ";
- user "backupuser" has sudo access to the rsync command
- Both host and client are running 3.0.9
 
The transfer starts and some files are actually transferred. Once a certain file is reached (plain PHP file, no special characters or any other peculiarities) it segfaults.
 
rsync host output:
 
[sender] make_file(<redacted>/libraries/phputf8/mbstring/strlen.php,*,2)
rsync: connection unexpectedly closed (51261222 bytes received so far) [Receiver]
rsync error: unexplained error (code 139) at io.c(605) [Receiver=3.0.9]
[Receiver] _exit_cleanup(code=12, file=io.c, line=605): about to call exit(139)
----------------------------------------------------------------------------
rsnapshot encountered an error! The program was invoked with these options:
/usr/bin/rsnapshot -c \
    /home/remotebackup/hosts/<redacted>/rsnapshot.conf sync
----------------------------------------------------------------------------
ERROR: /usr/bin/rsync returned 139 while processing backupuser <at> <redacted>:/backup/
 
Client output when using gdb to debug the coredump:
 
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff015fd000
Core was generated by `/usr/bin/rsync --server --sender -vvvlogDtprRe.Lsf --numeric-ids . /backup'.
Program terminated with signal 11, Segmentation fault.
#0  0x00000035cda7b441 in memcpy () from /lib64/libc.so.6
 
Any help would be greatly appreciated. Please let me know if additional info is required to properly debug this issue.
--
Best regards / Met vriendelijke groet,

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

-- 
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
Tachuâ„¢ | 19 Mar 17:50 2015
Picon

Rsync Batch mode with multicast

the man pages indicate that batch mode can use multicast 

"Multicast
       transport protocols can be used to transfer the batch update files in parallel to many hosts at once, instead of sending the same data to every host individually.”

I can’t seem to find a reliable example anywhere about using batch mode with multicast. Anyone here has had any success with that?

Thanks

t
--

-- 
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
Aron Rotteveel | 17 Mar 11:51 2015
Picon

rsync 3.0.9 segmentation fault

Hi,

I am experiencing segfaults when transferring files via rsync though sudo.
Setup:

- Backupserver initiates the rsync command with --delete -vvv --no-inc-recursive --numeric-ids --delete-excluded --relative --rsync-path=/home/backupuser/rsync-wrapper.sh
- rsync-wrapper.sh (on the client) contains /usr/bin/sudo /usr/bin/rsync "$ <at> ";
- user "backupuser" has sudo access to the rsync command
- Both host and client are running 3.0.9

The transfer starts and some files are actually transferred. Once a certain file is reached (plain PHP file, no special characters or any other peculiarities) it segfaults.

rsync host output:

[sender] make_file(<redacted>/libraries/phputf8/mbstring/strlen.php,*,2)
rsync: connection unexpectedly closed (51261222 bytes received so far) [Receiver]
rsync error: unexplained error (code 139) at io.c(605) [Receiver=3.0.9]
[Receiver] _exit_cleanup(code=12, file=io.c, line=605): about to call exit(139)
----------------------------------------------------------------------------
rsnapshot encountered an error! The program was invoked with these options:
/usr/bin/rsnapshot -c \
    /home/remotebackup/hosts/<redacted>/rsnapshot.conf sync
----------------------------------------------------------------------------
ERROR: /usr/bin/rsync returned 139 while processing backupuser <at> <redacted>:/backup/

Client output when using gdb to debug the coredump:

warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff015fd000
Core was generated by `/usr/bin/rsync --server --sender -vvvlogDtprRe.Lsf --numeric-ids . /backup'.
Program terminated with signal 11, Segmentation fault.
#0  0x00000035cda7b441 in memcpy () from /lib64/libc.so.6

Any help would be greatly appreciated. Please let me know if additional info is required to properly debug this issue.
--
Best regards / Met vriendelijke groet,

Aron Rotteveel
--

-- 
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 | 16 Mar 17:14 2015
Picon

[Bug 11166] New: running with -vvv causes a hang

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

            Bug ID: 11166
           Summary: running with -vvv causes a hang
           Product: rsync
           Version: 3.1.1
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: pskocik <at> gmail.com
        QA Contact: rsync-qa <at> samba.org

I don't know what might be causing this but when I run rsync with -vvv (my
other options were `-aH --delete  -F -Pi --dry-run -vvv` , the process hangs
somewhere in the middle of my wine's virtual c_drive (I'm running this to
mirror my /home).
It works fine without the -vvv or even with -vv.

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

samba-bugs | 11 Mar 22:12 2015
Picon

[Bug 11161] New: rare crash in hlink.c:536

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

            Bug ID: 11161
           Summary: rare crash in hlink.c:536
           Product: rsync
           Version: 3.1.1
          Hardware: x64
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: sbrabec <at> suse.cz
        QA Contact: rsync-qa <at> samba.org

While calling

/usr/bin/rsync --verbose -e ssh -l -rltzuHAX --delete --force --exclude="*~"
--exclude=feed --exclude="upload" --exclude=spam_statistics.html
~sb/public_html/penguin/public_html/ utx <at> penguin.cz:public_html/

I experienced following abort message during syncing:

rsync: hlink.c:536: finish_hard_link: Assertion `node != ((void *)0) &&
node->data != ((void *)0)' failed.
rsync: [sender] write error: Broken pipe (32)
rsync error: unexplained error (code 255) at io.c(829) [sender=3.1.1]

Local side is openSUSE 13.2 x86_64:

sync  version 3.1.1  protocol version 31
Copyright (C) 1996-2014 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, prealloc, SLP

Remote side is Debian GNU/Linux 6.0:

sync  version 3.0.7  protocol version 30
Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
    64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
    socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
    append, ACLs, xattrs, iconv, symtimes

The bug can not be reproduces. It was never seen before and next call of the
same command succeeded as well.

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

Andrew LaPierre | 11 Mar 14:41 2015

Rsync ACLs over NFSv4 to EXT4 - rsync_xal_set: lsetxattr - Operation not supported

I think this is an NFS or ext4 question, but wanted to post this here for a sanity check. :) I've been searching for over a week for a solution and have turned up nil.

I'm trying to rsync with options -AX over an NFSv4 mount TO an ext4 drive FROM an ext4 drive and both have acl and user_xattr enabled. The command:

    rsync -aAX /data/ /mnt/back/data

results in:

    rsync: rsync_xal_set: lsetxattr(""/mnt/back/data/Users/user/Documents/Desktop"","security.NTACL") failed: Operation not supported (95)

along with all the other files.

Running the same command to a local folder works perfect so I'm assuming it has something to do with NFS4 or EXT4 on the Server side.

My fstab mount:

    UUID=732683f0-e6ac-42d6-a492-e07643d7719c /media/back   ext4    defaults,acl,user_xattr,barrier=1       0       0

My nfs exports file:

    /media/back  10.111.106.3(fsid=0,rw,async,no_root_squash,no_subtree_check)

My mount command:

    mount -t nfs4 -o proto=tcp,port=2049 10.111.106.12:/ /mnt/back

Version info:

Server

    Ubuntu 14.04.2

Client

    Ubuntu 14.04.2
    rsync 3.1.0

Thanks for any suggestions!


--

-- 
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 | 11 Mar 13:41 2015
Picon

[Bug 11152] New: Feature Request: Cache Filelist

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

            Bug ID: 11152
           Summary: Feature Request: Cache Filelist
           Product: rsync
           Version: 3.1.1
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: andrebruce <at> gmail.com
        QA Contact: rsync-qa <at> samba.org

Making it simple:

--cache=FILENAME -> Enable cache. Cache, for the local folder, will be
stored/read from FILENAME

So, with --cache, instead of browsing through local files/folders, rsync would
rely on the cache stored at FILENAME (or, if it doesn't exist, rsync would
generate it)

Without --cache, rsync would ignore reading/generating a cache and just work as
usual.

Mirror and backup servers are wasting a lot of IO when browsing through
files/folders that will just be changed by rsync. Caching would be perfect.
While browsing mailing list and google, I've found some of people looking for
this feature.

Thanks!

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

samba-bugs | 11 Mar 11:41 2015
Picon

[Bug 11151] New: rsync transfers entire source file even when unable to create destination

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

            Bug ID: 11151
           Summary: rsync transfers entire source file even when unable to
                    create destination
           Product: rsync
           Version: 3.0.9
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
          Assignee: wayned <at> samba.org
          Reporter: b.candler <at> pobox.com
        QA Contact: rsync-qa <at> samba.org

[This is with rsync 3.0.9 under Debian Wheezy]

Using the following command to copy a 2TB file:

    rsync -t --progress /file/on/nfs/source /local/dest

The permissions were wrong on /local to create the file, but the whole 2TB was
still read from NFS - hence it took ~6 hours for the command to fail!

The issue is easy to replicate, here with a smaller (4.4GB) file:

$ time rsync /nfs/testfile /etc/dontcare
<< hangs at this point for 16 seconds >>
rsync: mkstemp "/etc/.dontcare.xBvfOf" failed: Permission denied (13)
rsync error: some files/attrs were not transferred (see previous errors) (code
23) at main.c(1070) [sender=3.0.9]

real    0m16.102s
user    0m19.213s
sys    0m7.396s

You can observe the same problem with a local source file (i.e. not involving
NFS), although it needs to be sufficiently large for the problem to be
noticeable.

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

Rob Straughan | 9 Mar 15:00 2015
Picon

Will rsync adopt Kerberos integration?

Hi,

Will rsync adopt Kerberos/GSSAPI integration?  It would be really good if we could establish password-less connections that adhere to user permissions.

I am aware there is a patched version of rsync for this purpose, but it seems to run a few versions behind the main releases.  Are there any plans to incorporate the work done there into the main release? (see http://jrds.fr/rsynck for patch)

At the moment, I am using the following script as a cron job:

--
#!/bin/bash

kinit -k -t /etc/rsync.keytab $1
rsync -aHAXxv --numeric-ids --delete --progress -e "ssh -p $2 -T -c arcfour -o Compression=no -x" $3 $1 <at> $4
kdestroy
--

Where a command might look like:

sudo ./myscript <principal> <port> <source> <host <at> destination>

This works for the purposes of creating a Kerberized connection over which the backup can take place, and will adhere to all user access controls.  The downsides are that the tunnel is encrypted and is slow (terrabytes over gigabit ethernet takes a while), and also requires that the principal's posixAccount have a valid homeDirectory and loginShell to establish the ssh tunnel rather than being a non-interactive service account.

It would be really good if we could use the rsync + rsyncd approach with a connection that can pass user credentials through using an established central security infrastructure.

Regards,
Rob.
--

-- 
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
Robert | 5 Mar 05:06 2015
Picon

Possible Error in rsync 3.0.9

Hi
  I was using rsync with the following options
rsync -aPH --exclude-from=/var/tmp/ignorelist /home/me/ /run/media/me/ADATA\ #2/rsync-me/
and I was creating a copy of a home directory on my Linux machine.  It went along for sometime (some 30,000 files) when it stopped with the following message.
--->
Desktop/OSme/Web-Site-Backups/backup-5.4.2014_15-11-43_linux014.tar.gz 4288446464 78% 32.15MB/s 0:00:36 rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32) rsync: connection unexpectedly closed (1964386 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] [root <at> puter ~]# <---
  I suspect, because the 4,288,446,464 is so close to 2^32 that it is 32 bit limit error of some kind.  It happened twice on the same file.  The version I am using is rsync.x86_64 version on Fedora 21.  It appears that although it says it is a 64 bit version something in the code must be limited by 32 bit values.
  I could be off track here but I don't think so.  I do not know how to raise a Possible Bug Report so I post my concerns here.  Thanks...
Robert
--

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

Gmane