Sonarr delete downloaded torrents

Drone Factory is configured on the Download Client settings page, its an advanced option. Ahh, i see it. No, ive never used the Drone Factory, the folder field is blank.

Where do I attached the log??? All i can see is an upload icon…. I suspect niczoom has uTorrent configured to stop seeding as soon as the download finishes Yes i did this a few weeks ago as the kids were streaming too much over the holidays, trying to save a few GB. Post it to hastebin. Use that. I really just need a new hosting provider though, I don't even think they'd update Sonarr even if this feature was added.

I still stand by the whole 'Sonarr should be able to respond to an indication of download failure from a torrent client" stance though. I was able to using Linuxserverio deluge. Maybe not but just curious. Guys I do appreciate all the tech support, but I'm in a managed shared environment because I'm cheap, and they use docker to provide plug-n-play addons, so they have docker locked down and unavailable to us mere peasants. I've sacrificed control for cheapness, so there's no hope for me until I migrate elsewhere.

It's just a matter of we as a community deciding on a pesudo-standard and requesting that it be implemented. To re-iterate what I believe was my strongest point. There should be a way for the Download client to passively advertise that a download has failed, and there should be a way for Sonarr to detect and respond to that if the user wants it to.

I just learned writing this post that Sonarr does support custom scripting for processing rules and such, but by the looks of it there's no way to use the existing hooks to support this particular thing, which is why we're asking for it to be included as a feature in the main application.

I personally believe that way should be 'The torrent was removed from the download client and Sonarr doesn't have the file it was expecting'. In my opinion, there is no reason that Sonarr shouldn't treat that scenario as a failed download. I am open to being presented one though. There was a reasonable sounding argument above, basically, "we don't know how long it will take -- what about network outages or giant season files". Doing peers does not make sense.

The root cause to this issue is really mostly public trackers lying to the user on site and to sonarr about the number of seeds a torrent has.

They may say a torrent has 50 seeds, but it really has 0. Then perhaps add an exception? Solution seems simple to me but perhaps I haven't understood correctly, or missed something important From my understanding, Sonarr already communicates with the download client on a regular basis to retrieve the status of each torrent.

When it does this, it already captures the progress of each of those torrents. Can't it just keep a history of each torrent's progress and use that to determine if a download has stalled or not? If a download hasn't progressed at all in the last X checks X being a configurable option, checks being where Sonarr gets the status from the download client , then it isn't progressing and is considered stalled. No need to guess at how long a download should take vs how long it's really taking.

As long as some progress is being made even slow , then it isn't stalled. Downloads that are stalled for more than Y minutes would be automatically blacklisted and removed from the download client, and a replacement would be automatically searched for. Then we have the question of "What if the internet is down and all downloads appear stalled" - Well it should be quite easy to detect the state of the internet shouldn't it?

Just make a test request to the indexers - if any respond, you have an internet connection. Failing that, ping a known working address. Do this before marking any downloads as stalled. With the last of this feature, I wrote a small script to handle this outside of Sonarr.

We currently know a torrent has stalled. While running this script, I no longer have any issues where stalled downloads hang forever, and with Sonarr error handling downloading a new torrent after it has been blocklisted is a breeze.

While I do understand it's not feasible for every user to configure something like this manually, It would be great to have something like this within Sonarr; if we are worried about settings defaults, keep the feature off by default, flag it as an advanced feature and let users set their parameters.

The following screenshot is my Sonarr blocklist after I started running this script, yes there are a few false positives, but that is something I'm more than happy to live with, knowing that the vast majority of them are correctly blocklisted torrents. Drapersniper I would love to see your script you used. Sounds exactly like what I need since I am ending up with tons of '0' byte torrents which won't go anywhere, and there doesn't seem to be an easy way to deal with them.

Skip to content. Star 6. New issue. Jump to bottom. Labels download-client enhancement. Copy link. But often i get that is no seeds at all when i look it up in Transmission. So i suggest that we can have a setting where we choose how many seeds we want. Thanks in advance and thanks for a great application. I think there are two separate issues here, add support to configure minimum number of seeds, very reasonable, the question is what should be the scope?

I want to say global setting. I would say global is ok per tracker is overkill I guess. Yes we really need an option to ignore seeders count! Hi just wanted to add some support to this thread. If a torrent gets picked up but it's really slow then let me have a parameter that globally forces another search after certain amount of elapsed time.

This would then obey the same rules as normal, in my case preferring nzb and then torrents as a backup with more seeds than the currently downloading file. If there isn't anything new to pickup then carry on, if there is something better out there, give it a go.

Hope that makes sense and thanks for listening :. SonarrBot mentioned this issue Jun 11, Torrent Support - Part 2 Feature Request: Removing 0 seeder torrents Any news on the implementation of this? Pretty please Qstick mentioned this issue Jul 22, Handle Hung Downloads How many more years must we wait? No, if it did this issue would be closed and in the v3 milestone. Failed Download Handling, expand support to Torrent Downloaders When I now re-download, Sonarr deletes it immediately it completes, without even any request from me to do any importing even after reboot!

Is the torrent stopping seeding immediately after it downloads? If you have Remove Completed Downloads enabled, the torrent is finished seeding and Sonarr has already imported at least one file from the torrent it will tell your download client to remove it and delete the files.

Via manual import? If it detected it properly it should have imported any episode file that was an upgrade automatically. Were all the files missing or only some of them?

I clicked the icon to import the first file, it gave me a list of all the 12, so I ticked all 12, but it only got 3 before they were deleted my guess is that the completion of importing the first file triggered the delete starting a race which the next two files won, but the remaining 9 did not.

Using the same category Sonarr is set to use is telling Sonarr to manage it, using a different category would tell Sonarr not to touch it manual import would still work.