SABnzb just queues the nzb with Fetch status

Post any problems / bugs / issues that are Mylar-related in here.
Post Reply
bigredone
Posts: 2
Joined: Thu Apr 26, 2018 1:33 am

SABnzb just queues the nzb with Fetch status

Post by bigredone »

I am using several nzb providers and nothing has been downloading recently. I am seeing the errors in the log. It is showing 10.35.86.234:8090 which is no ip I recognize. Also, the API that is showing is no api I have. Any help is appreciated.

23-Apr-2018 20:45:48 - INFO :: mylar.NZB_SEARCH.475 : Thread-12 : Shhh be very quiet...I'm looking for Regression issue: 9 (2018) using nzb.su.
23-Apr-2018 20:45:48 - INFO :: mylar.NZB_SEARCH.681 : Thread-12 : pausing for 60 seconds before continuing to avoid hammering
23-Apr-2018 20:45:48 - INFO :: mylar.NZB_SEARCH.753 : Thread-12 : no errors on data retrieval...proceeding
23-Apr-2018 20:45:48 - INFO :: mylar.searcher.2317 : Thread-12 : Found Regression (2018) issue: 9 using nzb.su
23-Apr-2018 20:45:48 - INFO :: mylar.searcher.2322 : Thread-12 : nzbid: 6e3432f06108ec9da45f63a75d4c9907
23-Apr-2018 20:45:48 - INFO :: mylar.searcher.2323 : Thread-12 : IssueID: 667697
23-Apr-2018 20:45:48 - INFO :: mylar.searcher.2324 : Thread-12 : oneoff: False
23-Apr-2018 20:45:48 - INFO :: mylar.failed_check.244 : Thread-12 : prov : nzb.su[6e3432f06108ec9da45f63a75d4c9907]
23-Apr-2018 20:45:48 - INFO :: mylar.failed_check.255 : Thread-12 : [FAILED_DOWNLOAD_CHECKER] Successfully marked this download as Good for downloadable content
23-Apr-2018 20:45:49 - INFO :: mylar.searcher.2487 : Thread-12 : filen: Regression0092018DigitalZone-Empire -- nzbname: Regression.009.2018.Digital.Zone-Empire are not identical. Storing extra value as : Regression0092018DigitalZone-Empire
23-Apr-2018 20:45:49 - INFO :: mylar.sender.41 : Thread-12 : parameters set to {'nzbname': u'Regression.009.2018.Digital.Zone-Empire.nzb', 'apikey': u'e4bb7de9c93f13d2bf1a1a329479671f', 'name': u'http://10.35.86.234:8090/api?apikey=2b5 ... Empire.nzb', 'cmd': 'downloadNZB', 'cat': u'comics', 'priority': '-100', 'mode': 'addurl', 'output': 'json'}
23-Apr-2018 20:45:49 - INFO :: mylar.sender.42 : Thread-12 : sending now to http://192.168.1.83:8080/api
23-Apr-2018 20:45:49 - INFO :: mylar.sender.49 : Thread-12 : {u'status': True, u'nzo_ids': [u'SABnzbd_nzo_L90iXH']}
23-Apr-2018 20:45:49 - INFO :: mylar.searcher.2800 : Thread-12 : Successfully sent nzb file to SABnzbd
23-Apr-2018 20:45:49 - INFO :: mylar.nzblog.683 : Thread-12 : setting the nzbid for this download grabbed by nzb.su in the nzblog to : 6e3432f06108ec9da45f63a75d4c9907
23-Apr-2018 20:45:49 - INFO :: mylar.nzblog.687 : Thread-12 : setting the alternate nzbname for this download grabbed by nzb.su in the nzblog to : Regression0092018DigitalZone-Empire
23-Apr-2018 20:45:49 - INFO :: mylar.foundsearch.751 : Thread-12 : [UPDATER] Updating status to snatched
23-Apr-2018 20:45:49 - INFO :: mylar.foundsearch.847 : Thread-12 : [UPDATER] Updated the status (Snatched) complete for Regression Issue: 9
23-Apr-2018 20:45:49 - INFO :: mylar.searchforissue.1944 : Thread-12 : result: {'Issue_Number': u'6', 'IssueID': u'667698', 'StoreDate': u'2018-04-25', 'StoryArcID': None, 'SARC': None, 'IssueArcID': None, 'mode': 'want', 'IssueDate': u'2018-04-30', 'ComicID': u'102612'}
23-Apr-2018 20:45:49 - INFO :: mylar.issue_status.2374 : Thread-12 : returning false
23-Apr-2018 20:45:49 - INFO :: mylar.search_init.70 : Thread-12 : Issue Title given as : None
23-Apr-2018 20:45:49 - INFO :: mylar.search_init.168 : Thread-12 : search provider order is ['public torrents', 'nzb.su', 'dognzb', 'newznab:NZB Planet', 'newznab:NZB Geek']

Thanks,
bigredone
User avatar
evilhero
Site Admin
Posts: 2883
Joined: Sat Apr 20, 2013 3:43 pm
Contact:

Re: SABnzb just queues the nzb with Fetch status

Post by evilhero »

Do you have more than one interface / network card on the machine with mylar?

The 10.35.86.234:8090 is the address that sabnzbd is trying to access to download the nzb (basically from mylar since it already downloaded it).

So it could be one of 2 things:
- what do you have specified for the mylar host in the configuration GUI?
- Are sabnzbd and mylar on different machines? And do you have the different machines option enabled?

If they are on different machines, and you specify localhost as the mylar host, it won't resolve properly. You have to set it to either 0.0.0.0 to listen on all interfaces, or the ip address of the mylar machine.

Otherwise, you can specify the return_host value in the config.ini so that when mylar creates the download link url it sends to sabnzbd, it will have the correct mylar address. So setting it as: return_host = http://192.168.1.83:8080 would allow it to retrieve the file from mylar when called from sabnzbd.
bigredone
Posts: 2
Joined: Thu Apr 26, 2018 1:33 am

Re: SABnzb just queues the nzb with Fetch status

Post by bigredone »

Now I get this error.

2018-04-27 21:30:01 ERROR Uncaught exception: Traceback (most recent call last):
File "c:\Mylar\mylar\logger.py", line 335, in new_run
old_run(*args, **kwargs)
File "c:\Python27\lib\threading.py", line 754, in run
self.__target(*self.__args, **self.__kwargs)
File "c:\Mylar\mylar\webserve.py", line 1427, 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, torrentid_32p=TorrentID_32p)
File "c:\Mylar\mylar\search.py", line 334, 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, oneoff=oneoff, cmloopit=cmloopit, manual=manual, torznab_host=torznab_host, torrentid_32p=torrentid_32p)
File "c:\Mylar\mylar\search.py", line 1783, in NZB_SEARCH
searchresult = searcher(nzbprov, nzbname, mylar.COMICINFO, links, IssueID, ComicID, tmpprov, newznab=newznab_host, torznab=torznab_host)
File "c:\Mylar\mylar\search.py", line 2798, in searcher
sendtosab = ss.sender()
File "c:\Mylar\mylar\sabnzbd.py", line 48, in sender
sendresponse = sendit.json()
File "c:\Mylar\lib\requests\models.py", line 819, in json
return json.loads(self.text, **kwargs)
File "c:\Mylar\lib\simplejson\__init__.py", line 428, in loads
return _default_decoder.decode(s)
File "c:\Mylar\lib\simplejson\decoder.py", line 402, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "c:\Mylar\lib\simplejson\decoder.py", line 420, in raw_decode
raise JSONDecodeError("No JSON object could be decoded", s, idx)
JSONDecodeError: No JSON object could be decoded: line 1 column 0 (char 0)
2018-04-27 21:30:01 INFO sending now to http://192.168.1.83:8080/api
2018-04-27 21:30:01 INFO parameters set to {'nzbname': u'Wonder.Woman.049.2016.Digital.HD.Thornn-Empire.nzb', 'apikey': u'e4bb7de9c93f13d2bf1a1a3294', 'name': u'http://192.168.1.83:8080/api?apikey=5db ... Empire.nzb', 'cmd': 'downloadNZB', 'cat': u'comics', 'priority': '-100', 'mode': 'addurl', 'output': 'json'}
2018-04-27 21:30:01 INFO filen: WonderWoman0492016DigitalHDThornn-Empire -- nzbname: Wonder.Woman.049.2016.Digital.HD.Thornn-Empire are not identical. Storing extra value as : WonderWoman0492016DigitalHDThornn-Empire
2018-04-27 21:30:01 INFO [FAILED_DOWNLOAD_CHECKER] Successfully marked this download as Good for downloadable content
2018-04-27 21:30:01 INFO prov : nzb.su[614e1e8908b36e296f36ac35]
2018-04-27 21:30:01 INFO oneoff: False
2018-04-27 21:30:01 INFO IssueID: 516070
2018-04-27 21:30:01 INFO nzbid: 614e1e8908b36e296f36ac35d910387b
2018-04-27 21:30:01 INFO Found Wonder Woman (2016) issue: 52 using nzb.su
2018-04-27 21:30:01 INFO no errors on data retrieval...proceeding
User avatar
evilhero
Site Admin
Posts: 2883
Joined: Sat Apr 20, 2013 3:43 pm
Contact:

Re: SABnzb just queues the nzb with Fetch status

Post by evilhero »

It's saying that it can't get a response from your sabnzbd server that's a valid response.

Is

Code: Select all

http://192.168.1.83:8080/api
the correct location for your sabnzbd instance? Have you tried to do the Test Sabnzbd option in the Configuration/Download Settings tab?
Post Reply