Seer pushing items to Radarr Sonarr thus qBittorrent #3413
|
I just installed and setup Seerr and love the look and ease of use of it so far. Corrdct me if I've got this wrong, but isn't Seerr only suppose to send to the arr's if make a request? I select a movie to test and it got sent to Radarr and thus qBittorrent. After I deleted the request in Seerr I've still getting error messages from QBT telling me duplicate files can't be added. Is this a Seer issue of continuing to send the request anyway, or is it a issue with the way Radarr received the info to pass to QBT? |
Replies: 5 comments 1 reply
What do you mean by select a movie to test? Once you request a movie on seerr, it gets passed to radarr. Deleting that request will not delete the radarr entry. Once its requested, its passed to radarr, and from there its out of responsibility of seerr. Radarr handles it. Seerr only awaits your media server to announce it as available from then on. Also please share your logs too. (Preferrably in our support channel discord as it's easier to troubleshoot and thats where we carry out support). |
|
Yea I get that I have to remove it from Radarr once I delete the request in Seerr. I started geting the below from QBT shortly after creating the request in Seer. |
|
I should add that Discord is having issues right now. I get the below if I try to go to it in the browser and the desktop app just sits and spins. |
That is not seerr related. Seerr doesn't interact with qBittorrent. And that looks like an issue with your radarr configuration/qBittorrent. This has nothing to do with seerr. Like i said, all seerr does is add the media to radarr and monitor it (the moment you request). After that seerr doesn't interact with radarr at all. From then on its handled by radarr on however you have it configured. Also please do not post content related to media acquisition. I removed that part of your post. |
|
I'm not one to believe in coincidences. This behavior only started like I said after I made the request. Since it doesn't seem to be hurting anything I'll just post on the QBT forums and see if they have any suggestions as to why. |
That message is a known qBittorrent quirk, not something on Seerr's end. See qbittorrent/qBittorrent#23810 and #23367 on their tracker. From what i can understand, when qBittorrent finds a duplicate torrent by info hash, it merges the new trackers into the existing entry, but still throws a "couldn't add torrent" error even though the merge succeeded. It's a misleading notification, not an actual failure. Seerr's involvement ends the moment Radarr accepts the grab request. If that download never successfully imported (stuck, failed move, permissions issue, etc.), Radarr will keep treating the movie as missing and its scheduled search or RSS sync will keep re-grabbing a matching release (depending on your radarr configuration). Since qBittorrent already has a torrent with that info hash sitting there from the first grab, each retry hits the duplicate/merge path and throws the same error again. Removing the movie from Radarr itself, not just the Seerr request, is what stops it. This is a Radarr/qBittorrent interaction end to end, and like i said completely unrelated to Seerr. |
That message is a known qBittorrent quirk, not something on Seerr's end. See qbittorrent/qBittorrent#23810 and #23367 on their tracker. From what i can understand, when qBittorrent finds a duplicate torrent by info hash, it merges the new trackers into the existing entry, but still throws a "couldn't add torrent" error even though the merge succeeded. It's a misleading notification, not an actual failure.
Seerr's involvement ends the moment Radarr accepts the …