I have sabnzbd running as a service on my Raspberry Pi 4 running Dietpi. I updated sabnzbd to 4.0.0 version and now I can’t access it on my network. I have confirmed in Dietpi that the sabnzbd service is running but when I try to access it via http://192.168.xx.xx:8080/sabnzbd/ (where it normally sits) I am unable to connect. I have radarr and sonarr also running on this box and I’m able to access those services fine. Am I missing something?
Correction. Looks like the service isn’t able to start. I’ve tried to get this to start multiple times manually using DietPi-Services and I keep getting this. How do I get the service to start?
● sabnzbd.service - SABnzbd (DietPi)
Loaded: loaded (/etc/systemd/system/sabnzbd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2023-04-28 20:53:54 BST; 9s ago
Docs: https://sabnzbd.org/wiki/
Process: 31367 ExecStart=/usr/bin/python3 -OO /etc/sabnzbd/SABnzbd.py -f /etc/sabnzbd/sabnzbd.ini -n --disable-file-log (code=exited, status=1/FAILURE)
Main PID: 31367 (code=exited, status=1/FAILURE)
Apr 28 20:53:54 NAS systemd[1]: sabnzbd.service: Service RestartSec=100ms expired, scheduling restart.
Apr 28 20:53:54 NAS systemd[1]: sabnzbd.service: Scheduled restart job, restart counter is at 5.
Apr 28 20:53:54 NAS systemd[1]: Stopped SABnzbd (DietPi).
Apr 28 20:53:54 NAS systemd[1]: sabnzbd.service: Start request repeated too quickly.
Apr 28 20:53:54 NAS systemd[1]: sabnzbd.service: Failed with result 'exit-code'.
Apr 28 20:53:54 NAS systemd[1]: Failed to start SABnzbd (DietPi).
Apr 28 20:53:55 NAS systemd[1]: sabnzbd.service: Start request repeated too quickly.
Apr 28 20:53:55 NAS systemd[1]: sabnzbd.service: Failed with result 'exit-code'.
Apr 28 20:53:55 NAS systemd[1]: Failed to start SABnzbd (DietPi).
can you check system log
journalctl -u abnzbd.service
-- Logs begin at Thu 2019-02-14 10:12:00 GMT, end at Fri 2023-04-28 21:33:19 BST. --
Apr 28 21:05:47 NAS systemd[1]: Started SABnzbd (DietPi).
Apr 28 21:05:48 NAS SABnzbd[449]: File "/etc/sabnzbd/SABnzbd.py", line 403
Apr 28 21:05:48 NAS SABnzbd[449]: if home := os.environ.get("HOME"):
Apr 28 21:05:48 NAS SABnzbd[449]: ^
Apr 28 21:05:48 NAS SABnzbd[449]: SyntaxError: invalid syntax
Apr 28 21:05:48 NAS systemd[1]: sabnzbd.service: Main process exited, code=exited, status=1/FAILURE
Apr 28 21:05:48 NAS systemd[1]: sabnzbd.service: Failed with result 'exit-code'.
Apr 28 21:05:48 NAS systemd[1]: sabnzbd.service: Service RestartSec=100ms expired, scheduling restart.
Apr 28 21:05:48 NAS systemd[1]: sabnzbd.service: Scheduled restart job, restart counter is at 1.
Apr 28 21:05:48 NAS systemd[1]: Stopped SABnzbd (DietPi).
Apr 28 21:05:48 NAS systemd[1]: Started SABnzbd (DietPi).
Apr 28 21:05:48 NAS SABnzbd[477]: File "/etc/sabnzbd/SABnzbd.py", line 403
Apr 28 21:05:48 NAS SABnzbd[477]: if home := os.environ.get("HOME"):
Apr 28 21:05:48 NAS SABnzbd[477]: ^
Apr 28 21:05:48 NAS SABnzbd[477]: SyntaxError: invalid syntax
Apr 28 21:05:48 NAS systemd[1]: sabnzbd.service: Main process exited, code=exited, status=1/FAILURE
Apr 28 21:05:48 NAS systemd[1]: sabnzbd.service: Failed with result 'exit-code'.
Apr 28 21:05:49 NAS systemd[1]: sabnzbd.service: Service RestartSec=100ms expired, scheduling restart.
Apr 28 21:05:49 NAS systemd[1]: sabnzbd.service: Scheduled restart job, restart counter is at 2.
Apr 28 21:05:49 NAS systemd[1]: Stopped SABnzbd (DietPi).
Apr 28 21:05:49 NAS systemd[1]: Started SABnzbd (DietPi).
Apr 28 21:05:49 NAS SABnzbd[478]: File "/etc/sabnzbd/SABnzbd.py", line 403
Apr 28 21:05:49 NAS SABnzbd[478]: if home := os.environ.get("HOME"):
Apr 28 21:05:49 NAS SABnzbd[478]: ^
Apr 28 21:05:49 NAS SABnzbd[478]: SyntaxError: invalid syntax
Apr 28 21:05:49 NAS systemd[1]: sabnzbd.service: Main process exited, code=exited, status=1/FAILURE
Apr 28 21:05:49 NAS systemd[1]: sabnzbd.service: Failed with result 'exit-code'.
Apr 28 21:05:49 NAS systemd[1]: sabnzbd.service: Service RestartSec=100ms expired, scheduling restart.
Apr 28 21:05:49 NAS systemd[1]: sabnzbd.service: Scheduled restart job, restart counter is at 3.
Apr 28 21:05:49 NAS systemd[1]: Stopped SABnzbd (DietPi).
Apr 28 21:05:49 NAS systemd[1]: Started SABnzbd (DietPi).
Apr 28 21:05:49 NAS SABnzbd[482]: File "/etc/sabnzbd/SABnzbd.py", line 403
Apr 28 21:05:49 NAS SABnzbd[482]: if home := os.environ.get("HOME"):
Apr 28 21:05:49 NAS SABnzbd[482]: ^
Apr 28 21:05:49 NAS SABnzbd[482]: SyntaxError: invalid syntax
Apr 28 21:05:49 NAS systemd[1]: sabnzbd.service: Main process exited, code=exited, status=1/FAILURE
Apr 28 21:05:49 NAS systemd[1]: sabnzbd.service: Failed with result 'exit-code'.
Apr 28 21:05:49 NAS systemd[1]: sabnzbd.service: Service RestartSec=100ms expired, scheduling restart.
Apr 28 21:05:49 NAS systemd[1]: sabnzbd.service: Scheduled restart job, restart counter is at 4.
Apr 28 21:05:49 NAS systemd[1]: Stopped SABnzbd (DietPi).
Apr 28 21:05:50 NAS systemd[1]: Started SABnzbd (DietPi).
Apr 28 21:05:50 NAS SABnzbd[484]: File "/etc/sabnzbd/SABnzbd.py", line 403
Apr 28 21:05:50 NAS SABnzbd[484]: if home := os.environ.get("HOME"):
Apr 28 21:05:50 NAS SABnzbd[484]: ^
Apr 28 21:05:50 NAS SABnzbd[484]: SyntaxError: invalid syntax
Apr 28 21:05:50 NAS systemd[1]: sabnzbd.service: Main process exited, code=exited, status=1/FAILURE
Apr 28 21:05:50 NAS systemd[1]: sabnzbd.service: Failed with result 'exit-code'.
Apr 28 21:05:50 NAS systemd[1]: sabnzbd.service: Service RestartSec=100ms expired, scheduling restart.
Apr 28 21:05:50 NAS systemd[1]: sabnzbd.service: Scheduled restart job, restart counter is at 5.
Apr 28 21:05:50 NAS systemd[1]: Stopped SABnzbd (DietPi).
Apr 28 21:05:50 NAS systemd[1]: sabnzbd.service: Start request repeated too quickly.
Apr 28 21:05:50 NAS systemd[1]: sabnzbd.service: Failed with result 'exit-code'.
Apr 28 21:05:50 NAS systemd[1]: Failed to start SABnzbd (DietPi).
looks like an issue within Sabnzbd application itself. Usually something that would need to be reported to Sabnzbd developer. Issues · sabnzbd/sabnzbd · GitHub
Thanks! I’ll log the issue there.
It looks like the issue is that sabnzbd 4.0.0 no longer supports Python 3.7 which is the version that’s on Dietpi. I just updated sabnzbd using the dietpi-software reinstall 139 command. Is there any way I can roll this back to sabnzbd 3.7.2? Or upgrade the Python 3 version I’m running? Whichever is easier?
As stated on GitHub, you would need to update your system to Debian Bullseye DietPi - How to upgrade to "Bullseye" - DietPi blog
Follow up question on this. I’m now running SAB 4.0.0 on Dietpi Bullseye. I understand the version of SAB included in dietpi-software is now 3.7.2 so future installs don’t run into Python 3 support issues. Given that I’m running SAB 4.0.0 on Bullseye, how would I get new updates of SAB? Will dietpi-software reinstall 139 automatically give me the latest version of SAB? Or will it downgrade me to 3.7.2?
That’s wrong, I guess a misunderstanding. We just set a specific Sab version on Debian Buster system. All other Debian version Bullseye / Bookworm will be able to update to latest Sab version as always.