Isue with DogNZB(maybe)

Post any problems / bugs / issues that are Mylar-related in here.

Isue with DogNZB(maybe)

Postby disposablehero » Sat Apr 15, 2017 7:00 am

Hi,

today I ran into an error with DogNZB. While searching for Comics, I always get an Error:
Code: Select all
2017-04-15 08:53:06   ERROR   Uncaught exception: Traceback (most recent call last):
File "c:\Mylar\mylar\logger.py", line 158, in new_run
old_run(*args, **kwargs)
File "C:\Python27\lib\threading.py", line 763, in run
self.__target(*self.__args, **self.__kwargs)
File "c:\Mylar\mylar\webserve.py", line 1425, in queueissue
foundcom, prov = search.search_init(ComicName, ComicIssue, ComicYear, SeriesYear, Publisher, issues['IssueDate'], storedate, IssueID, AlternateSearch, UseAFuzzy, ComicVersion, mode=mode, ComicID=ComicID, manualsearch=manualsearch, filesafe=ComicName_Filesafe, allow_packs=AllowPacks)
File "c:\Mylar\mylar\search.py", line 257, in search_init
findit = NZB_SEARCH(ComicName, IssueNumber, ComicYear, SeriesYear, Publisher, IssueDate, StoreDate, searchprov, send_prov_count, IssDateFix, IssueID, UseFuzzy, newznab_host, ComicVersion=ComicVersion, SARC=SARC, IssueArcID=IssueArcID, RSS="no", ComicID=ComicID, issuetitle=issuetitle, unaltered_ComicName=unaltered_ComicName, allow_packs=allow_packs)
File "c:\Mylar\mylar\search.py", line 1600, in NZB_SEARCH
if foundc == "yes":
UnboundLocalError: local variable 'foundc' referenced before assignment
2017-04-15 08:53:06   WARNING   Connection error trying to retrieve data from dognzb: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)


If that Error occurs, Mylar will stop searching.

What I did was, removed DogNZB from my Search Providers, and use my second Provider NZBGeek, and with that Mylar worked fine.

I´m on:
Mylar Version: development
-- git build 13cbe739c6a8a86905a1873519c8dffa5edf3240.
Python Version : 2.7.9
Win 7 Maschine

Any Ideas?

Thanks and Happy Easter
DH
disposablehero
 
Posts: 13
Joined: Sat Nov 21, 2015 7:44 am

Re: Isue with DogNZB(maybe)

Postby evilhero » Sat Apr 15, 2017 8:10 pm

Yeah that's a problem in the exception handling of that particular error - it should be notifying and then continuing on to the next provider. Should have it up in the next development commit when I get some time this long weekend to push it out.

The more important problem at hand, is why it's throwing the error that it can't verify the ssl certificate for dognzb. The
Code: Select all
Connection error trying to retrieve data from dognzb: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)
indicates that either dog has an invalid certificate or that your python version is having problems authenticating the certificate. You might have to do:

Code: Select all
pip install requests[cryptography]


or update something in relation to that.

However, I know that dog was trying to put out a new api server over the last few weeks, and I believe it went live just 24hours ago - so perhaps the error you were getting was related to their api problems they've been having for the past few weeks.

Are you still experiencing the problem (given that they just rolled a new api server out less than 24hrs ago)...
User avatar
evilhero
Site Admin
 
Posts: 1886
Joined: Sat Apr 20, 2013 3:43 pm

Re: Isue with DogNZB(maybe)

Postby disposablehero » Sun Apr 16, 2017 6:08 am

Today I tried again, but the same Error came up. I also did update my requests[cryptography] in Python, but no success.

Then I went to DogNZB and searched their Forum, and it seems that indeed other people have the same issue with their API:
Code: Select all
https://dognzb.cr/board/index.php?/topic/3118-api-issues/page-6


What one Member recommended was to disable the Verify SSL Option. I tried to do that in Mylar, but once Mylar restartet the Option is set again. So my questions is: is there any way to disable the SSL Option, without the preference menu? maybe a config file change?

Thanks
DH
disposablehero
 
Posts: 13
Joined: Sat Nov 21, 2015 7:44 am

Re: Isue with DogNZB(maybe)

Postby evilhero » Sun Apr 16, 2017 5:30 pm

Yep just look for dognzb_verify and set the value to False.

Keep in mind that mylar cant be running when you're editing the config.ini too.

I'll have to check into why the Gui isn't holding the settings properly... It was working as far as I was aware.
User avatar
evilhero
Site Admin
 
Posts: 1886
Joined: Sat Apr 20, 2013 3:43 pm

Re: Isue with DogNZB(maybe)

Postby disposablehero » Mon Apr 17, 2017 7:28 am

Setting the config file to dognzb_verify = False worked with DogNZB. Seems they need to get their API working again.

One thing about Mylar, once I was done and Shutdown Mylar, I checked the config.ini again, and the dognzb_verify was set to True again. Even if I never went into the Preference API within Mylar.

Thanks
DH
disposablehero
 
Posts: 13
Joined: Sat Nov 21, 2015 7:44 am

Re: Isue with DogNZB(maybe)

Postby evilhero » Mon Apr 17, 2017 8:30 pm

Yep, can confirm - it looks like it was taking the wrong interpretation of the bool (basically a true statement, didn't equate to a 1).

Think I have it fixed in my local repo now - so when I push the next dev it'll be in there with a buncha other stuff that I haven't been able to push out yet due to the long weekend :/
User avatar
evilhero
Site Admin
 
Posts: 1886
Joined: Sat Apr 20, 2013 3:43 pm


Return to Problems / Bugs / Issues

Who is online

Users browsing this forum: No registered users and 2 guests

cron