Page 1 of 1

sabnzbd integration with newznab

Posted: December 20th, 2012, 5:13 pm
by poto
Hi,
I'm looking for some help with sabnzbd integration w/newznab. Newznab is set up with full api key, and I can see the queue and download entries in newznab main menu. When I click on the "send to nzb" button, newznab responds with msg that nzb sent to queue, but nothing is showing up in the newznab queue window. From the sabnzbd queue, I can see an entry, but nothing is being retrieved, it just keeps recycling the request: "Trying to fetch NZB from http://localhost/getnzb/6f56021f334b455 ... 8b74bbb60b"
Thanks!

Re: sabnzbd integration with newznab

Posted: December 20th, 2012, 5:22 pm
by shypike
What happens if you paste that entry into a web browser?

Re: sabnzbd integration with newznab

Posted: December 20th, 2012, 7:23 pm
by poto
When the queue url is entered in a browser, the nzb is retrieved and a "save as" window displays. The file is correctly named and the default save directory matches sabnzbd setup file. Once the file is saved, sabnzbd adds to queue and downloads as expected.

debug logging output:
2012-12-21 00:57:52,013::INFO::[_cplogging:55] [21/Dec/2012:00:57:52] ENGINE Bus STARTED
2012-12-21 01:34:39,776::DEBUG::[interface:420] API-call from 192.168.1.17 [Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13] {'output': 'json', 'apikey': '54f122a2fc4b69c416cea674fa322xxx', 'mode': 'qstatus'}
2012-12-21 01:34:43,391::DEBUG::[interface:420] API-call from 192.168.1.17 [Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13] {'output': 'json', 'apikey': '54f122a2fc4b69c416cea674fa322xxx', 'mode': 'qstatus'}
2012-12-21 01:34:47,082::DEBUG::[interface:420] API-call from 192.168.1.17 [Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13] {'output': 'json', 'apikey': '54f122a2fc4b69c416cea674fa322xxx', 'mode': 'qstatus'}

If relevant, I'm running latest version of sabnzbd & newznab. The sabnzb working directories are mapped to a shared "scratch" drive on fileserver. All 3 pc's are win7x86 vm's on the same esxi host.
Thanks for the help!

Re: sabnzbd integration with newznab

Posted: December 21st, 2012, 5:43 am
by shypike
If you paste the same URL into SABnzbd's "Add NZB" dialog, what happens then?
Since I have no newznab, I cannot test.
I do have nzbz.org (customized newznab) send me API-calls with NZBs and that works fine.

Re: sabnzbd integration with newznab

Posted: December 21st, 2012, 8:58 am
by poto
Some progress here -
When I paste same URL into "Add NZB" dialog, I get the same result - sab keeps trying to fetch nzb from "localhost" I replaced "localhost" in the address with ip from newznab vm and nzb added successfully to sabnzb queue! Same success substituting network alias of newznab vm for "localhost' in url. So it seems, in my limited grasp of what is happening, that the request being sent from newznab to sabnzbd is assuming that sabnzbd is on the same box as newznab. I think I need to figure out a way to configure the nzb request to generate with the specific ip/name of the newznab box.

Re: sabnzbd integration with newznab

Posted: December 21st, 2012, 10:41 am
by shypike
It may have to do with SABnzbd and the browser having different ideas
about what localhost is.
Often it resolves to both 127.0.0.1 (IPv4) and ::1 (IPv6).
You could let all programs use 127.0.0.1 instead of localhost.

Re: sabnzbd integration with newznab

Posted: December 21st, 2012, 11:24 am
by poto
Ok, can you point me toward any docs to get me started on how to do that? I'm guessing the hosts file needs to be modified, but I'm not sure if both the newznab and sabnzbd vm's would need their host files changed. I'm also assuming the sabnzbd config>general>hosts field would be updated to 127.0.0.1? Thanks for your patience - I'm a little out of my depth here.

Re: sabnzbd integration with newznab

Posted: December 21st, 2012, 1:06 pm
by poto
Solved! After trying different host file configurations, I stopped all ops. on newznab and did a database cleanup/optimization. Rebooted newznab/sab vm's and all is well, nzb's passing successfully. All I can attribute this to is that I was trying to request nzb's for newest releases while running massive backfill. Thanks for taking the time to support this great app!