rTorrent Crashing


#1

Just had a few questions regarding getting my server working. I have reinstalled twice now, and I am having the same issue. Once I get everything up and running and try to use blackhole to start some torrents, everything starts fine, then a few seconds later the physical memory starts to climb, when it maxes out rtorrent crashing and then I get into a loop of restarting, maxing ram and crashing.

In addition, I thought I have fixed the diskspace problem. After trying to completely reboot system, once its boots back up the problem is back and my previous solution no longer works.

Thanks for any help.


#2

A couple of things to point out to hopefully add a bit of clarity.

Physical Memory Usage is nothing more than Memory at work. This implies that your RAM is doing it’s job and this is not by any means the actual amount of Used RAM on a system. Take note of your Real Memory Usage as this is an indicator of your actual RAM in use. Physical Ram hitting between 95% - 98% is common and expected behavior. This is a part of your systems RAM that is always there, QuickBox just exposes it to you for transparency.

Hard to say without knowing what your previous problem was and as well as your attempted fix at some scenario. If you could provide more details with what the problem may had been, we can issue a concrete solution for you… no need for guess work on your end, it’s what we’re here for :wink:

To focus on you first issue:

When it crashes, if you do systemctl status [email protected] and we’ll have something to go on. Without any real evidence of the issue, it’s fairly hard to troubleshoot… the status will at the very least give us a small clue. Additionally, any other information such as the OS you are on will be helpful.


#3

Thank you for your quick reply.

  1. I figured as much for the first issue, was just trying to best describe the crashing process.

  2. Cold rebooting causes the used portion to go negative, (-1468ish GB), I used setdisk again to 1800GB and it updated on Webui

  3. Results from systemctl status [email protected]

Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: inactive (dead)


#4

Are you on Debian by chance?

Also, if you could do a quick cat /etc/fstab


#5

Ubuntu 16.04.1, no /home, Kimsufi server

cat /etc/fstab

/dev/sda1 / ext4 usrjquota=aquota.user,jqfmt=vfsv1,errors=remount-ro,relatime 0 1
/dev/sda2 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
devtmpfs /dev devtmpfs rw 0 0


#6

Are you replacing the USERNAME with your actual username in this command?


#7

Well that’s embarrassing… but here is the result

[email protected] - rTorrent
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2016-09-02 01:45:52 CEST; 10min ago
Process: 20853 ExecStop=/usr/bin/killall -w -s 2 /usr/bin/rtorrent (code=exited, status=1/FAILURE)
Process: 20393 ExecStart=/usr/bin/screen -d -m -fa -S rtorrent /usr/bin/rtorrent (code=exited, status=0/SUCCESS)
Process: 20389 ExecStartPre=/bin/rm -f /home/%I/.sessions/rtorrent.lock (code=exited, status=0/SUCCESS)
Main PID: 20394 (code=exited, status=0/SUCCESS)

Sep 02 01:45:11 BC systemd[1]: Starting rTorrent…
Sep 02 01:45:11 BC systemd[1]: Started rTorrent.
Sep 02 01:45:52 BC systemd[1]: [email protected]: Control process exited, code=exited status=1
Sep 02 01:45:52 BC systemd[1]: [email protected]: Unit entered failed state.
Sep 02 01:45:52 BC systemd[1]: [email protected]: Failed with result ‘exit-code’.

I run systemctl restart [email protected], then rerun status, I get active (running) then abou 15 seconds into “checking” active torrents it crashes again…[01.09.2016 20:02:59] Bad response from server: (500 [error,list]) Link to XMLRPC failed. May be, rTorrent is down?


#8

This type of behavior actually sounds like you have a bad torrent that is corrupting your session.

Try rechecking them one by one until you hit the sweet spot. The bad one (once it attempts to recheck) will immediately crash rtorrent.


#9

Thank you, that seems to have worked. Never thought that would be a problem, a few years on my old seedbox, never had a bad torrent.

One more question if you have a second. Ever since I rebooted I cannot get my other services to restart, clicking refresh does nothing. Also attempted to uninstall, reinstall.


#10

Can you give me the output of uname -a


#11

Linux BC 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux


#12

Kernel looks right.

What do the following items return (remembering to change the items with USERNAME to yours):

systemctl status [email protected]
systemctl status plexmediaserver
systemctl status plexpy
systemctl status plexrequests
systemctl status [email protected]

#13

BC:~# systemctl status plexpy
● plexpy.service - PlexPy - Stats for Plex Media Server usage
Loaded: loaded (/etc/systemd/system/plexpy.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Fri 2016-09-02 01:25:48 CEST; 58min ago

Sep 02 01:25:47 BC systemd[1]: Starting PlexPy - Stats for Plex Media Server usage…
Sep 02 01:25:48 BC systemd[1]: Started PlexPy - Stats for Plex Media Server usage.

BC:~# systemctl status plexrequests
● plexrequests.service
Loaded: loaded (/etc/systemd/system/plexrequests.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Fri 2016-09-02 01:23:41 CEST; 1h 1min ago
Main PID: 12637 (code=exited, status=0/SUCCESS)

Sep 02 01:23:40 BC systemd[1]: Starting plexrequests.service…
Sep 02 01:23:40 BC systemd[1]: Started plexrequests.service.
Sep 02 01:25:07 BC systemd[1]: [/etc/systemd/system/plexrequests.service:1] Assignment outside of section. Ignoring.
Sep 02 01:25:07 BC systemd[1]: [/etc/systemd/system/plexrequests.service:2] Assignment outside of section. Ignoring.
Sep 02 01:25:47 BC systemd[1]: [/etc/systemd/system/plexrequests.service:1] Assignment outside of section. Ignoring.
Sep 02 01:25:47 BC systemd[1]: [/etc/systemd/system/plexrequests.service:2] Assignment outside of section. Ignoring.
Sep 02 01:26:29 BC systemd[1]: [/etc/systemd/system/plexrequests.service:1] Assignment outside of section. Ignoring.
Sep 02 01:26:29 BC systemd[1]: [/etc/systemd/system/plexrequests.service:2] Assignment outside of section. Ignoring.

BC:~# systemctl status plexmediaserver
● plexmediaserver.service - Plex Media Server for Linux
Loaded: loaded (/lib/systemd/system/plexmediaserver.service; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: core-dump) since Fri 2016-09-02 01:08:39 CEST; 1h 16min ago
Main PID: 3160 (code=dumped, signal=ABRT)

Sep 02 01:08:39 BC systemd[1]: plexmediaserver.service: Service hold-off time over, scheduling restart.
Sep 02 01:08:39 BC systemd[1]: Stopped Plex Media Server for Linux.
Sep 02 01:08:39 BC systemd[1]: plexmediaserver.service: Start request repeated too quickly.
Sep 02 01:08:39 BC systemd[1]: Failed to start Plex Media Server for Linux.
Sep 02 01:11:14 BC systemd[1]: [/lib/systemd/system/plexmediaserver.service:11] Invalid escape sequences in line, correcting: "/bin/sh -c 'LD_LIBRARY_PA
Sep 02 01:11:33 BC systemd[1]: [/lib/systemd/system/plexmediaserver.service:11] Invalid escape sequences in line, correcting: "/bin/sh -c 'LD_LIBRARY_PA
Sep 02 01:23:40 BC systemd[1]: [/lib/systemd/system/plexmediaserver.service:11] Invalid escape sequences in line, correcting: "/bin/sh -c 'LD_LIBRARY_PA
Sep 02 01:25:07 BC systemd[1]: [/lib/systemd/system/plexmediaserver.service:11] Invalid escape sequences in line, correcting: "/bin/sh -c 'LD_LIBRARY_PA
Sep 02 01:25:47 BC systemd[1]: [/lib/systemd/system/plexmediaserver.service:11] Invalid escape sequences in line, correcting: "/bin/sh -c 'LD_LIBRARY_PA
Sep 02 01:26:29 BC systemd[1]: [/lib/systemd/system/plexmediaserver.service:11] Invalid escape sequences in line, correcting: "/bin/sh -c 'LD_LIBRARY_PA

BC:~# systemctl status [email protected]
[email protected] - SickRage
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2016-09-02 01:26:30 CEST; 59min ago
Process: 15145 ExecStart=/usr/bin/python /home/%I/.sickrage/SickBeard.py -q --daemon --nolaunch --datadir=/home/%I/.sickrage (code=exited, status=1/FA

Sep 02 01:26:30 BC python[15145]: tempfile.gettempdir(), ‘fake_useragent.json’
Sep 02 01:26:30 BC python[15145]: File “/usr/lib/python2.7/tempfile.py”, line 275, in gettempdir
Sep 02 01:26:30 BC python[15145]: tempdir = _get_default_tempdir()
Sep 02 01:26:30 BC python[15145]: File “/usr/lib/python2.7/tempfile.py”, line 217, in _get_default_tempdir
Sep 02 01:26:30 BC python[15145]: (“No usable temporary directory found in %s” % dirlist))
Sep 02 01:26:30 BC python[15145]: IOError: [Errno 2] No usable temporary directory found in [’/tmp’, ‘/var/tmp’, ‘/usr/tmp’, ‘/’]
Sep 02 01:26:30 BC systemd[1]: [email protected]: Control process exited, code=exited status=1
Sep 02 01:26:30 BC systemd[1]: Failed to start SickRage.
Sep 02 01:26:30 BC systemd[1]: [email protected]: Unit entered failed state.
Sep 02 01:26:30 BC systemd[1]: [email protected]: Failed with result ‘exit-code’.

[email protected] - SickRage
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2016-09-02 01:26:30 CEST; 59min ago
Process: 15145 ExecStart=/usr/bin/python /home/%I/.sickrage/SickBeard.py -q --daemon --nolaunch --datadir=/home/%I/.sickrage (code=exited, status=1/FA

Sep 02 01:26:30 BC python[15145]: tempfile.gettempdir(), ‘fake_useragent.json’
Sep 02 01:26:30 BC python[15145]: File “/usr/lib/python2.7/tempfile.py”, line 275, in gettempdir
Sep 02 01:26:30 BC python[15145]: tempdir = _get_default_tempdir()
Sep 02 01:26:30 BC python[15145]: File “/usr/lib/python2.7/tempfile.py”, line 217, in _get_default_tempdir
Sep 02 01:26:30 BC python[15145]: (“No usable temporary directory found in %s” % dirlist))
Sep 02 01:26:30 BC python[15145]: IOError: [Errno 2] No usable temporary directory found in [’/tmp’, ‘/var/tmp’, ‘/usr/tmp’, ‘/’]
Sep 02 01:26:30 BC systemd[1]: [email protected]: Control process exited, code=exited status=1
Sep 02 01:26:30 BC systemd[1]: Failed to start SickRage.
Sep 02 01:26:30 BC systemd[1]: [email protected]: Unit entered failed state.
Sep 02 01:26:30 BC systemd[1]: [email protected]: Failed with result ‘exit-code’.

[email protected]
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2016-09-02 02:07:48 CEST; 19min ago
Process: 31665 ExecStart=/usr/bin/python /home/%I/.couchpotato/CouchPotato.py --daemon (code=exited, status=1/FAILURE)

Sep 02 02:07:48 BC python[31665]: l = Loader()
Sep 02 02:07:48 BC python[31665]: File “/home/usfguy/.couchpotato/CouchPotato.py”, line 57, in init
Sep 02 02:07:48 BC python[31665]: os.makedirs(self.log_dir)
Sep 02 02:07:48 BC python[31665]: File “/usr/lib/python2.7/os.py”, line 157, in makedirs
Sep 02 02:07:48 BC python[31665]: mkdir(name, mode)
Sep 02 02:07:48 BC python[31665]: OSError: [Errno 28] No space left on device: '/home/usfguy/.couchpotato/logs’
Sep 02 02:07:48 BC systemd[1]: [email protected]: Control process exited, code=exited status=1
Sep 02 02:07:48 BC systemd[1]: Failed to start [email protected]
Sep 02 02:07:48 BC systemd[1]: [email protected]: Unit entered failed state.
Sep 02 02:07:48 BC systemd[1]: [email protected]: Failed with result ‘exit-code’.


#14

If you do systemctl restart [email protected], does the service enable and stay active?


#15

Job for [email protected] failed because the control process exited with error code. See “systemctl status [email protected]” and “journalctl -xe” for details

also, rtorrent crashed again, I think it might be an issue of diskspace. I have plenty of space but the details on the torrent state Low diskspace


#16

I am thinking it may have to do with blackhole. I don’t personally use a blackhole folder so I can’t confirm this.

Hmm, this is suggesting then that it simply will not start. What does journalctl -xe show. @liara may also have some additional feedback on this once she is around.

Ah, this may be your issue.

Will you do this as root user fix-disk_widget_root and see if that settles your Disk Status Widget on the dashboard. Additionally, are you using the diskspace plugin… or does it say that diskspaceh

Since you are using journaled quotas… there should be no issue, so I am thinking it is reading from the wrong mount for some reason. With that said… so you need Quotas installed?


#17

I edited my previous post, Im thinking its something with available space (I know nothing about linux HD allocations)

journalctl -xe
Sep 02 02:39:01 BC CRON[12636]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 02 02:39:01 BC CRON[12645]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
Sep 02 02:39:01 BC CRON[12634]: pam_unix(cron:session): session closed for user root
Sep 02 02:39:01 BC CRON[12636]: pam_unix(cron:session): session closed for user root
Sep 02 02:39:12 BC sudo[12802]: www-data : unable to resolve host BC
Sep 02 02:39:12 BC sudo[12802]: www-data : TTY=unknown ; PWD=/srv/rutorrent/home/widgets ; USER=root ; COMMAND=/usr/sbin/repquota /
Sep 02 02:39:12 BC sudo[12802]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 02 02:39:12 BC sudo[12802]: pam_unix(sudo:session): session closed for user root
Sep 02 02:39:12 BC sudo[12807]: www-data : unable to resolve host BC
Sep 02 02:39:12 BC sudo[12807]: www-data : TTY=unknown ; PWD=/srv/rutorrent/home/widgets ; USER=root ; COMMAND=/usr/sbin/repquota /
Sep 02 02:39:12 BC sudo[12807]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 02 02:39:12 BC sudo[12807]: pam_unix(sudo:session): session closed for user root
Sep 02 02:39:12 BC sudo[12812]: www-data : unable to resolve host BC
Sep 02 02:39:12 BC sudo[12812]: www-data : TTY=unknown ; PWD=/srv/rutorrent/home/widgets ; USER=root ; COMMAND=/usr/sbin/repquota /
Sep 02 02:39:12 BC sudo[12812]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 02 02:39:12 BC sudo[12812]: pam_unix(sudo:session): session closed for user root
Sep 02 02:39:28 BC sudo[12885]: www-data : unable to resolve host BC
Sep 02 02:39:28 BC sudo[12885]: www-data : TTY=unknown ; PWD=/srv/rutorrent/home/widgets ; USER=root ; COMMAND=/usr/sbin/repquota /
Sep 02 02:39:28 BC sudo[12885]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 02 02:39:28 BC sudo[12885]: pam_unix(sudo:session): session closed for user root
Sep 02 02:39:28 BC sudo[12890]: www-data : unable to resolve host BC
Sep 02 02:39:28 BC sudo[12890]: www-data : TTY=unknown ; PWD=/srv/rutorrent/home/widgets ; USER=root ; COMMAND=/usr/sbin/repquota /
Sep 02 02:39:28 BC sudo[12890]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 02 02:39:28 BC sudo[12890]: pam_unix(sudo:session): session closed for user root
Sep 02 02:39:28 BC sudo[12895]: www-data : unable to resolve host BC
Sep 02 02:39:28 BC sudo[12895]: www-data : TTY=unknown ; PWD=/srv/rutorrent/home/widgets ; USER=root ; COMMAND=/usr/sbin/repquota /
Sep 02 02:39:28 BC sudo[12895]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 02 02:39:28 BC sudo[12895]: pam_unix(sudo:session): session closed for user root
Sep 02 02:39:44 BC sudo[12968]: www-data : unable to resolve host BC
Sep 02 02:39:44 BC sudo[12968]: www-data : TTY=unknown ; PWD=/srv/rutorrent/home/widgets ; USER=root ; COMMAND=/usr/sbin/repquota /
Sep 02 02:39:44 BC sudo[12968]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 02 02:39:44 BC sudo[12968]: pam_unix(sudo:session): session closed for user root
Sep 02 02:39:44 BC sudo[12973]: www-data : unable to resolve host BC
Sep 02 02:39:44 BC sudo[12973]: www-data : TTY=unknown ; PWD=/srv/rutorrent/home/widgets ; USER=root ; COMMAND=/usr/sbin/repquota /
Sep 02 02:39:44 BC sudo[12973]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 02 02:39:44 BC sudo[12973]: pam_unix(sudo:session): session closed for user root
Sep 02 02:39:44 BC sudo[12978]: www-data : unable to resolve host BC
Sep 02 02:39:44 BC sudo[12978]: www-data : TTY=unknown ; PWD=/srv/rutorrent/home/widgets ; USER=root ; COMMAND=/usr/sbin/repquota /
Sep 02 02:39:44 BC sudo[12978]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 02 02:39:44 BC sudo[12978]: pam_unix(sudo:session): session closed for user root

#18

I originally didn’t install quota. But to fix my widget I already entered that, installed quota then used setdisk to fix the widget.

diskspace is uninstalled, current have diskspaceh active


#19

uninstall the diskspaceh and install diskspace and that will sort your rtorrent issue in that regard.

Removing the quotas package will fix your Disk Status Widget as long as you have it calling the right mount, which that command will address. I know we have a considerable amount of Kimsufi users, this is just one such situation that has never cropped up.


#20

Ok we are getting somewher, I uninstalled spaceH, installed diskspace, removed quotas.

Now widget says 0GB free, 19GB used
Rutorrent is finally showing disk usage in bottom left, and giving me the full disk warning.

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.8T 0 disk
├─sda1 8:1 0 19.5G 0 part /
└─sda2 8:2 0 511M 0 part [SWAP]
BC:~# showspace
24.1GB usfguy/