Page 6 of 6

Re: [PP-Script] NotifyPlex - Library Update and GUI Notifica

Posted: 02 Sep 2016, 04:41
by hugbug
You don't need debug version of nzbget. You need to modify the script and add extra log messages around the message in question to understand why the script thinks that download has failed.

Re: [PP-Script] NotifyPlex - Library Update and GUI Notifica

Posted: 02 Sep 2016, 07:27
by konubywy
Unfortunately for me, that is actually beyond my skillset to do such a thing :cry:

Re: [PP-Script] NotifyPlex - Library Update and GUI Notification

Posted: 30 Aug 2019, 22:23
by fleXible
From time to time I experienced the same problem, but wasn't big enough to dive into it. Till yesterday...

In line 108 the status is checked for "SUCCESS/ALL" to determine whether to notify the plex server.
But according to the nzbget documentation at https://nzbget.net/api/history there are more status signalling success.

Change the line to:

Code: Select all

ppStatus = os.environ['NZBPP_STATUS'].startswith('SUCCESS/')
Tell me, if it works

Re: [PP-Script] NotifyPlex - Library Update and GUI Notification

Posted: 23 Sep 2019, 23:12
by fleXible

Re: [PP-Script] NotifyPlex - Library Update and GUI Notification

Posted: 20 Aug 2020, 00:21
by mannibis
I have added python3 compatibility and also started to store the auth_token to disk, so that the script does not sign-in with plex.tv every time it is ran. The auth_token will be re-used after the initial sign-in.

I have also created a GitHub repo here: https://github.com/mannibis/NotifyPlex in case anyone wants the newest version

Re: [PP-Script] NotifyPlex - Library Update and GUI Notification

Posted: 12 Sep 2020, 20:05
by mouzzampk2014
Hi all,

Need little guidance. I am using linuxserver/nzbget image and getting this message. Thank you

Code: Select all

Executing script NotifyPlex/NotifyPlex.py with command ConnectionTest
NotifyPlex: Fixing permissions for/shared/downloads/usenet/scripts/NotifyPlex/NotifyPlex.py
NotifyPlex: Traceback (most recent call last):
NotifyPlex:   File "/shared/downloads/usenet/scripts/NotifyPlex/NotifyPlex.py", line 102, in <module>
NotifyPlex:     import requests
NotifyPlex: ModuleNotFoundError: No module named 'requests'
Script NotifyPlex/NotifyPlex.py with command ConnectionTest failed (terminated with unknown status)

Re: [PP-Script] NotifyPlex - Library Update and GUI Notification

Posted: 14 Sep 2020, 13:49
by owine
mouzzampk2014 wrote:
12 Sep 2020, 20:05
Hi all,

Need little guidance. I am using linuxserver/nzbget image and getting this message. Thank you

Code: Select all

Executing script NotifyPlex/NotifyPlex.py with command ConnectionTest
NotifyPlex: Fixing permissions for/shared/downloads/usenet/scripts/NotifyPlex/NotifyPlex.py
NotifyPlex: Traceback (most recent call last):
NotifyPlex:   File "/shared/downloads/usenet/scripts/NotifyPlex/NotifyPlex.py", line 102, in <module>
NotifyPlex:     import requests
NotifyPlex: ModuleNotFoundError: No module named 'requests'
Script NotifyPlex/NotifyPlex.py with command ConnectionTest failed (terminated with unknown status)
You can either configure your Docker container to install the required pip module at container start or download the source for the requests module from https://pypi.org/project/requests/#files and save the enclosing folder entitled requests in the same folder as NotifyPlex.py.

Re: [PP-Script] NotifyPlex - Library Update and GUI Notification

Posted: 07 Oct 2020, 15:38
by fleXible
Need little guidance. I am using linuxserver/nzbget image and getting this message. Thank you
I just had a quick look at the image you use. Regarding installed software packages it comes just with the bare minimum. For python not even pip is available. Weird thing is, while building the docker image, it was installed, but got removed as a "development dependency".

To reinstall pip and a bunch of other widely used modules, you can use this command:

Code: Select all

docker exec -it nzbget apk add py3-pip
This will keep working even across container restarts.

I wouldn't recommend putting modules inside the script directory. In the long-run it will lead to weird dependency problems and upgrading is short of impossible.