Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings.
Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Everything seems to be installed and the right version but sab still does not recognize or accept it. I do not have python3/pip3 installed as it was the case in another thread here.
Any hints are much appreciated.
Why don't you use the SynoCommunity package?
It comes with the correct SABYenc.
But it seems to be a classic case of multiple python's installed.
You should find the one that runs SABnzbd, I think it should be listed on the first page of the Config.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
I would love to use the synocommunity pkg (especially for multicore par which is also not found by sab but that is another topic) but it is not available for the 718+ although it has a x86 cpu. I don't know why. Pkg selection for the 718 is VERY limited. Not even git is available.
On the config page it says: Python Version: 2.7.13 (default, Sep 25 2017, 23:51:57) [GCC 6.3.0] [UTF-8]
Is there any way to see the python path sab uses? Above i used my sab user to execute the commands and when i start sab from the same session it should have the same environment as the user that executes the command. So sab should be using the above listed python with the sabyenc module. At least that is my understanding. Please correct me if i am wrong.
my sabyenc is in /volume1/@entware/lib/python2.7/site-packages and which python gives /opt/bin/python if that helps.
Ok got it.
Do not understand it but it works (i have no clue how i ended up with two python installs).
/opt/bin/python was just a symlink to /opt/bin/python2.7.
Redirecting that link to /volume1/@entware/bin/python2.7 worked.
Not really problems with running the packages, but installing goes wrong for new systems.
Older synology systems that were updated from older DSM versions work, new installations only half of the time.
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate