Sonarr failed to blacklist failed NZBHydra nzb's correctly

Help & Support
1

Sonarr version (exact version): 2.0.0.4916
OS: Windows
Description of issue:
I have been Using NZBHydra for the past 2 weeks and notice something that never happened before. Just want to find out if it’s a known issue or must I raise a bug report.
Sonarr downloads the nzb from NZBHydra and when it fails it it black lists it correctly, but then just goes and downloads the same nzb from NZBHydra.
It’s like it doesn’t exclude the failed nzb from the list and always takes the top result. Could have failed like 30 times and it continues downloading the failed nzb.
It’s as if NZBHydra is hiding some identifying metric from Sonarr with which it matches multiple/failed downloads.

2

In some cases (I believe when the nzb doesn’t have a unqiue ID from the indexer), NZBHydra creates it’s own unique ID, but the problem is it’s a different ID every time do Sonarr treats it as a different NZB and tries it again. If NZBHydra can provide a stable ID it will work otherwise it may be best to disable that indexer within NZBHydra (at least for searching).

3

Thanks. Will try and see which indexer it is and disable it.

4

I kn ow someone had the issue with NZB Index before, but probably worth starting with any non-newznab ones.

5

You might be right. It’s either nzbindex or binsearch. Not that I use them in anycase.

6

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