Skip to content
This repository

can't send nzb to sab #37

Closed
anomalousone opened this Issue September 30, 2012 · 10 comments

2 participants

anomalousone evilhero
anomalousone

Since the update that allowed selection of download priorities mylar hasn't been able to send nzbs to sabnzbd. I get the following error:

2012-09-30 09:16:52 ERROR Unable to send nzb file to SABnzbd
2012-09-30 09:16:46 INFO Sucessfully retrieved nzb file using nzb.su

Couchpotato and Headphones are running without a problem with the same settings. I've tried HTTP and HTTPS and have tried changing my port settings multiple times.

evilhero
Owner

I'm guessing from the 2 log lines that you chose not to select a priority in the configuration section and it's not working because of that. Newest commit has fixed that issue (if you don't select a priority, it will default to the normal priority), however if you're still having issues please give some more info - ie. post the console output as it will show traceback errors or other faults possibly.

anomalousone

Actually, I had tried several priorities; that's just the last setting I had attempted. I've updated to the latest commit and am still having the same issue. Here's the output from the mylar.log file:

30-Sep-2012 12:21:07 - INFO :: CP Server Thread-6 : Marking Batman issue: 12.00 as wanted...
30-Sep-2012 12:21:07 - INFO :: CP Server Thread-6 : Shhh be very quiet...I'm looking for Batman issue: 12.00 using experimental
30-Sep-2012 12:21:08 - INFO :: CP Server Thread-6 : I found 4 results doing my search...now I'm going to analyze the results.
30-Sep-2012 12:21:08 - INFO :: CP Server Thread-6 : Found Batman (2012) issue: 12 using experimental
30-Sep-2012 12:21:08 - INFO :: CP Server Thread-6 : Sucessfully retrieved nzb file using experimental
30-Sep-2012 12:21:13 - ERROR :: CP Server Thread-6 : Unable to send nzb file to SABnzbd
30-Sep-2012 12:21:13 - INFO :: CP Server Thread-6 : Shhh be very quiet...I'm looking for Batman issue: 12.00 using nzb.su
30-Sep-2012 12:21:14 - INFO :: CP Server Thread-6 : Found Batman (2012) issue: 12 using nzb.su
30-Sep-2012 12:21:14 - INFO :: CP Server Thread-6 : Sucessfully retrieved nzb file using nzb.su
30-Sep-2012 12:21:19 - ERROR :: CP Server Thread-6 : Unable to send nzb file to SABnzbd

I'm very sorry, but is that what you were calling the "console output"? I'm quite the n00b.

anomalousone

Also, forgot to mention, some kind of attempt at communication is happening in that sabnzbd is getting set to Paused when mylar tries to send a file, just no file makes it through.

evilhero
Owner

Ok, so it's possible that your SAB configuration is wrong. Here's some quick troubleshooting for you to try:
-Are you running a https version of SABnzbd ?
-How do you have your SAB Host set in the Mylar Configuration ?
-Do you have a category set in Mylar for comics (and is identical to one set in SABnzbd) ?
-Ensure that your API Key is correct (don't use the NZB key, the SABnzbd API key is what you need).

That's a good starting point at least...let me know :)

anomalousone

I actually triple-checked my SAB settings before I posted, to not bug you with something so basic. I've reinstalled, but still not working. So, I'm looking at the SAB settings again. They look good to me, but maybe something is off:
-SAB host: https://localhost:9095
-SAB category: comics (priority is set to high in SAB and Mylar; everything else in SAB is "Default")
-The API Key looked good, but I recopied it anyway.

Am I missing anything?

evilhero
Owner

Nope, it appears that it looks good based on your config. So next step is to use the search.py that's located in the test/ subfolder in the root of Mylar. Backup your exisiting search.py (in root of mylar/mylar), copy the test one into the place where the original one was, restart mylar and try again...console logging Is the console window (terminal window) it will have more detailed results with the 'debugging' search.py file being used.

anomalousone

Restarted with the 'debuggin' search.py. Doesn't seem like its providing any more information:

03-Oct-2012 20:23:02 - INFO :: CP Server Thread-4 : Marking Batman issue: 12.00
as wanted...
03-Oct-2012 20:23:02 - INFO :: CP Server Thread-4 : Shhh be very quiet...I'm loo
king for Batman issue: 12.00 using experimental
03-Oct-2012 20:23:03 - INFO :: CP Server Thread-4 : I found 4 results doing my s
earch...now I'm going to analyze the results.
03-Oct-2012 20:23:03 - INFO :: CP Server Thread-4 : Found Batman (2012) issue: 1
2 using experimental
03-Oct-2012 20:23:03 - INFO :: CP Server Thread-4 : Sucessfully retrieved nzb fi
le using experimental
03-Oct-2012 20:23:08 - ERROR :: CP Server Thread-4 : Unable to send nzb file to
SABnzbd
03-Oct-2012 20:23:08 - INFO :: CP Server Thread-4 : Shhh be very quiet...I'm loo
king for Batman issue: 12.00 using nzb.su
03-Oct-2012 20:23:09 - INFO :: CP Server Thread-4 : Found Batman (2012) issue: 1
2 using nzb.su
03-Oct-2012 20:23:09 - INFO :: CP Server Thread-4 : Sucessfully retrieved nzb fi
le using nzb.su
03-Oct-2012 20:23:14 - ERROR :: CP Server Thread-4 : Unable to send nzb file to
SABnzbd

What should I try next? Like I said before, this issue is specific to Mylar; I have Couch Potato and Headphones running without any problems, with the same settings. Thanks for all your help!

evilhero
Owner

Well what you posted was the log from within Mylar. The debugging search.py file throws all the verbose information to the console terminal window. And yes, Couch Potato, Headphones and Mylar might all seem somewhat related but really they all are using different logic within to grab the nzb's because of the differing nature.

Also do you have the Rename Files option checked off in the Mylar Configuration ? If you do (or don't) might further the investigation abit....

anomalousone

I had Rename Files checked. I thought I had read elsewhere that if you unchecked it, there could be problems. Once I unchecked it everything worked fine.

Just to make sure I didn't misunderstand you before, I had taken the search.py from the test directory and overwrote the one in the mylar directory. I then copied the text from the "DOS" window, not from within mylar. Was that not correct?

evilhero
Owner

No that was correct - although if you replaced the search.py the text is different, which makes me think something happened in that it wasn't overwritten. It should look like this:

04-Oct-2012 08:27:45 - INFO :: CP Server Thread-7 : Marking Batman issue: 12.00 as wanted...
04-Oct-2012 08:27:46 - INFO :: CP Server Thread-7 : Shhh be very quiet...I'm looking for Batman issue: 12.00 using experimental
04-Oct-2012 08:27:47 - INFO :: CP Server Thread-7 : I found 4 results doing my search...now I'm going to analyze the results.
Comic:batman beyond 012
year detected!
2012 - right - years match baby!
incorrect comic lengths...not a match
Comic:batman the dark knight 012
year detected!
2012 - right - years match baby!
incorrect comic lengths...not a match
Comic:batman and robin 012
year detected!
2012 - right - years match baby!
incorrect comic lengths...not a match
Comic:batman 012
year detected!
2012 - right - years match baby!
length match..proceeding
issue detected
this should be a match!
issues match!
cache directory set to: /home/hero/mylar/cache
savefile set to: /home/hero/mylar/cache/79339130.nzb
sucessfully retrieve nzb to : /home/hero/mylar/cache/79339130.nzb
sab host set to :http://localhost:9092
Queue paused
sab api string:http://localhost:9092/api?mode=addlocalfile&name=/home/hero/mylar/cache/79339130.nzb&pp=3&cat=comics&script=ComicRN.py&apikey
outqueue line generated
passed api request to SAB
there are 1 things in SABnzbd's queue
79339130
79339130
matched
slot_nzoid: SABnzbd_nzo__uER20
attempting to rename queue to http://localhost:9092/api?mode=queue&name=rename&apikey&value=SABnzbd_nzo__uER20&value2=Batman 12 (2011) (2012)

although this ends because of the spaces in the rename, you get the idea...you would have more output even prior to the attempted send to SAB with Rename Files unchecked :)

evilhero evilhero closed this October 30, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.