-
Notifications
You must be signed in to change notification settings - Fork 173
can't send nzb to sab #37
Comments
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. |
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... I'm very sorry, but is that what you were calling the "console output"? I'm quite the n00b. |
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. |
Ok, so it's possible that your SAB configuration is wrong. Here's some quick troubleshooting for you to try: That's a good starting point at least...let me know :) |
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: Am I missing anything? |
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. |
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 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! |
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.... |
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? |
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:
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 :) |
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.
The text was updated successfully, but these errors were encountered: