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.
[....] Starting sabnzbdplus (via systemctl): sabnzbdplus.serviceJob for sabnzbdplus.service failed because the control process exited with error code. See "systemctl status sabnzbdplus.service" and "journalctl -xe" for details.
failed!
â sabnzbdplus.service - LSB: SABnzbd+ binary newsgrabber
Loaded: loaded (/etc/init.d/sabnzbdplus; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2018-01-13 23:23:32 CET; 3min 8s ago
Docs: man:systemd-sysv-generator(8)
Process: 2973 ExecStart=/etc/init.d/sabnzbdplus start (code=exited, status=2)
Jan 13 23:23:30 schattorie-web systemd[1]: Starting LSB: SABnzbd+ binary newsgrabber...
Jan 13 23:23:30 schattorie-web sabnzbdplus[2973]: * Starting SABnzbd+ binary newsgrabber
Jan 13 23:23:32 schattorie-web sabnzbdplus[2973]: ...fail!
Jan 13 23:23:32 schattorie-web systemd[1]: sabnzbdplus.service: Control process exited, code=exited status=2
Jan 13 23:23:32 schattorie-web systemd[1]: Failed to start LSB: SABnzbd+ binary newsgrabber.
Jan 13 23:23:32 schattorie-web systemd[1]: sabnzbdplus.service: Unit entered failed state.
Jan 13 23:23:32 schattorie-web systemd[1]: sabnzbdplus.service: Failed with result 'exit-code'.
When I try to run the sabnzbdplus deamon manually it appears to "hang" at the line: SSL verification test: True
My /etc/default/sabnzbdplus has all the parameters empty, except for the USER= which contains the user which I'm logged on as...
I've tried removing/installing/updating, tried different users in that config file, tried pointing it to the sabnzbd.ini... I have no clue on why the deaon suddenly stopped working after a couple of years of running :S
The process just keeps coming back with a different PID when I kill it...
Edit: Where does sabnzbd store it's configuration? If I change the port it might be fine... I do have a file in /home/marc/.sabnzbd/sabnzbd.ini, but that doesn't seem to be the one?
Edit 2: It was the correct file anyway, I didn't look properly... I changed the port, no it runs fine again!
had the same problem, looked in the sabnzbd.ini and saw that I had updated the listen IP to 0.0.0.0. notice the extra "." at the end...removed the extra "." restarted the service and everything worked great....would be better to have extra error message to point us in the right direction in the future IMHO.
Tf2n7vhFYATz wrote: ↑July 26th, 2022, 10:44 am
had the same problem, looked in the sabnzbd.ini and saw that I had updated the listen IP to 0.0.0.0. notice the extra "." at the end...removed the extra "." restarted the service and everything worked great....would be better to have extra error message to point us in the right direction in the future IMHO.
Ah, that's a bug. In the GUI, you can fill that out, and it's accepted. And then SAB won't start. Not good.
And SAB even says:
Open a Terminal window and type the line (example):
/home/sander/git/sabnzbd/SABnzbd.py --server 0.0.0.0.:8081
... with the trailing dot.
And stdout says:
Fatal error:
Unable to bind to port 8080 on 0.0.0.0.. Some other software uses the port or SABnzbd is already running.