SABnzbd doesn't start on boot (CentOS7)
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.
SABnzbd doesn't start on boot (CentOS7)
After upgrading my Linux server from CentOS6 to CentOS7 I had to re-install SABnzbd. It runs great like before, but the program is no longer automatically started at boot up. I can start the program from a PuTTY terminal on a Windows machine. Change from the former installation is, that I now use root as the sabnzbd user. Would that be a problem?
Re: SABnzbd doesn't start on boot (CentOS7)
I know nothing about CentOS, so I can only refer to the https://sabnzbd.org/wiki/installation/i ... entos-rhel (especially setting for user / group)
Furthermore:
* why run as root? SAB doesn't need root rights, so why give root rights. Furthermore it could be the cause of your problem
* check the system log files
* what happens when you type "systemctl start sabnzbd.service"
Furthermore:
* why run as root? SAB doesn't need root rights, so why give root rights. Furthermore it could be the cause of your problem
* check the system log files
* what happens when you type "systemctl start sabnzbd.service"
Re: SABnzbd doesn't start on boot (CentOS7)
"systemctl start sabnzbd.service" is processed without any error or confirmation, but afterwards there is no sabnzbd process running
Re: SABnzbd doesn't start on boot (CentOS7)
Thanks for the link. I had used another scheme but will now try this one.
Re: SABnzbd doesn't start on boot (CentOS7)
Works great. Thanks. Root as user was not a problem, although I have changed the sabnzbd user now. Problem was a small typo in sabnzbd.service.