On Tue, Sep 19, 2017 at 10:47 AM, Gandalf Corvotempesta
<gandalf.corvotempe...@gmail.com> wrote:
> 2017-09-19 17:41 GMT+02:00 Les Mikesell <lesmikes...@gmail.com>:
>> If your client rsyncd is configured to write a log file you should be
>> able to see the invocation there. Just guessing, I'd say there is
>> probably something wrong in your excludes and you are wandering into
>> the /sys, /proc, or /dev directories and hanging when you access the
>> contents.
>
> rsyncd is logging, but there isn't any invocation argument.
> Anyway, the same command line (except for the "bpc" custom arguments)
> is used by my
> with rsnapshot and plain "rsync" and i'm able to backup the whole
> server without issues.
>
> Maybe BPC is unable to manage some kind of files that plain rsync is
> able to handle ?
A brute-force approach to debugging would be to start an strace on the
rsyncd client soon after the backup starts and after it hangs try to
figure out the failing operation and hope you have enough scroll back
buffer to find where the relevant file descriptor was opened so you
know what it was.
--
Les Mikesell
lesmikes...@gmail.com
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
