rtorrent crashes after system update

octobee · 2014-10-25 20:11:11

Problem started after system update, rtorrent package was not changed.
After start, it "works" for about a half-second, and then crashes with the following log:

Caught SIGBUS, dumping stack:
rtorrent() [0x41369e]
/usr/lib/libpthread.so.0(+0x10200) [0x7f2c6ac1e200]
/usr/lib/libcrypto.so.1.0.0(+0x6e3b0) [0x7f2c698053b0]
Error: Success
Signal code '2': Non-existent physical address.
Fault address: 0x7f2c155f7000
The fault address is not part of any chunk.
Aborted (core dumped)

Varies from time to time.
Did not see different value.

All values tend to stay the same if reproduced in short time interval.

Memtest says RAM is fine (although I did not complete it, only 5 first tests).
Before-last update was done at 11th of October.

jasonwryan · 2014-10-25 20:31:23

What versions of rtorrent and libtorrent are you using?

octobee · 2014-10-25 21:00:05

jasonwryan wrote:

What versions of rtorrent and libtorrent are you using?

rtorrent 0.9.4-1
libtorrent 0.13.4-1

Xlator · 2014-10-26 21:38:11

I'm having this too. Reading through issues on the Github page led me to believe it might be a file system or hard drive issue, but fsck and extended SMART test come up green. Given that and your RAM test, we can at least be sure it isn't hardware related.

Xlator · 2014-10-30 14:09:01

octobee: What file system are you using? I'm on btrfs. I don't know if that's the issue here, as rtorrent worked fine until the other day, but it might be a change in the filesystem tooling? I don't really have time to look into the issue at the moment, merely speculating at this stage.

octobee · 2014-10-30 17:51:50

Bits of research and observation:
Hardware is definitely not at fault, not RAM, nor hard disk. Memtest and SMART do not report any errors.
rtorrent is not related to problem at all, since I also observed random-looking IO errors in other software, such as mplayer and libreoffice. These errors are usually tied to the same place in the same file, and reset after reboot. For example, if mplayer started to crash at 0:12:34 of some video file, then on relaunch mplayer will crash at the same place of the file. After reboot this will disappear, just to emerge in some other place of filesystem.

Xlator wrote:

octobee: What file system are you using? I'm on btrfs. I don't know if that's the issue here, as rtorrent worked fine until the other day, but it might be a change in the filesystem tooling? I don't really have time to look into the issue at the moment, merely speculating at this stage.

I am using btrfs too, and it is quite likely to be the cause. Some googling revealed that there are quite heavy issues with btrfs on kernel 3.17.1, maybe because of some bug in the latter. While these issues are not the same as we are dealing here with, there is a probability that they have a common cause.
Since kernel 3.17.2 was published around yesterday, for now I am going to wait for it to get into Arch repositories.

Xlator · 2014-10-31 19:35:34

Cheers for the update! Hope the kernel release fixes the problem.

EDIT: rTorrent has been ticking along nicely for me for the past ten hours since I installed the kernel update.

Last edited by Xlator (2014-11-03 18:40:29)

Arch Linux

#1 2014-10-25 20:11:11

rtorrent crashes after system update

#2 2014-10-25 20:31:23

Re: rtorrent crashes after system update

#3 2014-10-25 21:00:05

Re: rtorrent crashes after system update

#4 2014-10-26 21:38:11

Re: rtorrent crashes after system update

#5 2014-10-30 14:09:01

Re: rtorrent crashes after system update

#6 2014-10-30 17:51:50

Re: rtorrent crashes after system update

#7 2014-10-31 19:35:34

Re: rtorrent crashes after system update

Board footer