Sabnzbd not working after upgrading from 4.0.0 to 4.0.3

[jemcleod]

I tried to upgrade to the latest sabnzbd and the page will not load. I get the following in the logs. I installed python 3 so not sure what's going on. This is on a Synology NAS.

Not all required Python modules are available, please check requirements.txt

Missing module: sabctools

You can read more at: https://sabnzbd.org/wiki/installation/i ... ff-modules

If you still experience problems, remove all .pyc files in this folder and subfolders

python3 --version
Python 3.8.15

[safihre]

If you are on Synology, why not use the SynoCommunity package?

[jemcleod]

If you are on Synology, why not use the SynoCommunity package?

That is an option but I prefer to use docker. I've had no issues that way up until this version.

[sander]

You use docker, and you get that error message?! Seems impossible to me. Which sabnzbd docker image are you using?

[jemcleod]

You use docker, and you get that error message?! Seems impossible to me. Which sabnzbd docker image are you using?

I know ive never run into issues using docker. I get the image from linuxserver and always have.

https://registry.hub.docker.com/r/linuxserver/sabnzbd/

[sander]

Code: Select all

sudo docker pull lscr.io/linuxserver/sabnzbd:latest # force refresh image
sudo docker run lscr.io/linuxserver/sabnzbd:latest # and run it

which shows in the logging:

Code: Select all

SABnzbd.py-4.0.3
SABCTools module (v7.0.2)... found!

So ... all good. It just works.

Could it be a PEBKAC? For example: not updating the container image, or still running the non-docker version?

Post your sabnzbd.log, like below, and certainly the line "Dockerized = "

Code: Select all

[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗ 
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝ 

   Brought to you by linuxserver.io
───────────────────────────────────────

To support the app dev(s) visit:
SABnzbd: https://sabnzbd.org/donate

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    911
User GID:    911
───────────────────────────────────────

[custom-init] No custom files found, skipping...

2023-08-05 14:30:34,039::INFO::[SABnzbd:1171] --------------------------------
2023-08-05 14:30:34,039::INFO::[SABnzbd:1172] SABnzbd.py-4.0.3
2023-08-05 14:30:34,039::INFO::[SABnzbd:1182] Commit = 9fafe64cff631ea6c61e65780f366046b2830108
2023-08-05 14:30:34,039::INFO::[SABnzbd:1184] Full executable path = /app/sabnzbd/SABnzbd.py
2023-08-05 14:30:34,040::INFO::[SABnzbd:1185] Arguments = "/app/sabnzbd/SABnzbd.py" "--config-file" "/config" "--server" "::"
2023-08-05 14:30:34,040::INFO::[SABnzbd:1186] Python-version = 3.11.4 (main, Jun  9 2023, 02:29:05) [GCC 12.2.1 20220924]
2023-08-05 14:30:34,040::INFO::[SABnzbd:1187] Dockerized = True

2023-08-05 14:30:34,057::INFO::[SABnzbd:425] SABCTools module (v7.0.2)... found!
2023-08-05 14:30:34,057::INFO::[SABnzbd:426] SABCTools module is using SIMD set: AVX512VL+VBMI2
2023-08-05 14:30:34,057::INFO::[SABnzbd:427] SABCTools module is linked to OpenSSL: True

[jemcleod]

Code: Select all

sudo docker pull lscr.io/linuxserver/sabnzbd:latest # force refresh image
sudo docker run lscr.io/linuxserver/sabnzbd:latest # and run it

which shows in the logging:

Code: Select all

SABnzbd.py-4.0.3
SABCTools module (v7.0.2)... found!

So ... all good. It just works.

Could it be a PEBKAC? For example: not updating the container image, or still running the non-docker version?

Post your sabnzbd.log, like below, and certainly the line "Dockerized = "

Code: Select all

2023-08-05 14:30:34,039::INFO::[SABnzbd:1171] --------------------------------
2023-08-05 14:30:34,039::INFO::[SABnzbd:1172] SABnzbd.py-4.0.3
2023-08-05 14:30:34,039::INFO::[SABnzbd:1182] Commit = 9fafe64cff631ea6c61e65780f366046b2830108
2023-08-05 14:30:34,039::INFO::[SABnzbd:1184] Full executable path = /app/sabnzbd/SABnzbd.py
2023-08-05 14:30:34,040::INFO::[SABnzbd:1185] Arguments = "/app/sabnzbd/SABnzbd.py" "--config-file" "/config" "--server" "::"
2023-08-05 14:30:34,040::INFO::[SABnzbd:1186] Python-version = 3.11.4 (main, Jun  9 2023, 02:29:05) [GCC 12.2.1 20220924]
2023-08-05 14:30:34,040::INFO::[SABnzbd:1187] Dockerized = True

2023-08-05 14:30:34,057::INFO::[SABnzbd:425] SABCTools module (v7.0.2)... found!
2023-08-05 14:30:34,057::INFO::[SABnzbd:426] SABCTools module is using SIMD set: AVX512VL+VBMI2
2023-08-05 14:30:34,057::INFO::[SABnzbd:427] SABCTools module is linked to OpenSSL: True

It could be if I am the only one seeming to have issues which is what I wanted to confirm. I am literally using the Synology Docker in GUI to download the image and update it via Action >> Reset. I will try it via CLI and see what happens.

[jemcleod]

So I tested on my Synology which is on DSM6 still and no issues. I will upgraded it to DSM7 and ran into the same issues my other NAS is having which is on that version. Time to go digging.

[jemcleod]

I just found this, its from 2 years ago. Will need to look more into this, looks to be a synology issue.

viewtopic.php?t=25474

[safihre]

That's about the SynoCommunity package, unrelated to Docker.
You could just add the Docker image again and start fresh instead of reset.
Many many people run SABnzbd as a Docker on Synology without problems.

[jemcleod]

That's about the SynoCommunity package, unrelated to Docker.
You could just add the Docker image again and start fresh instead of reset.
Many many people run SABnzbd as a Docker on Synology without problems.

100% ive never had issues up to now. I run everything (radarr, sonarr, tautulli etc) in a docker and have recently updates those with no issues. I've deleted the sabnzbd folder and container and started from fresh and still keep getting this same issue. I will keep investigating what is happening here.

[sander]

Did you read my advice 'Post your sabnzbd.log, like below, and certainly the line "Dockerized = " ' ?

[jemcleod]

Did you read my advice 'Post your sabnzbd.log, like below, and certainly the line "Dockerized = " ' ?

Apologies I missed your last line in your message. This is running the 4.0.0. Trying to run the latest sabnzbd image, I dont see any logs in sabnzbd, just in the docker terminal on synology where I saw those errors.

Code: Select all

2023-08-03 16:43:58,256::INFO::[SABnzbd:1168] --------------------------------
2023-08-03 16:43:58,271::INFO::[SABnzbd:1169] SABnzbd.py-4.0.0
2023-08-03 16:43:58,271::INFO::[SABnzbd:1179] Commit = 5e42e25617150256dee23c08fa6f78e2502e46f7
2023-08-03 16:43:58,271::INFO::[SABnzbd:1181] Full executable path = /app/sabnzbd/SABnzbd.py
2023-08-03 16:43:58,271::INFO::[SABnzbd:1182] Arguments = "/app/sabnzbd/SABnzbd.py" "--config-file" "/config" "--server" "::"
2023-08-03 16:43:58,272::INFO::[SABnzbd:1183] Python-version = 3.10.11 (main, Apr  6 2023, 01:16:54) [GCC 12.2.1 20220924]
2023-08-03 16:43:58,272::INFO::[SABnzbd:1184] Dockerized = True

2023-08-03 16:43:58,349::INFO::[SABnzbd:423] SABCTools module (v7.0.1)... found!
2023-08-03 16:43:58,349::INFO::[SABnzbd:424] SABCTools module is using SIMD set: SSSE3
2023-08-03 16:43:58,350::INFO::[SABnzbd:425] SABCTools module is linked to OpenSSL: True

[jemcleod]

Yeh so it was PEBKAC after all. I had the 4.0.0 image and had exported it (not the latest). When I went to download the latest image and create the new sabnzbd container, I imported that sabnzbd.syno.json file which had all my settings, but it referenced the 4.0.0 image.

Code: Select all

"build_version" : "Linuxserver.io version:- 4.0.0-ls104 Build-date:- 2023-04-28T09:00:21-05:00",
      "maintainer" : "thespad",
      "org.opencontainers.image.authors" : "linuxserver.io"

Code: Select all

2023-08-05 16:06:04,206::INFO::[SABnzbd:1171] --------------------------------
2023-08-05 16:06:04,221::INFO::[SABnzbd:1172] SABnzbd.py-4.0.3
2023-08-05 16:06:04,221::INFO::[SABnzbd:1182] Commit = 9fafe64cff631ea6c61e65780f366046b2830108
2023-08-05 16:06:04,221::INFO::[SABnzbd:1184] Full executable path = /app/sabnzbd/SABnzbd.py
2023-08-05 16:06:04,222::INFO::[SABnzbd:1185] Arguments = "/app/sabnzbd/SABnzbd.py" "--config-file" "/config" "--server" "::"
2023-08-05 16:06:04,222::INFO::[SABnzbd:1186] Python-version = 3.11.4 (main, Jun  9 2023, 02:29:05) [GCC 12.2.1 20220924]
2023-08-05 16:06:04,222::INFO::[SABnzbd:1187] Dockerized = True

2023-08-05 16:06:04,337::INFO::[SABnzbd:425] SABCTools module (v7.0.2)... found!
2023-08-05 16:06:04,337::INFO::[SABnzbd:426] SABCTools module is using SIMD set: SSSE3
2023-08-05 16:06:04,337::INFO::[SABnzbd:427] SABCTools module is linked to OpenSSL: True

All good now.

[rohanzx67]

I took the opportunity of this release to finally migrate from NZBGet back to Sab. Took about 15 minutes and everything is working great. It is a much more polished piece of software than the version I used 5+ years ago.