Sonarr version (exact version): 4.0.0.356 Mono version (if Sonarr is not running on Windows): 4.0.0.356-ls389 by linuxserver.io OS: Docker Description of issue:
Maybe I’m not fully grasping the concepts of Sonarr and not using it to its full potential.
From what I can understand, Sonarr and the like were created with the intent that a seedbox was not part of the equation. The torrent client would be run on the same system as Sonarr, and Sonarr could see when they were finished and move the file locally when done. Correct me if I am wrong on that. I used to use Sonarr on my seedbox directly but found that it was not updated regularly, and it was duplicating DLs on the drive, which was a headache. So I’ve moved to a Sonarr docker on my Unraid box.
But since I use a seedbox, my system operates a little differently. My process currently runs like this;
Sonarr grabs a torrent from an indexer and sends it to rTorrent
rTorrent DLs and manages which need to be seeded depending on private/public servers
When rTorrent has finished downloading, it hot-links to a ‘sync’ folder
Seedsync (a local Docker container app on Unraid) watches for new files in that ‘sync’ folder on the seedbox. When it sees a new file, it starts an LFTP session and downloads to a local DIR.
I then sort TV and movies in the local DIR and run filebot.
Processed TV and movies are moved into the DIRs that Kodi and Plex access.
The problem I think is with how the media management config works, TV show folders are being created where I don’t want them, and I can’t find any way of stopping it. Every now and then, I have to go through a clear out the stuff I don’t want, which defeats the purpose of automation.
I guess I am looking for either advice on how to integrate Sonarr into this process or the ability to disable Sonarr from creating all these folders automatically. One option that would work is that once an episode has been sent to the download client and successfully completed, it should be marked as unmonitored.
My ROOT folder in media management is defined as the location where all DVR files are located (tv shows specifically. I have a separate folder for movies).
The original downloads are removed by rTorrent almost immediately as these are from a public server that I cannot seed to. Once the torrent download is finished, the files are moved to the sync folder. It seems that once those original files are deleted, Sonarr doesn’t know what to do from there, and nothing further happens.
I have a TV show sitting in the local “/ssync/1-Incoming” folder, which matches the files on the remote seedbox in the “/files/11-sync” folder.
Sonarr doesn’t seem to know it needs to do anything to rename and move the files in “/ssync/1-Incoming” to the ROOT folder in the media management settings.
I have confirmed via the container’s console that I can read/write to both DIRs
You shouldn’t need or have anything 3rd party moving files or syncing files after download. As soon as you do, sonarr doesn’t know what is going on, as you have discovered.
Sonarr instructs download client to download something.
Download client does so into the location set in the download client.
Sonarr then processes the file from the download location into your root folder. Remote path mapping is what enables this to happen. You need to have mounted, mapped or otherwise linked your local Sonarr docker to your remote download folder to be able to complete the Remote Path Mapping https://trash-guides.info/Sonarr/Sonarr-remote-path-mapping/#local-path
So I need to have something to sync files across the internet. The seedbox is in the Netherlands and I’m in another country altogether. I use Seedsync as with lftp I can fully utilize my total bandwidth with 20 SFTP threads. I’ve tried syncthing and resilio and they were both slow as molasses.
Also, I download stuff other than TV shows and movies on the seedbox so disabling rtorrents auto-move feature would break any automation that isn’t triggered by sonarr or radarr.
I’m sure I’m not the only one that uses a remote seedbox and syncs files to a local store.
Something else could be if your Incoming folder doesn’t have the matching subfolder per whatever category you assigned to the download client. It’s how sonarr distinguishes what files it should manage.
