Sonarr version (exact version): 2.0.0.4613 Mono version (if Sonarr is not running on Windows): N/A OS: Windows 7 ((Debug logs)): Trace Log https://paste.ee/p/3B4Nh / Debug Log https://paste.ee/p/rkxhK
Description of issue:
Sonarr is working normally with usenet, however there have been occasions when it sends a torrent to qBittorrent (using rarbg) and it doesn’t append the tv-sonarr category to it. There seems to be no logic as to when it does/doesn’t do it.
The latest file in the logs is The 100 (S04E05). So once completed it will just sit there.
However Sonarr has also sent this to SabNZBd as a .nzb as well, which has already downloaded.
Is this why?
If so, why is it picking both?
The torrent will just sit there, untouched. If I change the category manually after it is complete, it will then process it, deleting the usenet downloaded one first and replacing with the torrent version.
I’m ok on space, so they can just sit there and I’ll either select manually or just delete, but I’m just confused as to why it is happening!
That could be happening because RARBG primarily uses magnet links and Sonarr may not be able set the label if qbit hasn’t resolved the torrent (not sue how that works for qbit).
The fact that an NZB was also grabbed is a symptom of the problem, which is likely Sonarr thinks the adding of the torrent failed and it looked for other sources. ((Debug logs)) of a grab (the attached logs don’t show any grabs), where something that was sent to qbit failed for some reason would be the piece we need to investigate further.
The trace log shows it (as well as the API calls Sonarr made, so it was actually better), but it doesn’t show any errors, according to the logs Sonarr sent the magnet to qbit, then set the category and both calls were successful.
If qbit failed to set the category after returning a successful response then something failed within qbit, perhaps qbit’s logs can shed some light on that.
