Sonarr + Transmission + Plex on MacOS 10.5 (Catalina)

markus101 · May 7, 2020, 1:00am

if no one was helping I can see trying things, but you had a reply, with the solution.

In download client settings (I said this in my last reply), you took a screenshot of them before too.

Right there at the bottom.

You’re asking for screenshots of things you’ve literally screenshot before, I’m not asking for anything new here. It was definitely not clear to me that you had no idea where they were since A you had already taken a screen shot and B you were off changing other things willy nilly.

pixelrogue · May 7, 2020, 1:13am

Same errors…

UPDATE
New ones also failed

Lets see what happens with this file… you will see the output path as /-data/raw/

rhom · May 7, 2020, 1:27am

sorry, it should have been docker exec -it “containername” bash

the volume mapping for ~MediaCenter/raw:/-data should just be ~MediaCenter/raw:/data, i have no idea what purpose the - in front of data is for (if its some mac specific thing then leave it but it seems odd)

that remote path mapping is probably pointless and you shouldnt need one if you setup the containers properly

lets go back and start with transmission, how have you set that up?

what volume mappings did you setup for it?
what folders did you set as the incomplete and completed dirs?
- (will be in the /config/settings.json file as "download-dir" and "incomplete-dir"

once we have that we can move on to sonarr

pixelrogue · May 7, 2020, 1:46am

pixelrogue@Mac-mini ~ % docker exec -it “sonarr” bash
Error: No such container: “sonarr”
pixelrogue@Mac-mini ~ % docker exec -it “4aebeaba1717” bash 
Error: No such container: “4aebeaba1717”

the volume mapping for ~MediaCenter/raw:/-data should just be ~MediaCenter/raw:/data , i have no idea what purpose the - in front of data is for (if its some mac specific thing then leave it but it seems odd)

Naming from ldexterldesign ~ not sure why he was using dashes so just kept them. Does help separate out the default from the custom. Don’t think that - is the cause of rejected imports. Dash was only introduced from his posts, and the import problem existed before the dash.

that remote path mapping is probably pointless and you shouldnt need one if you setup the containers properly

There was not one set up that way and that was per the recommendation of dexter…he thought it was pretty important and a key for the import rejection.

TRANSMISSION
Download folder is /Uses/pixelrogue/MediaCenter/raw

Complete = raw
Incomplete = not specified (traditionally the same spot as downloads, so raw in this case)

markus101 · May 7, 2020, 2:03am

No, it’s definitely necessary, transmission is on the host, not another docker container. /Users/pixelrogue is not mounted in the container (no should it be).

It sounds like the remote path mapping is almost working, no sense trying to perfect things, let’s get it working first.

If you look at the path in the latest error there is an extra raw in there, either the volume mapping in docker is pointed to the parent of raw (in which case adding raw/ to the remote path mapping should fix it, or the transmission path has an extra raw.

If you change the local path in the remote path mapping to make it /-data/raw/ does it work?

pixelrogue · May 7, 2020, 2:09am

Not following the bit about the extra /raw?
Error is just showing the one raw, right?

Import failed, path does not exist or is not accessible by Sonarr: /-data/raw/Bobs.Burgers.S10E08.1080p.WEB.x264-XLF[rarbg]. Ensure the path exists and the user running Sonarr has the correct permissions to access this file/folder
This is fresh, 10:10pm

markus101 · May 7, 2020, 2:15am

Removing raw/ from the remote path will have the same effect, but if /-data/raw isn’t visible to Sonarr it’s almost certainly a permissions issue (and a good reason not to use your home directory for these apps, especially with docker.

Your screenshot before my previous replt of the remote path mapping showed a /raw at the end of the remote path, but now your most recent one doesn’t, but also your docker mappings showed a /raw on the host side, if it’s mapped to ../rawon the host then account for that in the remote ath mapping’s remote path.

Eventually you’ll also want to make sure transmission downloads to one sub folder and sorted series are in another. You don’t want sorted and unsorted files in the exact same directory.

pixelrogue · May 7, 2020, 2:24am

Permissions have been the suspected reason for these problems.
Many many posts online about MacOS 10.15.4/Catalina and Sonarr problems (both Sonarr for MacOS, and through Docker). Countless hours/days/weeks spent on this, mainly focused on permissions and fruitless efforts to fix.

In my travels, folks are convinced the issue is related to the PUID/PGID or Permissions.

Ok, so saying the URL is combination from those two locations.
On the Sonarr side, I have no options. /-raw is it (short of deleting everything, editing the compose file and rerunning it all again from scratch). Low level of confidence that will change anything. Can’t tell you how many times I’ve set up these docker containers is so many different ways. The most recent as a compose.yml has been the best of the bunch.

docker mappings show a /raw on the host side…
Which screen?
I am not seeing raw doubling up anywhere… not sure where to address this point.

I added an incomplete directory for those files. at the same time the priority is on getting rid of that error so the imports work properly. tweaks and everything can come later. wastes a lot of time on tweaks when someone wanting to help wants to start everything over again from the beginning - so I just let all that go until the error is fixed and reason is known.

Think the Transmission directory set up is now ok? Back to sonarr?

markus101 · May 7, 2020, 2:44am

The typical issues with Sonarr on macOS are due to the lack of full disk access, since you’re running under docker that does not apply, though docker will probably need full disk access (if it doesn’t, I think you posted a screenshot where it already had it). All those other threads you posted are not the exact same issue you’re having and at that time you were having a different issue entirely because you mappings were a mess.

Other permission issues are due to Sonarr and your download client running as different users, which puid and pgid should address.

Something you posted previously, scroll up and you’ll find it.

You posted recently and still had /raw on the end of the remote path if you changed that since I have no way of knowing, but it’s recent enough to assume you didn’t.

At this point I assume either the docker container doesn’t have the correct user ID or group ID assigned or the permissions or they still don’t give you access to the /raw folder. Unless the volume mapping for the container is wrong, because it’s still not clear where /-data points to on the host.

pixelrogue · May 7, 2020, 2:54am

Mappings started off cleaner, and eventually went everywhere, as the more logical mappings were not rendering anything better than the sprawling mappings. Changed from so many different ways, had it set up in shares thinking permissions might have helped there. You name it.

Docker has been granted full folder and full disk write access, as well as the directories which are open to the setting of everyone.

The rejected imports are the same error as when the mappings were cleaner and more direct.

PUID/PGID were updated w/the codes found from the terminal, yet rendering no difference.

Tried to add raw as the one post suggested, but it kicked and error.
This is what I have now:

Everything pointed to -data.

I posted everything showing permissions for Docker, directories. Those have not changed. If you want screen shots of a particular permission setting just let me know.

Haven’t found a single Mac user with this successfully set up on 10.15.4/Catalina.

rhom · May 7, 2020, 7:02am

is there a reason you want transmission running directly on the host but everything else is in docker?

pixelrogue · May 7, 2020, 10:55am

As I understand it, desktop version better for processing power and runs smoother, where inside a vm it hits constraints, hangups and performance issues. Other Mac users insist using desktop version of Transmit.
Note - I have not found a single Mac user on 10.15.4/Catalina successfully running Sonarr/Radarr through Docker. This information is from Mojave, previous macOS.
Personally familiar and preference as I have been using that app for year.

That said, if adding a file manage insider docker would solve these problems that is one experiment that has not been tried. Also, the errors are from a file import from Sonarr where Sonarr does not recognize and/or have access to the given directory. Doubtful a file dowloaded from within Docker would improve either of those situations.

rhom · May 7, 2020, 1:42pm

sonar is saying it either cannot see, or cannot access the folders/files. youre saying you have sonarr setup correctly to remote map the host path transmission gives into a proper path inside the container so sonarr should be able to see, but its complaining that it cannot

have you confirmed you can see that path, and the files within it, manually via bash from inside the sonarr container?

the docker variants are all running with the same privileges, the only thing different is transmission running directly on the host.

whether theres a docker issue with macos or something else you have potential privilege differences somewhere so making all the apps run in exactly the same way is a good test to rule out a docker/host access issue.

if there is some underlying issue with docker on macos then youre probably screwed either way. which may be the case as i’ve never seen docker have this many issues before.

pixelrogue · May 7, 2020, 2:52pm

Based on previous tutorials followed, it would look like everything has been set up correctly per the given tutorial. Tutorials/approaches varied, yet the import error persisted. Everything was cleaned out and started over from scratch Tuesday evening.
There was a second error which was resolved when switching to docker compose approach (yea!). Many have provided help, each a clear perspective on what was wrong and how to get the situation resolved. As of today, sonarr import errors remain.

If paths are correct or not, no idea either way. I think so, but can not confirmed w/certainly.
Expect they were certainly correct at some point just based on the variations tried.

Sonarr can see the transmission files. Sonarr appears to when when the file has been completed, knows to go process the file and then hits that error. That is how it seems to me. Is there a way to determine what the proper path inside the container is, or should be to fix?

Confirming the path and seeing the files through bash:

root@642c9804b44b:/# dir
app bin boot config -data defaults dev docker-mods donate.txt etc home init lib lib64 libexec media mnt opt proc root run sbin srv sys tmp usr var

root@642c9804b44b:/# cd /-data
root@642c9804b44b:/-data# dir
Bob's\ Burgers				      Bobs.Burgers.S10E07.1080p.WEB.x264-TBS[TGx]	Bobs.Burgers.Series			     Family.Guy.S18E09.1080p.WEB.x264-XLF[TGx]				      x.incomplete
Bobs.Burgers.S10E01.1080p.WEB.x264-TBS[ettv]  Bobs.Burgers.S10E08.1080p.WEB.x264-XLF[rarbg]	FamilyGuy				     Family.Guy.S18E10.1080p.WEB.x264-TBS[TGx]
Bobs.Burgers.S10E02.1080p.WEB.x264-TBS[TGx]   Bobs.Burgers.S10E09.REAL.1080p.WEB.x264-TBS[TGx]	Family.Guy.S18E08.1080p.WEB.x264-XLF[rarbg]  Family.Guy.S18E11.Short.Cuts.1080p.HULU.WEB-DL.DD+5.1.H.264-CtrlHD[TGx]

To me, that looks like Sonarr path is correct and Sonarr can see the files.

Everything is now running as a single container inside Docker. Same permissions on each.
PUID/GPID were at defaults of 1000, and now at what the terminal exposes as PUID=501, and PGUID=20. No difference in end result, same error and same error code.

You will see all the permissions opened in an earlier post in this thread (screen shots) showing access to directories, as well as access to systems.

Docker is only having ONE issue.
The majority of this thread has been looking for ways to get this one import error fixed.
Haven’t yet seen anyone posting about getting Sonarr/Docker working on MacOS 10.15.4/Catalina.
Have seen tons of posts related to the same error code (failed import) ~ and the reasons all varied. All on difference systems, all w/different reasons. Some solved and many seems unresolved.

People disagree with this thought ~ I am of the mindset that what ever problem sonarr/docker has with importing files is related to the problems of people are experiencing w/Sonarr for macOS.
Different origins, different approaches and even different permissions and I think all the same, there will be a common issue discovered that impacts both.

Happy to do a zoom screen share w/anyone. They can direct me and see the files, paths etc. real time. Confirm everything is/is not properly set up, permission etc.

rhom · May 8, 2020, 12:12am

from a sonarr perspective it appears that transmission is putting completed files into /-data (or ~/MediaCenter/raw from the host) which is not something you want to do so were going to split them apart. never mix downloading and permanent content under the same folder.

change the volume mapping on the sonarr container from ~/MediaCenter/raw:/-data to ~/MediaCenter:/-data and delete/recreate the container

in sonarr, edit the download client entry for transmission and set the category to sonarr (this will stop sonarr from potentially mucking around with radarr and manual transmission downloads)

go to settings > download clients and down at the bottom edit the remote path mapping;
change the remote path to ~/MediaCenter/ and the local path to /-data/

im presuming that /-data/sonarr (~/MediaCenter/sonarr on the host) is meant to be where all your series folders are meant to go.

go to settings > media management and down at the bottom if /-data/sonarr is not listed as a root folder there, then add it.

go to series > mass editor and select everything (the tick box right at the top of the list), click on the root path dropdown and select /-data/sonarr as their new root path - then click on “no, ill move them myself” (im presuming no files have been added to sonarr yet as the import isnt working so theres nothing to move)

now try downloading something

note - if import still does not work check the folder name it cannot see. if its the full expanded version of ~ (the home path) then you will need to edit the remote path mapping an set the remote path to /Users/pixelrogue/MediaCenter/ instead. (basically whatever is in the sonarr logs - and its case sensitive so copy/paste it from the log).

then try downloading again

if it still fails after that please enable trace level logging, download something else, then disable trace level logging. attach the trace log somewhere and link it (do not paste it inline)

pixelrogue · May 8, 2020, 1:19am

Appreciate the patience, and the added detail of this post which is helping.

Currently at this step:

note - if import still does not work check the folder name it cannot see. if its the full expanded version of ~ (the home path) then you will need to edit the remote path mapping an set the remote path to /Users/pixelrogue/MediaCenter/ instead. (basically whatever is in the sonarr logs - and its case sensitive so copy/paste it from the log).

I have a directory for incomplete downloads open, one for complete downloads open and the sonarr directory open. Files have been successfully going from sonarr request > transmission > incomplete directory > complete directory.

FOR THE FIRST TIME I AM SEEING FILES MOVING INTO THE sonarr DIRECTORY!!
. . . .

THIS IS GREAT!!!
I OWE YOU GUYS A WELL DESERVED BEER!

(and, as others have mentioned, user error totally on my side as these settings are working!!)

OK. I rest easy tonight and will get back to this tomorrow to clean up all the experiments, make backups and document the settings. This is amazing…!!

Remaining:

getting jellyfin to composer.yml (and likely CouchPotato)
remote access to sonarr/radarr while vpn in place (overall vpn)

system · July 7, 2020, 1:19am

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.