Updated to Sabnzbd 4.3.2 and now cant download [Debian]

[Dold5000]

I updated to sabnzbd 4.3.2 and im getting two error codes

ERROR Essential modules are missing, downloading cannot start.
ERROR SABCTools disabled: no correct version found! (Found v8.1.0, expecting v8.2.0)

Thank you in advance

[OneCD]

Hi, what environment please? Windows, Linux, NAS, etc...

[Dold5000]

Debian bookworm

[OneCD]

Ah, same as me.

Installed from source, package manager or something else?

[Dold5000]

That's awesome, a friend that helped me setup the server recommended debian and I'm glad I did it. Large learning curve but it runs smooth

I upgraded from a repo

Debian org one

Sorry can't post link because I'm a new user

[OneCD]

The SABnzbd GitHub repo?

edit: ah, just saw your update. I can't help with that one, so I'll have to let someone else have a shot at this.

[Dold5000]

Thank you

[jcfp]

If you updated from an official debian repository to 4.3.2, you must be using unstable (which is called that for a reason). Then again, that should also have the latest version of sabctools available; I uploaded both on Thursday:
https://tracker.debian.org/news/1533673/
https://tracker.debian.org/news/1533674/

Sometimes sabctools takes a bit longer to complete its build on all architectures, whereas sabnzbdplus only needs a single build, so things can be out of sync for a bit. Try updating all packages on your system again, and restart sab if necessary. The only major change in the new sab package was the inclusion of a native systemd service file, that reads the same config file as the good old init.d (/etc/default/sabnzbdplus) to determine the user and set a bunch of options. I don't expect that to cause an older version of sabctools to stick around.

If things still don't work out, provide the output of

Code: Select all

apt policy $pkgname

for both packages. Add some space to break up the url if the forum software blocks those.

[Red_48]

[SOLVED]
Since the 4.3.2 upgrade SABNZBD running in Docker consistently loses connection to Sonarr/Radarr, all newservers, and the HTTP GUI.

It operates for short periods and then fails with the following error:

Sonarr - "Test was aborted due to an error: Unable to connect to SABnzbd, Http request timed out"
Radarr - "Test was aborted due to an error: Unable to connect to SABnzbd, Http request timed out"
GUI - SAZnzbd is disconnected

SSL has never been selected

Steps taken:
1. Rebooted NAS
2. Confirmed IP, port, and API Keys are correct in Sonarr & Radarr.
3. Re-pulled the latest Docker images for Sonarr, Radarr, SABnzbd from 'linuxserver/sabnzbd:latest' (updated 11 hrs ago at time of writing).
4. Rebotted LAN equipment.
5. In Portainer (Docker GUI) I removed the SABnzbd container from the 'bridge' network and added it back again. It obtained the same IP address when re-added and appears to have solved the problem*

*In my environment I'm unable to add containers to the 'host' network for some reason.

[stravrosmanoli]

That's awesome, a friend that helped me setup the server recommended debian and I'm glad I did it. Large learning curve but it runs smooth

I upgraded from a repo

Debian org one

Sorry can't post link because I'm a new user

Thank you for this solution now 4.3.2 works i dont have to use the older release.