#NZBGET CREATED FILE PERMISSIONS CODE#
#NZBGET CREATED FILE PERMISSIONS DOWNLOAD#

SSH into OMV as root and fetch group and user IDs (id or id ) and make a note Create the necessary folders on my /srv/disk target and then 'chown user:media folder' (persistent storage volume) Also, chmod 00775 to make sure the created group (media) has permissions on your media folder In OMV, create a group (media) create a user for each container (sabnzbd, sonarr, radarr) Make those users members of the created group (as well as the default users group) What are the differences in an 'ls -l' (lower Letter L) on the directory when it works, and when it doesnt? Has anyone experienced anything like this, or have a guess where the problem is coming from? I'm not very familiar with Unix permissions, but I can't figure why it would be fixed for 24-72 hours only to have it come back later. I have NZBGet using umask 002, sonarr and radarr running chmods in their settings (775), and I've run the above chmods/chgrp in both the /sharedfolders/ and srv/dev-disk-by-label to try to fix the issue. I usually run chmod g+s /directory for the parent directory as well. I can run chgrp -R users /directory and chmod -R g+w /directory for a temporary fix.

#NZBGET CREATED FILE PERMISSIONS CODE#

The shared folder is on a RAID array.Įvery few days, NZBGet starts failing it's unpacks with error code 9: permission denied when trying to create the directory. They all have read/write permission as a user and group in the shared folder.

They share a download/media folder which is a set up as a shared folder in OMV. They are using different users, but all with the default group 'users'. I have sonarr/radarr as well as transmission all running in Docker as well. i've just had to take the shared folder and give permissions to the users group, then it works.I keep having permissions issues while unpacking archives using NZBGet in Docker. Users ❌100:couchpotatoserver,nzbdrone,nzbget,sickbeardĪnd it does.

#NZBGET CREATED FILE PERMISSIONS DOWNLOAD#

Kinda out of ideas whats wrong, usually i solve it with a usergroup that owns the download folders but theres no group or user cli utilites when ssh into the nas.Īnyway i guess theres a good way of doing it i just cant figure it out now after alot of hours messing with other issues getting the packages. doesnt work.Īlso chmodded that dir to 777 just to make it writeable but still nzbget cant write or access the basedir or the tmp, inter, queue or nzb subdirs that i also created later after testing the 777 chmod. Made a shared folder 'Downloads' and nzbget doesnt seem to have permission to write to that folder, not sure how systemusers permissions usually looks on synologys but just for testing ive made /volume1/Downloads/nzbget and changed owner to nzbget that is the systemuser that runs nzbget. I've config it so /volume1/Downloads/nzbget is the basedir.īut i get 'Error saving diskstate: Could not create file /volume1/Downloads/nzbget/queue/stats.new'

This time its my DS214+ im trying to setup as my regular nas is down due to hardware failure.Īnyway i got nzbget installed manually via spk file, got nzbget up and running. Nzbget usually is a piece of cake to setup on debian/ubuntu/centos and what ever other linux flavour i tried. So far im at setting up nzbget, and i just dont get it. I've used the dev-branch and compiled nzbget, python, mono and nzbdrone.

Nzbget created file permissions