Hi,
Today I launched an automatic search and I suspect that a rss search started just after, and I just noticied that sonarr grabbed twice the same episode but different releases (NCIS.Los.Angeles.S07e02)
I didn’t received a grabbed push notification for both (received one for an other episode just before).
My deluge system sent me two complete notification, this is how I understood whats going on.
I checked deluge, this two episode got no label…
Can you help me to inderstand/fix that ?
It could be a couple things, since they are different releases they could be different qualities and the second quality added is better (and the cutoff wasn’t met yet) or it could be that the first release queued wasn’t in Sonarr’s queue yet so the second one didn’t fail on the queue check.
In either case there isn’t anything we can really fix, if Sonarr is told to do two things at once (either manually or scheduled) this is a potential issue.
Also your logs were already removed…
Here is the log again http://pastebin.com/HaYnF3kw
Strange because I don’t even receive notifications…
You can’t add a lock or a queue system to avoid that?
It happens again few day ago.
Double Grabbing without label and notifications.
Your logs are full of connection errors to Deluge, if Deluge fails to respond properly (or responds saying it failed to add), Sonarr would try to queue another release.
Looks like we’re talking about two separate issues though:
Two actions add releases to the download client at the same time (RSS and search) - a queue here may prevent it, but it wouldn’t be guaranteed since both could check the queue, see no conflicts and both try to queue because adding to the queue is the last thing Sonarr does after checking all the results
Deluge responds with an error/appears to fail to receive the torrent so Sonarr attempts another release, because the request failed Sonarr doesn’t apply a label to the release or track it.
With 1 there isn’t a lot we can do, we do track downloads in a queue of the download client and this is a fringe case that could happen, but wouldn’t happen often. For 2 this is a problem with Deluge, not something we can fix, if Deluge send a failed response/doesn’t respond properly Sonarr accepts that as fact, it won’t check to see if its incorrect, it will try a different release.
I don’t think that this is my problem finally, because I just figure out that my RSS doesn’t work.
I’m interested about understanding this one. My deluge freezes when it downloads too fast.
May be I will plan to download on local and not on my NAS.
Sonarr will make a copy on my NAS after, right? Not a move?
Yeah, Sonarr will copy the torrent if its still seeding otherwise it will move it.
What did you use to define the seeding status ? Because I’m absolutely need a copy.
Oh OK, if it’s not paused so. Thanks 
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.