RSync Task receives permission error when Task is 'Run Now' but no permission errors when Task is run according to schedule.
I have a Rsync task configured for Module Mode that is syncing all data to an older Synology NAS Box.
The data I am trying to sync is 4 CIFS shares. 2 of the 4 shares I have removed the 'Everyone' group from access by adjusting this from Windows as the documentation suggests.
The rsync task is configured to use a user 'rsync' that has been assigned the same groups as the 4 shares in the task.
Of the 4 shares I am having an issue with just the 2 shares that I have removed the 'Everyone' group from, but only when using the 'Run Now' option.
When using the 'Run Now' option, the task reports a permission error as seen in the screenshots attached.
If the same task is allowed to run from the assigned schedule which I had set-up to run at 11:03 P.M. just to demonstrate this issue, the rsync task can run and back up all 4 directories with no issues.
Is there a difference in how the task is run or users involved with using the 'Run Now' button vs. the scheduled method that would account for this difference in behavior?
Also as a side note my first version of this task was to attempt to do this rsync over ssh on Port 22. After switching back to module mode the Port Number is still displayed in the GUI. Not a big deal but can be a little misleading since we are not technically using 22 anymore. This is also in the screenshot.
I do also have extra parameters in this rsync task that I will include in the screenshot as well, I do not believe these are the issue though as the Task runs fine when ran according to schedule. Issue only presents itself when the 'Run Now' button is used.
#8 Updated by Benjamin Gilles over 5 years ago
- File RsyncConfig.jpg RsyncConfig.jpg added
- File RsyncFreeNASPerms.jpg RsyncFreeNASPerms.jpg added
- File SynologyModuleConfig.jpg SynologyModuleConfig.jpg added
- File SynologyFolderPerms.jpg SynologyFolderPerms.jpg added
Sure here are the screenshots of the configuration. I also just tested this to make sure it is still occurring and it is on the latest 9.3 stable. As stated in the word document the only shares that have a problem it seems are CIFS Shares that have had the Everyone group removed from access. This does not affect the sync though when the task is run via the schedule, only when using the 'Run Now' option. As the process has no permission errors when run via the scheduled time, only when using the Run Now option, I still think there is a difference between how the process is started and exists somewhere on the FreeNAS side not on the Synology.
User on Both Sides is user 'rsync'
Permissions for rsync user on FreeNAS side:
This is the rsync module that is being used from /etc/rsyncd.conf
This is the Directory Permissions on the Synology Side:
The rsync user on the synology side is a member of group 'users' and 'rsync' and has full read/write access to the rsync share.
#10 Updated by Benjamin Gilles over 5 years ago
I can confirm that I am no longer receiving the permission errors when using the 'Run Now' button, but I also did not have any modified data in these directories to sync since the last sync, but the permission errors would always occur regardless so I believe that issue is resolved. I will create some data to sync and test it further this evening when I get home.
Also the Port 22 is no longer displayed in the UI when using Module Mode.
I didn't see this specifically noted in the patch notes when I installed them. The patch version I am on is FreeNAS-9.3-STABLE-2015060162331.
Was there something included to specifically address this and I am curious what the fix was.
#11 Updated by William Grzybowski over 5 years ago
- Status changed from Screened to Resolved
Yes, this was addressed in this ticket as well but it didn't make to the changelog as I wanted to make sure the issue was resolved before closing the ticket.
Feel free to reopen this if you see the issues again.