If an indexer is offline and/or times out (usenet-crawler is doing a gateway timeout for me at the time of this posting), a manual search appears to fail until the indexer is disabled. Has anyone experienced this before?
I can reproduce if needed. I’ve just disabled Usenet-Crawler for now and it fixed it.
LJ
The manual search might take a while waiting for the search to that indexer to timeout, but it should eventually succeed.
Some debug logs would be helpful.
Markus,
Thanks for the quick reply. Unfortunately in my case, it never showed up with no results or results (I inspected the logs, no results). It just stayed at the loading ellipses.
Initial indexer timeout:
Here’s the clean debug logs: http://pastebin.com/wNq9RG0r
Results in logs:
LJ
Ahh, the timeout to the indexer exceeded the timeout to Sonarr’s server, makes sense. We’ll have to take a look.
Thanks Markus! I appreciate all you guys do for us.
LJ
@lordjynx which browser did you have this issue in?
Haven’t had a chance to dig in, but want to check if you’re running a reverse proxy or anything to connect to Sonarr? I haven’t found anything that indicates the connection would time out after a lengthy wait on the indexer.
I am using Nginx. I have the read timeout set to 60 seconds, perhaps I could increase that and test again (assuming an indexer is offline :P)
LJ
Yeah, I suspect that’s the issue, nginx isn’t waiting long enough in that situation.
What’s sonarr’s default timeout for indexers? I’ll increase mine accordingly.
LJ
Looks like we’re using the default of 100 seconds. You’ll also want to allow time for processing each result, 200 seconds would be more than enough I think.
Is that 100 seconds total for EACH indexer or 100 seconds total for all combined. In other words, does it wait 100 seconds then process the next or do them all at once?
LJ
Its 100 seconds per indexer request, but they’re done in parallel, unless they all take 100 seconds to respond they should all complete within that window.
Understood. Thanks Markus!
LJ
