search

evilhero / mylar

An automated Comic Book downloader (cbr/cbz) for use with SABnzbd, NZBGet and torrents
GNU General Public License v3.0
976 stars 169 forks source link

Mylar does not recognize torznab search providers #2431

Closed tolusonaike closed 4 years ago

tolusonaike commented 4 years ago

Describe the bug I suspect Mylar is not recognizing my torznab configuration. To test, i turned off nzb and trying to use only torznab, i get the error below

Screenshots/Logs image

mylar.log14-Mar-2020 15:57:36 - ERROR :: mylar.csv_load.1366 : MainThread : Could not locate exceptions.csv file. Make sure it is in datadir: /config/mylar

14-Mar-2020 15:57:37 - WARNING :: mylar.searchforissue.1875 : Thread-12 : There are no search providers enabled atm - not performing an RSS check for obvious reasons

14-Mar-2020 15:59:37 - WARNING :: mylar.searchforissue.1877 : SEARCH-QUEUE : There are no search providers enabled atm - not performing an Force Check for obvious reasons

Environment (please complete the following information):

evilhero commented 4 years ago

We've pretty much migrated to the python3 fork located here, and while I realise that you're using a docker, it bears mentioning that we've frozen the codebase on mylar save for critical bugs until such time as we deem it EOL.

That being said, without the debug logs it's hard to see what's the problem - so you'll have to pastebin/paste those in if you can (make sure to strip the apikeys, etc - as that functionality is not in this version of Mylar). If you're uncomfortable pasting the log, you can just throw it to me. Either way, I can look more into it when I'm able to see the debug log showing the workflow (ie. Start of search to warning message indicating no providers).

tolusonaike commented 4 years ago

@evilhero i just went ahead and upgraded to mylar3. Thanks for your quick response!