Unable to add a new show about readynas-sickchill HOT 4 CLOSED

Thanks for the issue report! Before a real human comes by, please make sure your report has all the below criteria checked

• Include basic information: Branch/Commit, OS, What you did, What happened, What you expected
• Enable debug logging (be sure to disable after the bug is fixed)
• Post debug logs, either inline (for smaller logs) or using gist

Please make sure you also read how to create an issue and followed all of the steps.

The title should describe your issue. Having "SR not working" or "I get this bug" for 100 issues, isn't really helpful. We will close issues if there isn't enough information.

Sometimes the devs may seem like grunts and respond with short answers. This isn't (always) because the dev hates you, but because he's on mobile or busy fixing bugs. If something isn't clear, please let us know, and this bot may get updated to automatically answer you.

Thanks!

from readynas-sickchill.

Welcome to GitHub.
What version inside of SickRage are you running? Did you update the latest version in SickRage? You can get more info what of you are running under Help & Info.
Are you getting any warnings in the logs?

from readynas-sickchill.

Branch: master
Commit: 7e6e0575542c3f3e5476663532b1357f3ae1e902
Database Version: 44.0
Python Version: 2.7.3 (default, Mar 13 2014, 11:03:55) [GCC 4.7.2]
SSL Version: OpenSSL 1.0.1t 3 May 2016
OS: Linux-4.1.30.x86_64.1-x86_64-with-debian-8.6
Locale: en_US.UTF-8

This is the message I get when I do my search : search timed out, try again or try another indexer

This is the log just after the search

13:45:47 DEBUG Thread-15 :: Searching for Show with searchterm(s): ['Game of Thrones'] on Indexer: theTVDB

Everything else seams none related to the thread. No errors or warnings for this.

Let me know if there's anything else you need to know. Thank you for your time and effort.

from readynas-sickchill.

It sounds like the ReadyNAS SickRage is up to date.
You like be running into a SickRage config issue or possible bug. There is another guy that file an issue that sounds similar to what you described:
SiCKRAGE/SiCKRAGE#2465

from readynas-sickchill.