Everybody else seems to be having the opposite problem, but I am using private trackers and DON’T want my torrents to stop seeding until I do it manually, independently from Sonarr. I am using Deluge, and my seed and ratio settings are all -1 (correct me if I’m wrong, but this means they should seed permanently). I also have turned OFF the “Remove” option in both Failed and Completed Download Handling. I also have enabled hardlinks instead of copying.
Is it possible that Sonarr is starting up faster than Deluge on a reboot, sees that the file isn’t seeding, and then it removes the torrent, thinking the seeding has completed? Or is there something else at work here?
Can you confirm that you are using the Deluge download client in Sonarr and not Blackhole?
The only option in Sonarr that would remove a completed torrent is the Remove option under Completed Download Handling, if you’re using the Deluge download client, if you are using Blackhole, thats your problem (it always moves).
If Sonarr started before Deluge it would fail to connect to Deluge and not get any status of the active downloads and not do anything and its torrent removal process is to ask the download client to remove the item from disk and its queue.
((Debug logs)) will show the removal process, but ((trace logs)) would be even better as they show the response from Deluge that we could use to piece together why Sonarr ask Deluge to remove the torrent. Of course these logs would need to be enabled when the torrent was being removed and assuming Sonarr played a role in it.
Thanks for the quick response. Yes, I am absolutely sure that I have Deluge set correctly, and not as a Black Hole torrent client. I will keep an eye out and try to get you some trace logs if I notice it happen again. I only realized it this time because I was notified by a tracker that I had abandoned several of my torrents too quickly.