Hello,
I’m working with Quickbox script for several months now and had some problems with rTorrent crashing at times.
I think the issue is due to a full, or near full disk.
I tested a lot of possibilities (several VPS of differents HDD size, reinstall QuickBox, w/without quotas, torrents and size of torrents) and apparently rtorrent is not pausing torrents when disk full.
I saw a post about rTorrent crash because of corrupt torrents but I am pretty sure I don’t have any bad torrent that is corrupting my session, cause any of those torrents works fine in another QuickBox VPS.
I first get rutorrent message about disk being full then about 5 seconds later I get
Bad response from server: (500 [error,list]) Link to XMLRPC failed. May be, rTorrent is down?
.
I even tried adding in my .rtorrent.rc file:
schedule = low_diskspace,5,60,close_low_diskspace=2000M
but doesn’t seem to be working either, as rutorrent “disk full” message appear only when size available is zero or < 100Ko and not when size available < 2Go.
It’s weird that I didn’t find any or really few informations about full disk problems with rtorrent. IMO it should be a really common problem.
I’m on a Kimsufi server, Ubuntu 16.04.2 LTS, /home quotas
cat /etc/fstab:
/dev/sda2 / ext4 usrjquota=aquota.user,jqfmt=vfsv1,errors=remount-ro,relatime 0 1
/dev/sda1 /boot ext4 usrjquota=aquota.user,jqfmt=vfsv1,errors=remount-ro,relatime 0 1
/dev/sda3 /home ext4 usrjquota=aquota.user,jqfmt=vfsv1,defaults,relatime 1 2
/dev/sda4 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
devtmpfs /dev devtmpfs rw 0 0
systemctl status [email protected] before crash:
● [email protected] - rTorrent
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: active (running) since Fri 2018-01-12 12:49:30 CET; 5min ago
Process: 25105 ExecStop=/usr/bin/killall -w -s 2 /usr/bin/rtorrent (code=exited, status=1/FAILURE)
Process: 28137 ExecStart=/usr/bin/screen -d -m -fa -S rtorrent /usr/bin/rtorrent (code=exited, status=0/SUCCESS)
Process: 28134 ExecStartPre=/bin/rm -f /home/%I/.sessions/rtorrent.lock (code=exited, status=0/SUCCESS)
Main PID: 28139 (screen)
CGroup: /system.slice/system-rtorrent.slice/[email protected]
├─28139 /usr/bin/SCREEN -d -m -fa -S rtorrent /usr/bin/rtorrent
└─28144 /usr/bin/rtorrent
Jan 12 12:49:30 ns376118 systemd[1]: Starting rTorrent...
Jan 12 12:49:30 ns376118 systemd[1]: Started rTorrent.
systemctl status [email protected] right after crash:
● [email protected] - rTorrent
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-01-12 12:55:00 CET; 7s ago
Process: 21584 ExecStop=/usr/bin/killall -w -s 2 /usr/bin/rtorrent (code=exited, status=1/FAILURE)
Process: 28137 ExecStart=/usr/bin/screen -d -m -fa -S rtorrent /usr/bin/rtorrent (code=exited, status=0/SUCCESS)
Process: 28134 ExecStartPre=/bin/rm -f /home/%I/.sessions/rtorrent.lock (code=exited, status=0/SUCCESS)
Main PID: 28139 (code=exited, status=0/SUCCESS)
Jan 12 12:49:30 ns376118 systemd[1]: Starting rTorrent...
Jan 12 12:49:30 ns376118 systemd[1]: Started rTorrent.
Jan 12 12:55:00 ns376118 systemd[1]: [email protected]: Control process exited, code=exited status=1
Jan 12 12:55:00 ns376118 systemd[1]: [email protected]: Unit entered failed state.
Jan 12 12:55:00 ns376118 systemd[1]: [email protected]: Failed with result 'exit-code'.
Ps: I saw somewhere it coud be caused by the ext4 filesystem. Supposedly in ext3 filesystem rtorrent would effectively pause torrents when threshold reached.
Thanks a lot for any insight.
Paul