Since the version 2.3.3 is now available in the Package Center an old problem seems to be back whenever SAB is started on my Synology:
"Cannot change permissions of /volume1/Usenet/incomplete" is annoying me again
Of course I changed the permissions as described in https://github.com/SynoCommunity/spksrc ... Management
I even gave "sc-download" the ownership of that folder - but as soon as I restart my Synology (which is hapening every day, as it is not 24/7 running) it is always back to "admin" as owner of that folder and therefore the message in SAB is showing up again.
The problem was totally gone during my SAB on Docker experience... where am I making a misstake?
an old problem is back on Synology
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
-
- Newbie
- Posts: 47
- Joined: April 24th, 2017, 8:51 am
Re: an old problem is back on Synology
You will have to ask over at SynCommunity support:
https://github.com/SynoCommunity/spksrc/issues
What I can say is that usually you have to make sure the whole share is set to "Use Windows ACL" and that you make sure to set the permissions changes to propagate to children etc.
https://github.com/SynoCommunity/spksrc/issues
What I can say is that usually you have to make sure the whole share is set to "Use Windows ACL" and that you make sure to set the permissions changes to propagate to children etc.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
-
- Newbie
- Posts: 47
- Joined: April 24th, 2017, 8:51 am
Re: an old problem is back on Synology
As far as I understand the Windows ACL thing is only relevant for folders that have been created before DSM 5, so that does not apply for my situation.
I have another idea that I want to try and I will report about it later that day if it was a success
I have another idea that I want to try and I will report about it later that day if it was a success
-
- Newbie
- Posts: 47
- Joined: April 24th, 2017, 8:51 am
Re: an old problem is back on Synology
Haha, it seems as if my new plan is working
I deleted the incomplete folder so that SAB was recreating it by itself a moment later and now - after a restart of my Synology - there is no silly error message showing up Hopefully it will stay that way...
I deleted the incomplete folder so that SAB was recreating it by itself a moment later and now - after a restart of my Synology - there is no silly error message showing up Hopefully it will stay that way...
Re: an old problem is back on Synology
Good to know!
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate