Recently I’ve found that my indexers from Jackett go offline fairly regularly, usually overnight while I sleep. Neither Sonarr or Jackett have updated recently and I’ve changed nothing else, so hopefully just some passng weirdness - but I’ve found when it happens that the only way to get the indexers to test ok when it happens is to restart both Jackett and Sonarr, and then manually test them.
I’ve made a bash shortcut to automate restarting Jackett and Sonarr - I wondered though if there was a way to tell Sonarr from the commandline to test all indexers to save me going in and manually clicking on them all?
Thanks! I had a look in the logs - there’s basically a warn level event for each torznab component saying “x server is currently unavailable”, “the operation has timed out.” Will debug level provide more detail?
EDIT: just checked - I had my logs already set at debug level. Do I need trace?
You’ll get some more information from trace, but debug should be sufficient. Post logs that include that error and link them here, that’ll give us some insight, as will the information requested when opening a support thread (OS, Sonarr version, mono version, etc).
I actually have RARBG set up both natively and via jackett - thought that was another good way to mitigate the issues of jackett going down! I’m fairly sure (although not 100%) that there have been times since I’ve done that when the built-in RARBG support has also gone down with jackett, but that could just be coincidental.
I think the log file I passed along before happened to be from a fairly unexciting period, error wise. I’ve updated the link with the active log from yesterday, when the jackett indexers definitely all went down for a while. That said, I can’t say I see anything illuminating myself - other than it looks as if the built-in RARBG throws an error a view times as well?
