›

rsync channel blocked

ssk2
in Acrosync for Windows
Was wondering if anyone has any tips to debug this issue? Does this imply a network issue? I'm able to reach the remote server just fine via ssh, rsync is installed and I'm able to log in fine with the same credentials. This was working perfectly until a few weeks ago and since then I've seen a message like the below every time:
2015/05/25 08:34:59    Acrosync for windows 1.3 build 462 initialized
2015/05/25 08:39:23    The rsync channel has been blocked for more than 120 seconds (read:0:0:3:1:1:1:0:64000:3:64000:0:0:0:1)

Trying again with the log verbosity turned up yields:
2015/05/25 21:56:31    Uploading D:/Personal/ to /c/backup/Personal/
2015/05/25 21:56:35    rsync command: rsync --server --modify-window=2 --out-format=%n --links --recursive --delete-during -tude. . /c/backup/Personal/
2015/05/25 21:56:35    Add pattern: - /.acrosync/
2015/05/25 21:57:06    Uploading ./
2015/05/25 21:59:07    The rsync channel has been blocked for more than 120 seconds (read:0:0:3:1:1:1:0:64000:3:64000:0:0:0:1)

Any suggestions as to what else I should check?

Comments

  • gchen
    Is your server a linux machine or a NAS?  sometimes a reboot of the server may help.
  • ssk2
    Apologies for the slow reply @gchen. Restarting seems to help! However after a few days, it fails to work again. Is there a reason this happens? I've used Deltacopy in the past with the same NAS for months and didn't have the same issue.

    It's a NAS running Linux:
    SS:/var/log# uname -a
    Linux SS 2.6.17.14ReadyNAS #1 Wed Jun 20 20:08:20 PDT 2012 padre unknown

    I've upgraded to 1.4 and the issue remains.
  • ssk2
    I suspect this isn't terminating in the correct way. Once the current backup finishes, I'll try again and see what happens. There's nothing obvious in the sshd or the rsync logs:
    2013/06/30 20:27:51 [3126] rsyncd version 3.0.9 starting, listening on port 873
    2013/06/30 22:02:24 [3126] rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(551) [Receiver=3.0.9]
    2015/05/22 02:33:33 [13175] rsyncd version 3.0.9 starting, listening on port 873
    2015/08/29 18:29:28 [1157] rsyncd version 3.0.9 starting, listening on port 873

    Is there a way of passing through the --log-file property to the remote rsync command to get more log output locally?
  • gchen
    A new version is available in which the timeout value is increased to 600 seconds.  The reason for this change is that it may be possible for the network traffic to stall for a while before it gets going again under certain conditions, but I haven't been able to reproduce it myself.

  • ssk2
    Thanks, trying this now!
  • ssk2
    Seems to be working! Looks like it needed just over 120 seconds... I'll continue to try it this week and report back if it fails.

    2015/09/05 10:59:16    Acrosync for windows 1.5 build 508 initialized
    2015/09/05 10:59:24    Uploading D:/Personal/ to /c/backup/Personal/
    2015/09/05 10:59:28    rsync command: rsync --server --modify-window=2 --out-format=%n --links --recursive --delete-during -tude. . /c/backup/Personal/
    2015/09/05 10:59:28    Add pattern: - /.acrosync/
    2015/09/05 10:59:51    Uploading ./
    2015/09/05 11:01:59    Uploading Photos/Incoming/DCIM/Camera/IMG_20140511_224200:nopm:.jpg
  • ssk2
    Working a charm over multiple backups. Thanks for the help @gchen!
  • Germo GörtzGermo Görtz
    Is is possible to make this 120 or 600 seconds as an option the user can set? Also the 600 is not enough for me and most sync operations are interrupted because of the 600 second limit.
  • gchen
    Starting from version 1.5, you add a registry entry 'TransmissionTimeout' under HKCU/Software/Acrosync/AcrosyncClient to set the number of seconds Acrosync will wait before reporting this error.
Sign In or Register to comment.