Support Forum

safihre wrote: ↑

August 27th, 2020, 4:03 pm

Well, I am the maintainer of the Synology package.. So guess I have work to do

Only takes a simple one-liner to mod the shebang to whatever you want:

So my initial guess was right. Best to leave it at /usr/bin/python3, which works in most cases. If the script comes as part of a package (don't have synology stuff around to try but the path /var/packages/sabnzbd/target/var/scripts/Deobfuscate.py does suggests so) and the system uses non-standard lo...

pven wrote: ↑

August 25th, 2020, 3:51 am

nice: can't execute '/var/packages/sabnzbd/target/var/scripts/Deobfuscate.py': No such file or directory

The No such file or directory part could also be referring to whatever is in the shebang line inside the script, for example an outdated or otherwise incorrect path to a python interpreter.

The sabnzbdplus package is not some wrapper around git. You cannot update sab by running 'git pull' unless you're running from git source.

Nice to see thing worked out. Using the init.d service that comes with the package - as you eventually did - had the side effect of letting you benefit from the sane environment it sets up. Basically, LANG is taken from /etc/default/locale (if defined), and PYTHONIOENCODING hardcoded to utf-8 to get...

Indeed just changing the default completed dir (and any such directories you set for categories) should do.

You might want to change that watched dir though, so it's separate from incomplete and complete dirs (e.g. F:\Downloads\WatchDir).

Recent changes to the way the interface templates communicate with the program backend may result in such errors after an upgrade if you didn't restart the application (and maybe clean browser cache). Was there a python traceback or other information on screen when you got this error?

The line sander mentioned is the correct one. That said: ymmv when trying to start a program in the clean environment system service use, when that program needs a bunch of modules installed with pip in a user context.

It's possible to select the version to install on the command line, e.g. sudo apt-get install sabnzbdplus=2.3.* but it would still be an uphill battle in a best case scenario, with python2 versions of both yenc and sabyenc missing for sure and possible some other pretty much essential modules as wel...

Happyeyeballs returning None is a bug caused by a hardcoded tls version (issue #1396 on github fixed in commit 26e1a72 ). That code is used to try to determine the optimal server ip to connect to, but its failure shouldn't prevent sab from connecting anyway. Did you setup us.newsdemon.com with a low...

The py3 version works fine as a daily driver. Even the sabnzbdplus package in ubuntu 20.04 is based on a (pre alpha1) git snapshot, alpha2 is currently on the ppa (in turn used by 3rd party docker setups). None of that caused an avelanche of a bug reports either. Just go for it.

The email issue is caused a typo in a packaging-specific patch, will be fixed in the alpha2 package. Thanks for reporting.

As far as I can tell every sab function continues to work just fine, daemon mode included. There's only the possibility of a (probably minor) resource leak until the sab parent process eventually exits and that zombie process disappears with it.

I suspect this is one of the cases where sab doesn't close file/process handles. Looking at recent github issues and commits, Sanderjo is on a mission to hunt these down.

Nzbfinder is an indexer, not a usenet server. You mistakenly configured nzbfinder as a usenet server in sabnzbd. That isn't going to work.