DrunkenSlug not available

Sonarr version (exact version): 3.0.4.1058 (Package Version: 3.0.4.1058-ls22 by linuxserver.io). However, I had this problems for a very long time
Mono version (if Sonarr is not running on Windows): 5.20.1.34
OS: Docker on a Qnap 453A running QTS 4.5.1.1495
Debug logs:
21-1-9 08:48:36.7|Debug|Newznab|Downloading Feed https://drunkenslug.com/api?t=tvsearch&cat=5020,5030,5040,5045,5080&extended=1&apikey=(removed)&offset=0&limit=100&tvdbid=70327&imdbid=tt0118276&rid=2930&tvmazeid=427&season=3
21-1-9 08:50:00.0|Warn|Newznab|DrunkenSlug https://drunkenslug.com/api?t=tvsearch&cat=5020,5030,5040,5045,5080&extended=1&apikey=(removed)&offset=200&limit=100&tvdbid=70327&imdbid=tt0118276&rid=2930&tvmazeid=427&season=2 Failed to read complete http response
21-1-9 08:50:00.2|Debug|IndexerFactory|Temporarily ignoring indexer DrunkenSlug till 1/9/2021 8:54:59 AM due to recent failures.
21-1-9 08:50:00.4|Debug|IndexerFactory|Temporarily ignoring indexer DrunkenSlug till 1/9/2021 8:54:59 AM due to recent failures.
Description of issue:
After a while Sonarr can’t use DS as an indexer. This happens from time to time when it automatically searches for missing episodes or like you can see in the log when I force a search for complete seasons of a TV show.
On DrunkenSlug I’m a “Wine supporter” which means no limits on API calls. When I check my account there is still a limit but I’m way under it (61/86400 API Calls).
When I added DS I used the Newznab DS preset. I also added the indexer again, but no change. When DS is not available I can fix it for the moment by either going to the indexer under settings and test it (test always works without issues) or under System - Status fixing the indexer.

Any ideas what’s wrong?

Log:

Please enable trace logging and post and link to the relevant logs when it happens again. From the logs it looks like there are simultaneous searches happening which shouldn’t be a problem, but it’s hard to see exactly what is happening and when exactly it’s failing.

1 Like

Thanks for your answer! I enabled trace logging and I hope that’s the relevant part:

Does it only fail like this when you’re performing a full season search? In both examples the request that fails this way was a search for the season. Unfortunately the logs don’t show the request, so I can’t see how long it took before it failed, but if it’s around 90 seconds that’d be where Sonarr about be timing the connection out.

1 Like

Not only when doing a full season search but that’s the best way to reproduce the error. I think it took around 10 minutes before it failed. Definitely more than 90 seconds.

The search is taking 10 minutes before it ultimately fails? Or Sonarr is running for 10 minutes before it DS fails this way?

1 Like

Search takes 10 minutes before failing.