I’m trying to get an optimal set up to download in deluge, use deluge’s extractor plugin, and then have sonarr move the extracted file in place, but have deluge leave all the original files in place for seeding.
Almost all of that is working perfectly except for two things. Sonarr seems to copy and not move the extracted file and either Sonarr or Deluge is deleting the archived files after extraction, causing seeding to die.
Anyone have a similar setup that can give some advice? Thanks.
Find it hard to believe that Deluge is deleting after extraction. The problem with the Deluge extractor it puts all the files in one place. You should run a custom script to extract in the same folder as the torrent, that way sonarr can use cdh to handle the import, in cdh sonarr will copy or hardlink. The first one will leave you with 3 copies not ideal, hardlink will not use space, so only two copies, the rared one and the actual imported video file.
If the hardlink left over file still bothers, you can use a custom processing script in sonarr to clean the source video file in case it comes from an extracted rar source.
I am having the same issue. My setup is I have a seperate hard drive just for active Torrent files and keep my media on a separate FlexRAID storage. I need to make a copy of the file because FlexRAID has pretty slow read/write speeds and I don’t want my torrenting affecting my ability to watch my shows. So I currently have the extractor plugin in deluge extracting files to another folder called “Extracted” on my torrenting harddrive. I have Sonarr monitoring the “Extracted” folder. My thinking being that then every once in while I would delete the extracted folder. Everything seems to work except the problem is that something is deleting the original RAR file. So my seeding stops saying file is missing and my ratios are taking a beating. Can someone help? Any suggestions? Thanks.
This sounds like my issue as well.
So, I turned off all plugins in Deluge and downloaded a archived format show from sonarr. Sonarr must have unarchived the show, deleted the original files, and then copied the extracted file to where I store my TV shows. What part of Sonarr is doing the unarchive and delete?
Sonarr won’t delete a folder that has RARed content or a valid video file directly.
If you have Remove Completed Downloads enabled and Deluge tells Sonarr the download has finished seeding then it will tell the download client to remove the download (and its files).
Sonarr has no method to extract files.
This is not what is happening. Remove Completed Downloads is disabled. Deluge is keeping the download in the queue, but because it has missing files it can no longer seed.
Exactly the same as my issue.
Are you using the drone Factory folder in the same place you place your downloads?
I am not using a drone factory folder. But if I was, where in relation to my downloads should it be stored?
deluge downloads to /downloads/
moves completed downloads to /downloads/sonarr_complete/
extractor extracts to /downloads/sonarr_complete/ with torrent name sub-folder selected
That is my current set up
This is my Folder Structure of my T: Drive
Here are my Deluge settings
Download to:
T:\Currently Downloading
Move Completed Torrents to:
T:\Completed
Copy of .torrent files to:
T:\Torrent Files
Autoadd .torrent files from:
T:\Auto Add - Blackhole
Here are my Sonarr Settings
Completed Download Handling
Failed Download Handling
Drone Factory
It shouldn’t, is not recommended at all.
Your setup should work, CDH should see the file extracted which inside the same folder deluge is reporting back to track, then proceeding to import (copy or hardlink the video extracted file)
Sonarr does copy, in your case it will be the extracted video file unless you choose hardlink, which is only possible if the target destination is in the same filesystem.
Sonarr doesn’t move, unless is using drone factory or torrent blackhole.
I suggest you enable debug/trace logs in sonarr as well as inspect the deluge logs to see what’s going on. Sonarr is not aware of rar files, but it can delete torrents if the option is enabled and the seeding has stopped in deluge
“399e038e8a516db5203681db5a11099c89a8e9ce”: {“active_time”: 2313, “total_done”: 1036611328, “ratio”: 0.0, “name”: “Arrow.S04E11.720p.HDTV.X264-DIMENSION”, “time_added”: 1455889280.0, “total_size”: 1036611328, “is_auto_managed”: true, “stop_ratio”: 10.0, “stop_at_ratio”: true, “state”: “Seeding”, “remove_at_ratio”: false, “save_path”: “/downloads/sonarr_complete”, “progress”: 100.0, “eta”: 0, “hash”: “399e038e8a516db5203681db5a11099c89a8e9ce”, “message”: “OK”, “is_finished”: true}
It seems that from the trace logs in sonarr, it still states the torrent is “seeding”. But there is nowhere in the logs I can see anything about removing a torrent because it is complete.
What I’m going to try now is loading into Deluge an archived torrent NOT from sonarr and see how it handles the extract and seeding process.
We’re you able to figure out a fix? I am still having issues.
I reinstalled the docker I was running Deluge in.
I have been able to conclude that the issue is definitely with Deluge and not sonarr as it occurs even when Sonarr is shutdown and not scanning anything.
I have had a few downloads go through since reinstalling without removing any files, but I have a feeling it has to do with the “auto-manage” torrent feature. When disabled, I don’t think this issue occurs. But I’m not sure if there is a way to default with the feature of for all new torrents.
It seems like it is removing the files (.r01, .r02, etc.) and replacing them with .fuse_hidden files like .fuse_hidden00001c5500000940 one for each removed archive file.
Not sure if you’re suggesting that Sonarr is doing that, but its not. Sounds like something else is altering them.
Those are intent to delete files by a fuse mount point when they are in use, in their native filesystem.
Are you using sshfs, curlftpfs or ntfs-3g?
You mentioned deluge is in docker container, how is sonarr getting access to the deluge container data?
Sonarr and Deluge are both running in Docker containers on an unRAID machine.
Here are the steps I took (which may have resolved the issue):
I will report back after a few days of automation to see if it’s still happening.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.