Closed chaoticdude closed 6 years ago
crsantos
commented
6 years ago /tmp which rtorrent user may not have access.
If this is the case: edit your httpd.service file and add the following: PrivateTmp=false.When I say httpd, I mean, the systemctl unit file of the application server you're using: apache2.service or nginx.service
AlOliveira88
commented
6 years ago Hello .. Good evening... I have the same problem... This is not 0% ... the strangest thing is that this has already been working, I have tested in several machines and the result is the same ..... 0%
Do they have a solution? thank you
AlOliveira88
commented
6 years ago this was the tutorial I followed: https://github.com/xombiemp/ultimate-torrent-setup/wiki and already worked very well .... was it some update ... ????
xombiemp
commented
6 years ago rTorrent code has been update and the guide is using the master branch again. It should work now.
My rtorrent service isn't starting. Not sure how to fix, here is the status...any insight would be much appreciated.
● rtorrent.service - rTorrent Loaded: loaded (/etc/systemd/system/rtorrent.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Sat 2017-11-11 10:28:33 MST; 3min 2s ago Process: 18193 ExecStart=/usr/bin/rtorrent -n -o import=/var/lib/rtorrent/rtorrent.rc (code=exited, status=255) Main PID: 18193 (code=exited, status=255)
Nov 11 10:28:33 CHAOTICSERVER systemd[1]: rtorrent.service: Unit entered failed state. Nov 11 10:28:33 CHAOTICSERVER systemd[1]: rtorrent.service: Failed with result 'exit-code'. Nov 11 10:28:33 CHAOTICSERVER systemd[1]: rtorrent.service: Service hold-off time over, scheduling restart. Nov 11 10:28:33 CHAOTICSERVER systemd[1]: Stopped rTorrent. Nov 11 10:28:33 CHAOTICSERVER systemd[1]: rtorrent.service: Start request repeated too quickly. Nov 11 10:28:33 CHAOTICSERVER systemd[1]: Failed to start rTorrent.