problems to connect to a NAS Server using Acrosync for Windows (rsync channel has been blocked)

I am not able to browse the remote directory on a Synology NAS using the small button with a networked folder icon.
Windows 8.1, 64 bit
But I am able to connect to my NAS using for example QtdSync
the user is rsync in both cases
the server I tried the IP address (192.168.178.26) and also the name (Diskstation)

2014/09/14 21:41:09    Acrosync for windows 0.92 build 370(unofficial) initialized
--this happens when "over SSH" is activated:
2014/09/14 21:43:00    ERROR: module is write only 
2014/09/14 21:45:21    ERROR: module is write only 
2014/09/14 21:45:42    ERROR: module is write only 
2014/09/14 21:46:36    ERROR: module is write only 
2014/09/14 21:46:53    ERROR: module is write only 

--this happens with "over SSH" deactivated
2014/09/14 21:50:13    The rsync channel has been blocked for more than 120 seconds (readAll:-1:0:0:0:0:64000:0:64000:0:0:0:1)
2014/09/14 21:52:50    The rsync channel has been blocked for more than 120 seconds (readAll:-1:0:0:0:0:64000:0:64000:0:0:0:1)

--this I tried because it works in QtdSync as server, but it doesn't work for acrosync
2014/09/14 21:53:07    Failed to resolve the host 'rsync://192.168.178.26': 11001
2014/09/14 21:53:21    Failed to resolve the host 'rsync://192.168.178.26': 11001

--trying only the server address again:
2014/09/14 21:55:58    The rsync channel has been blocked for more than 120 seconds (readAll:-1:0:0:0:0:64000:0:64000:0:0:0:1)
2014/09/14 22:00:49    The rsync channel has been blocked for more than 120 seconds (readAll:-1:0:0:0:0:64000:0:64000:0:0:0:1)

then I tried to enter AcrosyncTest as remote directory as in the instructions screenshot. I can start now, but nothing happens:
and after 120 sec I get the same error:
2014/09/14 22:20:23    Uploading D:/Acrosync test/ to AcrosyncTest/
2014/09/14 22:20:23    rsync command: rsync --server --modify-window=2 --out-format=%n --links --recursive -tude. . "AcrosyncTest/"
2014/09/14 22:22:24    The rsync channel has been blocked for more than 120 seconds (readAll:-1:0:0:0:0:64000:0:64000:0:0:0:1)

Comments

  • It looks like that Synology NAS is running a modified version of rsync as the "module is write only" error can only appear in the daemon mode.

    Can you try using root/admin as the username with "over SSH" activated to see if the issue was caused by permissions?

    I own a QNAP TS-212 with which Acrosync works really well (except that I have to log in as 'admin' for the 'over ssh' mode).  I'm going to order a Synology to see how it is different from QNAP.
  • user root with the admin password and SSH can connect.
    But there are no remote folders shown in the remote directory browser.
    So I enter the folder (for example AcrosyncTest) manually. The log is showing that the backup was running. Now I can browse the folder "AcrosyncTest" on the NAS, so it seams to be there. And my backup is on the server.

    But I am not able to find the files on the Synology diskstation. The user root can't be used to login via web interface. And logged in with a different user I can't find where the files are stored.
  • Install the latest version 0.93 if you haven't done so.  With 0.93 you should be able to enter '/' in the remote directory text field (or anything that begins with '/'), and then click on the browse button.  It will then start from the root directory rather than the home directory.
  • I finally received my synology DS214se running DSM 5.0-4493.  Yes, there is a bug in the connection code in Acrosync that prevents it from connecting to the rsync daemon. After fixing this bug, I was able to sync with a shared directory using a non-root user account in the rsync daemon mode.

    To made it work I had to 1) manually modified /etc/rsync.secrets to add the rsync password in plaintext and 2) chown the shared directory to that user (otherwise rsync would fail to update timestamps for all files).  Did you do the same to make it work with QtdSync?

    The ssh mode still gives me the annoying "module is write only" error, unless I login with 'root' and then start browsing from '/', which I guess not many users will like.

    The new version with the fix will be available early next week, as I'm just finished adding a scheduler and need a few days to test this new feature.  

  • I did not modify anything on the synology to get QtdSync work. My problem with QtdSync is, that I am not able to finish a backup of my whole PC sucessfull. And also areca-backup I was not able to et running on my 64 bit win 8.1 system. Thats why I am looking for other programs and found Acrosync.

    Now I downloaded version 0.93. The remote folder browser works fine now. I am able to browse the the folder which I wan't to use for my backup. This folder works fine for testing and I can see the backup also with other users logged into Synology. For example
    //volume1/NetBackup/AcrosyncTest/UploadHourly

    But what is strange: When I used the "New profile" the browser worked as in version 0.92
    Maybe I have to reboot my system what I will do now. I updated to version 0.93 only in the current windows session.

    What should be fixed by the new version next week? The issue when using a different user? If root works for now this is fine for me. 

    I will try to make a backup of my whole notebook and if this will work then acrosync will be the program I will use - and buy of course :-)
  • same issue after rebooting: sometimes I can browse all remote folders, sometimes I can browse only folders which have been created doing a sync with acrosync before. Anyway now I know the syntax and can manually enter the remote folder.
  • Version 0.94 will allow you to connect to the NAS using the rsync daemon mode, i.e., with 'Over SSH' unchecked.

    If you're fine with the root login then the ssh mode is recommended.  To allow easy browsing, you can create symlinks under your root home directory that link to those subdirectories under /volume.  For example:

    ssh root@<NAS ip>

    ln -s /volume1/NetBackup

    The reason why sometimes browsing works but not always is that the starting remote directory depends on what you enter in the remote directory text field.  If that starts with a '/', then it will start from the root directory.  Otherwise, it will start from the home directory, which is by default empty if you haven't created those symlinks.

Sign In or Register to comment.