Page 1 of 1

OMV / Docker: Unable to change Temporary and Completed download folders in sabnzbd

Posted: March 11th, 2021, 5:46 pm
by chonger
OMV and docker newbie here. I'm setting up a Raspberry Pi 4 media server. I've set up OMV 5 and got sabnzbd and radarr successfully running in docker using portainer to manage the containers. I'm testing to make sure everything plays nice together so I add a movie to radarr, and radarr searches for it and sab starts to download it. So far so good. Where I'm running into trouble is after the download has been completed. Radarr isn't able to fetch the completed file to move it to my Movies folder. I believe I've narrowed down the problem to Radarr not knowing where to look for the movie. I updated the Remost Host Mappings in Radarr to point to NAS\downloads\complete. On the SAB side, I noticed that my completed download folder is NOT pointed to the same folder. When I go to update this in the SAB folder settings, I get an error that says: "complete_dir directory: /downloads/complete error accessing". Has anyone run into this? Is this a folder permissions thing? If so how do I fix?

Re: Unable to change Temporary and Completed download folders in sabnzbd

Posted: March 12th, 2021, 1:14 am
by sander
chonger wrote: March 11th, 2021, 5:46 pm I get an error that says: "complete_dir directory: /downloads/complete error accessing". Has anyone run into this? Is this a folder permissions thing? If so how do I fix?
Yes, folder permission problem.
For example, when I select "/usr/bin" (which does exist but SAB has no writing rights to), SAB says "complete_dir directory: /usr/bin error accessing"
If so how do I fix?
Choose a folder that SAB has writing rights to. First try "~/Downloads/complete". Only if that works (including downloading), procoeed
As you're in Docker so you must consult what exposed, shared directory you should use. Maybe it's easy as "/complete" ... that depends how you start your docker sabnzbd container.

Re: Unable to change Temporary and Completed download folders in sabnzbd

Posted: March 14th, 2021, 1:20 am
by chonger
Thanks for the response. Here are the volumes I have set up in docker for sab:

Image

If you can't see the image it looks like this:

Host/volume ------------------------> Path in container
/srv/DISKPATH/AppData/sabnzbd-----> /config
/srv/DISKPATH/downloads--------------> /downloads

Note that this is different than the default location for the complete and incomplete folders which is "config/downloads/complete". I'm trying to get it to save to a "Downloads/complete" that I set up and I can't seem to change it.

I've also gone into radarr to try to change the Remote Path Mappings for sab to the current setting (config/downloads/complete) and I'm not able to see that path as an option. Any ideas what might be going on here?

Separately, is there a way, either in docker or directly on my raspberry pi console to just open up all folder access for all clients?

Re: OMV / Docker: Unable to change Temporary and Completed download folders in sabnzbd

Posted: March 14th, 2021, 4:19 am
by sander
This is OMV, Docker and possibly mounting stuff. Nothing SABnzbd specific.
Note that this is different than the default location for the complete and incomplete folders
Indeed. I would advice you to go the default location, and check if that works. First things first.

Re: OMV / Docker: Unable to change Temporary and Completed download folders in sabnzbd

Posted: March 14th, 2021, 1:31 pm
by chonger
Sorry, should have mentioned that I tried the default locations and they do work. I am able to download stuff into those folders but I'm unable to point radarr to look into those folders to move my downloads out of the complete folder into my library. Sounds like I need to post on some more OMV and docker specific forums.

Re: OMV / Docker: Unable to change Temporary and Completed download folders in sabnzbd

Posted: March 14th, 2021, 4:17 pm
by sander
A docker container lives in an isolated, fake world. So if the docker thinks it's "/somedir", it is probably a very different directory on the host system, and only if those container and host directory are connected to eachother by specifying at the moment of docker startup.

For linuxserver sabnzbd, if on the CLI to start the container, you specify

-v /path/to/downloads:/downloads

... it means "connect /path/to/downloads on the host system to /downloads in the docker container".

And then within SABnzbd's GUI you have to specify to save downloads into /downloads.

I find docker great, but with a steep learning curve.