Sonarr not working - All indexers are unavailable due to failures

Help & Support
1

I’m using Ubuntu 16.04 LTS
Sonarr version 2.0.0.4949

I’ve this message in System > Status tab > Health
All indexers are unavailable due to failures

If I go to Settings > Indexers > Click on each indexer and test, it works but I’ve multiple indexers and I don’t want to repeat this process every now and then. I’ve noticed it happens often.

I’ve restarted both jackett and sonarr services but that didn’t help.

Here’s the link to file from Settings > Logs > Sonarr.txt
https://pastebin.com/HckQhBuP

Any help would be greatly appreciated.

2

Looks like Jackett throws an error because MTV is unavailable:

17-10-29 04:30:58.7|Warn|HttpClient|HTTP Error - Res: [GET] http://localhost:9117/api/v2.0/indexers/morethantv/results/torznab/api?t=tvsearch&cat=5030,5040&extended=1&apikey=(removed)&offset=0&limit=100: 500.InternalServerError
{
  "result": "error",
  "error": "Exception (morethantv): Request to https://www.morethan.tv/torrents.php?searchstr=&tags_type=1&order_by=time&order_way=desc&group_results=1&action=basic&searchsubmit=1 failed (Error BadGateway) - The tracker seems to be down.: Request to https://www.morethan.tv/torrents.php?searchstr=&tags_type=1&order_by=time&order_way=desc&group_results=1&action=basic&searchsubmit=1 failed (Error BadGateway) - The tracker seems to be down.",

If that happens multiple times Sonarr will temporarily disable the indexer, is MTV going down or is Jackett having issues?

3

MTV is up and Jackett isn’t having any issues either. I just checked MTV and ran Jackett test, both went fine.

4

Now it is, but on the 29th it failed several times, to the point where Sonarr disabled it temporarily.

5

Okay, understood. But, why would it disable all indexers? According to your logic, only MTV should’ve been disabled, right? Currently, all indexers are disabled and I’m clueless why.

6

MTV is the one I specifically called out, I saw other failures as well:

17-10-29 11:12:15.9|Warn|Torznab|Avistaz server is currently unavailable. http://localhost:9117/api/v2.0/indexers/avistaz/results/torznab/api?t=tvsearch&cat=5030,5040&extended=1&apikey=(removed)&offset=0&limit=100 The request timed out: 'http://localhost:9117/api/v2.0/indexers/avistaz/results/torznab/api?t=tvsearch&cat=5030,5040&extended=1&apikey=(removed)&offset=0&limit=100'
17-10-29 11:12:27.9|Warn|Torznab|Cinema Z server is currently unavailable. http://localhost:9117/api/v2.0/indexers/cinemaz/results/torznab/api?t=tvsearch&cat=5030,5040&extended=1&apikey=(removed)&offset=0&limit=100 The request timed out: 'http://localhost:9117/api/v2.0/indexers/cinemaz/results/torznab/api?t=tvsearch&cat=5030,5040&extended=1&apikey=(removed)&offset=0&limit=100'

(Plus others). Looks like indexers through Jackett are failing.

7

Hmm, I don’t see any failures in Jackett. Also, if I retest each indexer in Sonarr, it works. But, I’ve like 20 indexers and it’s a tedious process to retest each, given that this issue repeats itself often.

In Jackett, there’s a ‘test all’ button so it’s not an issue. Unfortunately, there’s no such option in Sonarr.

8

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