Mylar sends nzb so Sab and does not show up in downloads

[shawndaddy]

I have sabnzbd setup on a freenas and has been running well with all programs (cp, sickbeard, headphones, and mylar). The problem started last week with mylar. Mylar says it has snatched an nzb and says it has added to sabnzbd. The nzb never shows up in Sab and it doesn't give any errors. I have tried deleting and reinstalling both programs, but it still is doing the same thing. Thanks for any help that can be provided.

[shypike]

Enable debug logging in SABnzbd and look in the log file
whether an API calls actually comes from the other programs.

[shawndaddy]

I have attached my log file minus my api when Mylar sends a nzb. Can you take a look at it.

2015-07-10 17:36:51,448::DEBUG::[interface:421] API-call from 192.168.1.53 [python-requests/2.7.0 CPython/2.7.9 FreeBSD/9.1-RELEASE] {'apikey': '*******************************', 'name': '/var/db/mylar/cache/The.Walking.Dead.144.2015.Digital.Zone-Empire.nzb', 'script': 'ComicRN.py', 'cat': 'Comics', 'priority': '1', 'mode': 'addlocalfile'}

[shypike]

For "addlocalfile", the sent path much reachable locally.
Are you sure that the listed path is there?
Is there any error message a bit further down the log?

[sander]

Shypike, I played a bit with this, and I don't see the result of the API call in the logging.

API-call:

Code: Select all

$ curl 'http://localhost:8080/api?mode=addlocalfile&name=full/local/path/to/file.ext&pp=1&script=script.cmd&priority=-1'
error: file does not exist

The log just says there is an API call, but not what the result is:

Code: Select all

2015-07-12 16:05:49,564::DEBUG::[interface:423] API-call from 127.0.0.1 [curl/7.38.0] {'priority': u'-1', 'pp': u'1', 'mode': u'addlocalfile', 'name': u'full/local/path/to/file.ext', 'script': u'script.cmd'}

So I changed the code in sabnzbd/api.py (def _api_addlocalfile(name, output, kwargs):), resulting in:

Code: Select all

2015-07-12 16:07:40,876::DEBUG::[interface:423] API-call from 127.0.0.1 [curl/7.38.0] {'priority': u'-1', 'pp': u'1', 'mode': u'addlocalfile', 'name': u'full/local/path/to/file.ext', 'script': u'script.cmd'}
2015-07-12 16:07:40,876::DEBUG::[api:370] API-call result: file does not exist

Maybe that is a useful code change?

[shypike]

Of course better error messages are always a good idea.
I'll check this out.

[sander]

@shawndaddy

1) Are SABnzb and mylar running on the same device, so your FreeNAS
2) On the device, what is the output of "ls -al /var/db/mylar/cache/The.Walking*"?

Two questions, so two answers please.

[evilhero]

I'll chime in here - this is probably a problem with Mylar in relation to how it sends items to SAB.

There were numerous problems from users (of Mylar) that caused us to change the way mylar sends nzbs to SAB - from using the addurl option to the addlocalfile. In doing so, there was also an issue with users who ran SAB and Mylar on separate machines - but at this point a vast majority of these types of problems have been resolved in the latest development commit on github for mylar. That being said the FreeNAS plugin is tied to the Master branch.

Mylar now has gone back to using the addurl option, but first downloads the nzb to the local cache directory. It then opens up a temporary api call into itself (called downloadNZB which references back to the local cache nzb file) and sends that api url call to SAB as the addurl option. This gets around the different machines problem as well as allowing Mylar to check the nzb for alternate naming within the file. However in some cases, the url it throws back to SAB to retrieve has an ip of 0.0.0.0 which fails on setups where Mylar and SABnzbd are on different machines.

Basically, @shawndaddy - post your issue on github/mylar forums and I can help you out as there's probably no need to involve these folks in troubleshooting this, since it's not a problem with SABnzbd

[shypike]

I'll chime in here - this is probably a problem with Mylar in relation to how it sends items to SAB.

Thanks for your fine explanation.
Nevertheless, I have added some extra logging to "addlocalfile" and "addurl"
so that this type of problem is a bit easier to diagnose.