I’m having a very similar issue. I’ve been working to configure rtorrent to use an NFS share for all storage. I finally have that setup right but now rtorrent will not start automatically on the start of the QuickBox machine. This is what appears in journalctl after boot:
Apr 22 15:06:12 QuickBox systemd[1]: Started rTorrent.
Apr 22 15:06:12 QuickBox sshd[1016]: Server listening on 0.0.0.0 port 4747.
Apr 22 15:06:12 QuickBox sshd[1016]: Server listening on :: port 4747.
Apr 22 15:06:12 QuickBox systemd[1]: Started OpenBSD Secure Shell server.
Apr 22 15:06:12 QuickBox iscsid[1066]: iSCSI logger with pid=1073 started!
Apr 22 15:06:12 QuickBox systemd[1]: Started iSCSI initiator daemon (iscsid).
Apr 22 15:06:12 QuickBox iscsid[1073]: iSCSI daemon with pid=1074 started!
Apr 22 15:06:12 QuickBox systemd[1]: Starting Login to default iSCSI targets...
Apr 22 15:06:12 QuickBox systemd[1]: Starting Serve a login-terminal over http on port 4224....
Apr 22 15:06:12 QuickBox systemd[1]: Started Serve a login-terminal over http on port 4224..
Apr 22 15:06:12 QuickBox iscsiadm[1083]: iscsiadm: No records found
Apr 22 15:06:12 QuickBox systemd[1]: Started Login to default iSCSI targets.
Apr 22 15:06:12 QuickBox systemd[1]: Reached target Remote File Systems (Pre).
Apr 22 15:06:12 QuickBox systemd[1]: Mounting /Data_Share...
Apr 22 15:06:12 QuickBox kernel: FS-Cache: Loaded
Apr 22 15:06:12 QuickBox kernel: FS-Cache: Netfs 'nfs' registered for caching
Apr 22 15:06:12 QuickBox killall[1100]: /usr/bin/rtorrent: no process found
Apr 22 15:06:12 QuickBox systemd[1]: [email protected]: Control process exited, code=exited status=1
Apr 22 15:06:12 QuickBox systemd[1]: [email protected]: Unit entered failed state.
Apr 22 15:06:12 QuickBox systemd[1]: [email protected]: Failed with result 'exit-code'.
Thus, when I go to this machine’s IP address, rtorrent is not running in the service control center and is not shown in the menu. When ssh’ing in as my ‘user’ user (this is the user initially created during the Ubuntu server install), and running “systemctl status rtorrent@master” I get the following:
user@QuickBox:~$ systemctl status rtorrent@master
● [email protected] - rTorrent
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2017-04-22 15:06:12 MDT; 48min ago
Process: 1100 ExecStop=/usr/bin/killall -w -s 2 /usr/bin/rtorrent (code=exited, status=1/FAILURE)
Process: 1054 ExecStart=/usr/bin/screen -d -m -fa -S rtorrent /usr/bin/rtorrent (code=exited, status=0/SUCCESS)
Process: 1031 ExecStartPre=/bin/rm -f /home/%I/.sessions/rtorrent.lock (code=exited, status=0/SUCCESS)
Main PID: 1062 (code=exited, status=0/SUCCESS)
Apr 22 15:06:11 QuickBox systemd[1]: Starting rTorrent...
Apr 22 15:06:12 QuickBox systemd[1]: Started rTorrent.
Apr 22 15:06:12 QuickBox killall[1100]: /usr/bin/rtorrent: no process found
Apr 22 15:06:12 QuickBox systemd[1]: [email protected]: Control process exited, code=exited status=1
Apr 22 15:06:12 QuickBox systemd[1]: [email protected]: Unit entered failed state.
Apr 22 15:06:12 QuickBox systemd[1]: [email protected]: Failed with result 'exit-code'.
Note: the user created during the QuickBox install process is named ‘master’.
When ssh’ing in as the ‘master’ user and running “systemctl start rtorrent@master” I get the following:
[master@QuickBox]:(0b)~$ systemctl start rtorrent@master
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to start '[email protected]'.
Authenticating as: user,,, (user)
Password:
.I can enter the password and it will then start the service.
Once I do that, the service control center shows Rtorrent as running but it is still not in the menu. If I go to the url for accessing rtorrent, it is now working and I can add torrents just fine.
Also, rtorrent runs perfectly fine if I ssh in as ‘master’ and just run “rtorrent”.
My question is this: why can’t rtorrent run on startup? I’m guess it has something to do with the prompt for authentication but I can’t seem to solve it. Any ideas?
