Post-processing with ComicRN failing

Post any problems / bugs / issues that are Mylar-related in here.
Aimhere
Posts: 95
Joined: Mon Apr 06, 2015 2:32 pm

Post-processing with ComicRN failing

Post by Aimhere » Sun Feb 18, 2018 7:56 pm

Hi,

After getting my web UI problem straightened out (thanks, evilhero!), I now have a new problem.

When post-processing, ComicRN is now failing, partial log taken from web UI below:

Code: Select all

Sun Feb 18 2018 13:37:38	Post-process-script ComicRN.py for X-Men.Gold.001.2017.Digital.Zone-Empire failed (terminated with unknown status)
info	Sun Feb 18 2018 13:37:38	ComicRN: ImportError: No module named requests
info	Sun Feb 18 2018 13:37:38	ComicRN: import requests
info	Sun Feb 18 2018 13:37:38	ComicRN: File "/volume1/@appstore/nzbget/share/nzbget/scripts/autoProcessComics.py", line 2, in <module>
info	Sun Feb 18 2018 13:37:38	ComicRN: import autoProcessComics
info	Sun Feb 18 2018 13:37:38	ComicRN: File "/usr/local/nzbget/share/nzbget/scripts/ComicRN.py", line 15, in <module>
info	Sun Feb 18 2018 13:37:38	ComicRN: Traceback (most recent call last):
It appears autoProcesscomics.py is unable to load a module called "requests". I see this module is referred to in the autoProcessComics.py on the development branch, but not on the master branch. What does this module do, and why can't my system find it? Where/how would I install it?

aimhere

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

Re: Post-processing with ComicRN failing

Post by evilhero » Sun Feb 18, 2018 9:02 pm

Requests is a module that is used by Python in order to make URL requests. It has some extra bells & whistles, along with security items that make it the defacto thing now to use.

I didn't even think about the non-requests users when I updated thre autoProcessComics.cfg file.

The easiest fix atm is to put back the original autoProcessComics.py file - it will still work as it's legacy.

If you want to install requests it's pretty simple - 'pip install requests' will do it on a basic level. If you do happen to go this route, you'll have to change your autoProcessComics.cfg file to accommodate the new workflow - username and password are no longer part the cfg, just the mylar apikey.

I'll try to do the flip back in the code and roll it out so it will work either way, but might be a day or so before I get it out.

EDIT. Update to the latest dev - and replace your existing autoProcessComics.py file with the newest one. You'll also have to change out your autoProcessComics.cfg so that you're using the one with the apikey and fill in that value (that's unavoidable - I was never fond of keeping user/pass' in plain txt files)

Aimhere
Posts: 95
Joined: Mon Apr 06, 2015 2:32 pm

Re: Post-processing with ComicRN failing

Post by Aimhere » Sun Feb 18, 2018 10:45 pm

Huzzah! I was just about to revert autoProcesscomics.py, but then I saw your post. Updated again, tried post-process again on a previous pp-failure, now ComicRN is succeeding.

Before all that, I did try 'pip install requests' from my python folder, and it appeared to complete successfully, but the (old) version of autoProcessComics.py was still saying it couldn't load requests. I think somehow I may have two revisions of Python 2.7 installed on my system (the one from SynoCommunity, and maybe one built-into DSM???)

aimhere

jedimole
Posts: 88
Joined: Sat Jan 02, 2016 9:19 pm

Re: Post-processing with ComicRN failing

Post by jedimole » Mon Feb 19, 2018 1:27 am

evilhero wrote:
Sun Feb 18, 2018 9:02 pm
Requests is a module that is used by Python in order to make URL requests. It has some extra bells & whistles, along with security items that make it the defacto thing now to use.

I didn't even think about the non-requests users when I updated thre autoProcessComics.cfg file.

The easiest fix atm is to put back the original autoProcessComics.py file - it will still work as it's legacy.

If you want to install requests it's pretty simple - 'pip install requests' will do it on a basic level. If you do happen to go this route, you'll have to change your autoProcessComics.cfg file to accommodate the new workflow - username and password are no longer part the cfg, just the mylar apikey.

I'll try to do the flip back in the code and roll it out so it will work either way, but might be a day or so before I get it out.

EDIT. Update to the latest dev - and replace your existing autoProcessComics.py file with the newest one. You'll also have to change out your autoProcessComics.cfg so that you're using the one with the apikey and fill in that value (that's unavoidable - I was never fond of keeping user/pass' in plain txt files)

Im confused here, do I need to change the cfg file?

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

Re: Post-processing with ComicRN failing

Post by evilhero » Mon Feb 19, 2018 2:48 am

It's a bit more involved depending on your workflow.

If you aren't using forms authentication in Mylar, you can just keep your existing autoProcessComics.cfg, and autoProcessComics.cfg files (since odds are they're seperate from the mylar install unless you symlinked them).

If you're using forms authentication with mylar, then you have no choice but to use the new versions of both the autoProcessComics.cfg and autoProcessComics.py files. In the .cfg, the only new aspect is the inclusion of the apikey now, and the removal of the username and password fields. Everything else is identical. So if you don't have an apikey generated within Mylar, you need to do that first - otherwise you would just put the existing apikey into new autoProcessComics.cfg file.

Note that in either of these workflows, if you use completed download handling within Mylar, this change has no effect - since you can't use comicrn with completed download handling enabled it bypasses all of these issues.

jedimole
Posts: 88
Joined: Sat Jan 02, 2016 9:19 pm

Re: Post-processing with ComicRN failing

Post by jedimole » Tue Feb 20, 2018 4:16 pm

Ok, maybe I missed something on the upgrade in dev, but post processing and pushbullet are both dead now. I have been using this for so long with no issues, I guess I forget what I might have added to make this all work?

I don't want to take to much time with troubleshooting if I need to look at a guide I will!

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

Re: Post-processing with ComicRN failing

Post by evilhero » Wed Feb 21, 2018 3:28 pm

You need to indicate more clearly as to what is broken and give the resulting logs showing what it is that's broken. Unfortunately just saying that something is dead isn't helpful, as there are lots of us that are running it with no problems (granted the last big commit caused some issues, but they're being worked thru) - so without seeing a cause & effect workflow, it makes it really difficult to test seeing as how it can't be replicated currently by myself.

jedimole
Posts: 88
Joined: Sat Jan 02, 2016 9:19 pm

Re: Post-processing with ComicRN failing

Post by jedimole » Wed Feb 21, 2018 4:29 pm

Totally understand. I went to readme’s and github to see if I needed to update nzb scripts in Mylar but didn’t see anything obvious. I’ll post more logs when I get home!

jedimole
Posts: 88
Joined: Sat Jan 02, 2016 9:19 pm

Re: Post-processing with ComicRN failing

Post by jedimole » Fri Feb 23, 2018 7:35 pm

and all back to normal! Not sure what was hosing things

Thanks again

Rumik
Posts: 17
Joined: Sat Jul 22, 2017 12:21 pm

Re: Post-processing with ComicRN failing

Post by Rumik » Thu May 31, 2018 9:27 am

Hey there,

My ComicsRN has been acting up for a while (stalling and holding up the nzbget queue) so I thought upgrade to the latest version of this and the cfg file, but I have no idea how to install the Python Requests module on my QNAP. So I would like to go back to the of version that doesn't use the Mylar Api... I can't find a download for it tho. Can you help?

Thanks!

Post Reply