Failed Download Handling not working properly

Sonarr version (exact version): 2.0.0.4753
Mono version (if Sonarr is not running on Windows): 4.6.2.7-8
OS: Synology DSM 6.1.1-15101 Update 2
Debug logs: https://pastebin.com/zpuv59MP
Description of issue:

I have a Sonarr + SabNZB combination and for some reason, a failed download will be downloaded over and over again (every minute).

In this case it’s an episode of Entourage. I select the episode in Sonarr, click on “search selected” and it finds an episode. SabNZB tries downloading but fails because of damaged files. Sonarr sees that if fails but redownloads the same file, SABnzb marks it as duplicate, Sonarr receives the failed message and starts searching again, finds the same release, sends download to SABnzb etc. etc.

Here you can see Sonarr sees the downloads as failed.

Rebooting Sonarr or the synology doesn’t work. The only way to make this loop stop, is by disabling the indexer and turning it back on again. As soon as I use “search selected episode” again, the whole loop starts another time.

What is going on here?

Is it always the same indexer?
Sonarr uses a few pieces of information to determine if a release is the same one it blacklisted, if the release has a different ID from the same indexer (even if it has the same name) Sonarr treats it as a different release. If your indexer is giving Sonarr a different ID every time it searches it will keep grabbing it (assuming it’s the highest ranked release). I suspect that is the issue here.

This is happening to me as well. I just downloaded 400+GB of Twin Peaks, lol.

Not sure which of these would be helpful.

/edit: Actually, My issue is different, I think, as mine is downloading basically every version it can find of a show/season pack. They’re actually all different copies. I’ll look for a more relevant existing post, or make my own. Sorry!

Markus101, I’m using NZBhydra with all kinds of indexers setup. The “second-tier” indexer used in this loop example is NZBindex. Does that confirm your hypothesis?

Doesn’t confirm it outright, but I think it re-enforces it. I’s likely that NZBIndex doesn’t have a unique ID so NZBHydra is generating one, but it changes each time so Sonarr sees it as a new release. If you disable that indexer (or at least searching) do you see the same issue continue?

Markus, if I disable nzbindex the problem is gone. I guess that Will be the Approach for now :wink: Thanks!

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.