[Linux/Dietpi] Unable to connect to sabnzbd after 4.0.0 update
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
[Linux/Dietpi] Unable to connect to sabnzbd after 4.0.0 update
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/ I am unable to connect. I have radarr and sonarr also running on that Pi box and I'm able to access those services fine. Am I missing something?
Re: Unable to connect to sabnzbd after 4.0.0 update
Looks like the service isn't able to start. I've tried to get this to start multiple times manually using DietPi's service manager and I keep getting this. How do I get the service to start?
Code: Select all
● 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).
Re: Unable to connect to sabnzbd after 4.0.0 update
Running journalctl -u sabnzbd.service shows the syntax error below.
Code: Select all
-- 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).
Re: Unable to connect to sabnzbd after 4.0.0 update
I have the same syntax error (Debian 4.19.269-1 (2022-12-20) x86_64 GNU/Linux). Cannot start SABnzbd after upgrading.
-
- Newbie
- Posts: 1
- Joined: April 28th, 2023, 10:10 am
Re: Unable to connect to sabnzbd after 4.0.0 update
From what I have read the walrus operator was introduced in Python 3.8.
Re: Unable to connect to sabnzbd after 4.0.0 update
Correct. See release notes: python 3.7 not supported anymoretildajones wrote: ↑April 29th, 2023, 7:41 am From what I have read the walrus operator was introduced in Python 3.8.
-
- Newbie
- Posts: 24
- Joined: March 30th, 2019, 2:32 pm
Re: Unable to connect to sabnzbd after 4.0.0 update
After the update I can't connect either.
Re: Unable to connect to sabnzbd after 4.0.0 update
"can't connect" is logical if SABnzbd is NOT running at all. Check your python3 version: it must be python3.8 or higher.
-
- Newbie
- Posts: 24
- Joined: March 30th, 2019, 2:32 pm
Re: Unable to connect to sabnzbd after 4.0.0 update
SAB runs for a few seconds starts to d/l & then closes. I will check my python version. Thanks
Re: Unable to connect to sabnzbd after 4.0.0 update
That looks like something else. But ... start with the python3 version.pauladkins wrote: ↑April 29th, 2023, 6:04 pm SAB runs for a few seconds starts to d/l & then closes. I will check my python version. Thanks
Re: Unable to connect to sabnzbd after 4.0.0 update
Mine also crashes once starting a download. Installed python 3.8.10 to force a upgrade, still happened. Trying a full server restart now to ensure the dependencies are working. If that fails, I'll downgrade back to 3.72 and try extract the logs.
Note, using the legacy/windows/standalone.
Note, using the legacy/windows/standalone.
Last edited by mental on April 30th, 2023, 3:55 am, edited 1 time in total.
Re: Unable to connect to sabnzbd after 4.0.0 update
Same here standalone version 32bit, after downgrading too 3.7.2 all good and it works again
Re: [Linux/Dietpi] Unable to connect to sabnzbd after 4.0.0 update
Windows 32bit users: go here viewtopic.php?t=26211
This thread is about Linux, systemd and python3 <= 3.7
This thread is about Linux, systemd and python3 <= 3.7