You are not logged in.
If I start it in its own user account via "systemctl start sabnzbd", I get a web interface on http://127.0.0.1:8080/sabnzbd/, but if I start a user service via sabnzbd@maximilian.service, it fails:
sabnzbd@maximilian.service - SABnzbd binary newsreader
Loaded: loaded (/usr/lib/systemd/system/sabnzbd@.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2020-08-01 23:05:42 CEST; 6s ago
Docs: https://sabnzbd.org/wiki/
Process: 4970 ExecStart=/usr/lib/sabnzbd/SABnzbd.py --logging 1 --browser 0 --config-file /home/max>
Main PID: 4970 (code=exited, status=216/GROUP)
Aug 01 23:05:42 Mongo systemd[1]: sabnzbd@maximilian.service: Scheduled restart job, restart counter is>
Aug 01 23:05:42 Mongo systemd[1]: Stopped SABnzbd binary newsreader.
Aug 01 23:05:42 Mongo systemd[1]: sabnzbd@maximilian.service: Start request repeated too quickly.
Aug 01 23:05:42 Mongo systemd[1]: sabnzbd@maximilian.service: Failed with result 'exit-code'.
Aug 01 23:05:42 Mongo systemd[1]: Failed to start SABnzbd binary newsreader.
Directly executing the file /usr/lib/sabnzbd/SABnzbd.py as user works though. This isn’t connected to the recent v3.0 release, I’ve already had this issue formerly. Any ideas?
Offline
Can you `systemctl cat` the service and show it? And `journalctl -xa -u sabnzbd@maximilian.service` to see better details, I think.
Offline
/usr/lib/systemd/system/sabnzbd@.service:
[Unit]
Description=SABnzbd binary newsreader
Documentation=https://sabnzbd.org/wiki/
Wants=network-online.target
After=network-online.target
[Service]
# Default location is ~/.sabnzbd/sabnzbd.ini, but package previously used ~/.sabnzbd.ini so default to >
ExecStart=/usr/lib/sabnzbd/SABnzbd.py --logging 1 --browser 0 --config-file /home/%I/.sabnzbd.ini
User=%I
Group=%I
Type=simple
Restart=on-failure
[Install]
WantedBy=multi-user.target
$ journalctl -xa -u sabnzbd@maximilian.service
[…]
-- The job identifier is 1419 and the job result is done.
Aug 02 12:35:22 Mongo systemd[1]: sabnzbd@maximilian.service: Start request repeated too quickly.
Aug 02 12:35:22 Mongo systemd[1]: sabnzbd@maximilian.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The unit sabnzbd@maximilian.service has entered the 'failed' state with result 'exit-code'.
Aug 02 12:35:22 Mongo systemd[1]: Failed to start SABnzbd binary newsreader.
-- Subject: A start job for unit sabnzbd@maximilian.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit sabnzbd@maximilian.service has finished with a failure.
--
-- The job identifier is 1419 and the job result is failed.
Last edited by frumble (2020-08-02 16:17:55)
Offline
I have the same problem, I wonder did you manage ot find a solution?
Offline
How do you know you have the same problem if the problem was never properly identified in this thread?
The journalctl output (including the few lines in the systemctl status) is pretty useless (and the -x flag just adds a lot of noise). A clue is in the line
Main PID: 4970 (code=exited, status=216/GROUP)
The service file uses the same value for user and group. I'm guessing the OP had a user maximilian without the corresponding group.
And this is not systemd user service, but a (templated) system service where sabnzb is executed as a specific user.
Offline