Need some help with sabnzbdplus on Ubuntu 22.04

[sastek]

Hi, I'm hoping someone can steer me in the right direction here.

A couple of years ago I setup sab on a Ubuntu 20 VPS. Everything ran great until I upgraded to 22.04 yesterday, then sab stopped working.

I was going to just try uninstalling sabnzbdplus and reinstall it again, but when I try to remove it with "apt remove sabnzbdplus" I get an error saying Package 'sabnzbdplus' is not installed, so not removed. Now I was convinced that I had used the recommended JCFP method to install sabnzbdplus, I have the jcfp repository installed, and the init file /etc/init.d/sabnzbdplus contents says copyright jcfp. So now I'm wondering how I actually installed it back then and why I can't uninstall it now.

Some other info on the problem is that "systemctl status sabnzbdplus" says that it is running, but I can't connect with a browser, and there is nothing in the sabnzbd.log since yesterday. So it looks like it isn't actually running right.

Can anyone advise me on how to proceed here? There may be a simple solution, but I'm not hugely competent with Ubuntu, especially when it's something I did years ago.

[sander]

What is the output of:

Code: Select all

sudo ps -ef | grep -i sabnzbd

[jcfp]

Doing ubuntu upgrades the official way disables third-party repositories such as PPAs as a precaution, and they may well choose to remove packages installed from there as well. The files under /etc are considered configuration files and remain on the system after uninstalling the package that put them there. And by design, the init.d will handle that situation gracefully, which in turn can make it appear as if systemd is saying the program should be runnning even though it isn't.

Long story short: you probably just need to redo the ppa setup and install sabnzbdplus - then it all works again, system service and your old settings included.

[sastek]

Thanks jcfp, that was my problem. I'll need to try to remember that for the upcoming ubuntu 24 release.

Everything is working fine again, except that I'm now getting an error " Exit(127): /usr/bin/env: ‘python’: No such file or directory" I assume that's a problem with nzbToMedia and python versions

[jcfp]

Plain "python" refers to python2 in every mainstream linux distribution, which has been replaced by python3 by now. You'll have to fix or update whatever scripts your setup uses.

[sastek]

Yeah thanks, I've got it fixed.

[NotANoobLol]

Long story short: you probably just need to redo the ppa setup and install sabnzbdplus - then it all works again, system service and your old settings included.

I always get the error, that GPG can't find a key for the repository, when I try to enable your ppa.

Code: Select all

$ sudo add-apt-repository ppa:jcfp/nobetas

Code: Select all

 Exactly the same as https://launchpad.net/~jcfp/+archive/ubuntu/ppa but without alpha, beta or rc releases (and with the occasional extra delay thrown in for free!). Dermatologically tested. Compatible with cucumber water diets.
 More info: https://launchpad.net/~jcfp/+archive/ubuntu/nobetas
Press [ENTER] to continue or ctrl-c to cancel adding it

gpg: Die "Keybox" `/tmp/tmpsatsivgn/pubring.gpg' wurde erstellt
gpg: /tmp/tmpsatsivgn/trustdb.gpg: trust-db erzeugt
gpg: Schlüssel F13930B14BB9F05F: Öffentlicher Schlüssel "Launchpad PPA for jcfp" importiert
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
gpg:                              importiert: 1
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
gpg: Keine gültigen OpenPGP-Daten gefunden.

I'm on debian 11 (Bullseye). I don't really understand what i am supposed to do

[jcfp]

I always get the error, that GPG can't find a key for the repository, when I try to enable your ppa.
[...]
I'm on debian 11 (Bullseye). I don't really understand what i am supposed to do

For starters, you probably don't want to use the PPA on debian. That said, with the gpg key you might be running into deprecation of 1024 bit keys that Launchpad still uses for signing PPAs at the moment, see https://github.com/sabnzbd/sabnzbd/issu ... 2085383403 for details. You could try to grab the key from keyserver.ubuntu.com and import it manually (sudo apt-key add FILENAME), maybe that gives you a more useful error message.

[NotANoobLol]

I always get the error, that GPG can't find a key for the repository, when I try to enable your ppa.
[...]
I'm on debian 11 (Bullseye). I don't really understand what i am supposed to do

For starters, you probably don't want to use the PPA on debian. That said, with the gpg key you might be running into deprecation of 1024 bit keys that Launchpad still uses for signing PPAs at the moment, see https://github.com/sabnzbd/sabnzbd/issu ... 2085383403 for details. You could try to grab the key from keyserver.ubuntu.com and import it manually (sudo apt-key add FILENAME), maybe that gives you a more useful error message.

Thank you for the link to the issue, I didnt see that.

But why shouldn't I use the ppa?
The alternative in the backlog does only have version sabnzbdplus/bullseye-backports 3.7.1+dfsg-1~bpo11+1 all available too.
This corresponds to: https://qa.debian.org/madison.php?packa ... s=&text=on#

Maybe I'm misunderstanding something in what I need to do? How do I get the sid Package? Is this even an official one? I'm well confused to be honest.

[jcfp]

But why shouldn't I use the ppa?

Because the PPA targets Ubuntu. The packages provided there - especially the architecture-dependent ones such as sabctools - are not binary compatible with Debian.

The alternative in the backlog does only have version sabnzbdplus/bullseye-backports 3.7.1+dfsg-1~bpo11+1 all available too.
This corresponds to: https://qa.debian.org/madison.php?packa ... s=&text=on#

Maybe I'm misunderstanding something in what I need to do? How do I get the sid Package? Is this even an official one? I'm well confused to be honest.

Backports provided by the Debian project come with the same safeguards as regular packages, use the same build daemons, mirror infrastructure, etc, so in that sense packages there are "official" - unlike PPAs that can be setup by anyone.

Sabnzbdplus in bullseye-backports is "stuck" at 3.7.1 because these official backports cannot move beyond the version packaged in the next Debian release (bookworm), to ensure a clean upgrade path without the use of bookworm-backports. Now if you don't care about that last bit, 4.2.2 is available in bullseye-backports-sloppy (4.2.3 was uploaded a month or so ago but they are taking their sweet time approving that...).