Error when rtorrent starts
Home › Forums › GeeXboX on ARM SoCs › Error when rtorrent starts
This topic contains 1 reply, has 2 voices, and was last updated by
tomlohave 2 months, 3 weeks ago.
-
AuthorPosts
-
August 5, 2015 at 22:54 #10021
I saw this error many times in my original cubox and also in my new 4×4.
Many times when Geexbox try to start rtorrent this is the error generated:root@geexbox:/etc/systemd/system# journalctl -f -u rtorrent -- Logs begin at Thu 1970-01-01 01:00:03 BST. -- Jan 01 01:00:06 geexbox runrtorrent[280]: mkdir: can't create directory '/rtorre nt/': No such file or directory Jan 01 01:00:06 geexbox runrtorrent[280]: mkdir: can't create directory '/rtorre nt/': No such file or directory Aug 05 22:38:29 geexbox stoprtorrent[1059]: kill: you need to specify whom to ki ll Aug 05 22:38:29 geexbox systemd[1]: rtorrent.service: control process exited, co de=exited status=1 Aug 05 22:38:29 geexbox systemd[1]: Unit rtorrent.service entered failed state.So, I purpose to modify stoprtorrent file as:
#!/bin/sh # find pid of top level instance kill <code>/usr/bin/screen -d | grep -o "[0-9]*\.rtorrent"|cut -f1 -d'.'</code>into (same file may substitute runrtorrent and stoprtorrent)
#!/bin/bash screen -wipe sess='' sess=$(screen -ls | grep rtorrent | cut -d'.' -f 1) re='^[0-9]+$' if ! [[ $(echo $sess) =~ $re ]] ; then echo "rtorrent is powered off" systemctl stop rtorrent && systemctl start rtorrent else echo "rtorrent is powered on" kill <code>/usr/bin/screen -d | grep -o "[0-9]*\.rtorrent"|cut -f1 -d'.'</code> fiAdvantages:
cleaning screen session using wipe, if there is at least one dead rtorrent session this clean up
try to get screen rtorrent session number
if powered off stop && start (restart not ever works fine)
if powered on kill screen session (may be optimize the code using $sess vaqriable containing screen rtorrent session number)August 6, 2015 at 21:33 #10022Hi Skelos,
mkdir: can’t create directory ‘/rtorre
nt/': No such file or directoryIt’s a little suspicious, can you check why you have this problem ?
Anyway , if you think your approach is better
please, submit your modifications with a patch or send them to me.
( I have no problem with rtorrent since … and I use transmission)# systemctl status rtorrent rtorrent.service - rtorrent daemon Loaded: loaded (/usr/lib/systemd/system/rtorrent.service; disabled) Active: active (exited) since Tue 2015-06-23 15:53:20 BST; 1 months 13 days ago Process: 209 ExecStart=/usr/bin/runrtorrent (code=exited, status=0/SUCCESS) Main PID: 209 (code=exited, status=0/SUCCESS) CGroup: /system.slice/rtorrent.service ├─349 /usr/bin/SCREEN -dmS rtorrent rtorrent -n -o import=/etc/rtorrent.rc └─350 rtorrent -n -o import=/etc/rtorrent.rc -
AuthorPosts
You must be logged in to reply to this topic.

