Clarifications on getting debug information when rsync freezes

Hi I am having a problem with rsync freezing and I would like to collect the proper information while the problem happens. However, I would like to ask some clarifications. rsync-debug === I see references of using rsync-debug but I cannot figure out how to use it *while* the rsync

rsync got stuck

Hi I rsync from 4 machines to a single destination one, and I am certain the filenames they sync do not overlap. But from time to time rsync from a source machine gets stuck (not always the same source machine). I followed https://rsync.samba.org/issues.html and I gathered strace, lsof and

rename error on temporary destination file

Hi I am seeing from time to time the following error: rsync: rename "/DEST_DIR/SUB_DIR/.A_FILE.AzmlvG" -> "SUB_DIR/.tmp/A_FILE.xml.gz": No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1183) I rsync from a few source

Re: rsync got stuck

On 08/30/2017 05:39 PM, Paul Slootman wrote: > On Wed 23 Aug 2017, Vangelis Katsikaros via rsync wrote: > >> abc 3797 3796 0 01:12 ?00:03:14 /usr/bin/rsync --compress >> --compress-level=9 --bwlimit=512k --recursive --delay-updates --quiet >> --update

Should I worry about the "vanished files" warning?

Hi I would like to ask, when the "vanished files" warning is a sign that something bad is happening somewhere. I know that the `rsync-no-vanished` script can silence the warning, but I am wondering whether this is a sane thing to do. My guess based on

Re: Should I worry about the "vanished files" warning?

nd decide if it is a problem or not. > > On 09/07/2017 10:27 AM, Vangelis Katsikaros via rsync wrote: >> Hi >> >> I would like to ask, when the "vanished files" warning is a sign that >> something bad is happening somewhere. I know that the `rsync-no-vanis