Sonarr: Failing to remove completed torrents from download client using categories v3

Created on 21 Apr 2020  路  16Comments  路  Source: Sonarr/Sonarr

Describe the bug
I've been having problem since the weekend when Sonarr updated with the completed torrent. I have ratio 2, but the torrent becomes paused and Sonarr imported the file, but it forgets to check if the torrent is ready to be removed. I am using category option, though.

I have that configuration since last year and the only change in my system was the update of Sonarr.

Radar is still working flawless and I could confirm that I have no change any configuration in my download client (Transmission).

I think that my problem started with 3.0.3.764

Logs
https://pastebin.com/58k8FMkb

System Information

  • Sonarr Version: 3.0.3.765
  • Operating System: 3.0.3.765-ls8 by linuxserver.io
  • mono (macOS/Linux) Version: 5.20.1.34

Annotation 2020-04-21 113714

bug

Most helpful comment

It's the same issue for all clients, I see why it's happening, just need to figure out a good way to solve it.

All 16 comments

At a minimum we need debug logs, though in this case trace logs will show us the response from Transmission which will be useful.

thank you for the answer. I will change the log to debug mode and report.

Usually, I use ratio 1, but for this test, I've changed to 0.28 and I've done manual search in Sonarr. I've activated the debug mode before starting.

This time, I have 3 debug files, you can download from here: https://gofile.io/?c=62yPKV

I didn't remove the file or change the debug mode, if you need more information.

Annotation 2020-04-21 134714

It seems to be the same problem. At least, it is not only for Transmission. Just for the record. Last week, it was working correct. The torrent was removed once the limited was reached. Now, the torrent remains paused and it is not removed.

It's the same issue for all clients, I see why it's happening, just need to figure out a good way to solve it.

Was seeing the same issue and was wondering what did i mess up :). Can confirm see this in 3.0.3.770 as well.

I know this is marked as resolved and closed, but I've updated 2 releases past the one that was meant to fix it and am still having the issue.

I can also confirm that I have updated to 3.0.3.774 and still have the issue.

Same here, I'm using transmission.

Same. Issue is still there.

Please provide updated trace logs.

Yep, working now. Thanks!

I will test it tonight. Thank you very much.

Just want to confirm that it is working as before... thank you again

Was this page helpful?
0 / 5 - 0 ratings

Related issues

PiscisSwimeatus picture PiscisSwimeatus  路  3Comments

mabasic picture mabasic  路  3Comments

markus101 picture markus101  路  3Comments

markus101 picture markus101  路  4Comments

imathew picture imathew  路  4Comments