You are not logged in.
I set up a new server and has been running great for a month now, but now my rtorrent is giving me problems. The output is giving me:
Caught SIGBUS, dumping stack:
rtorrent() [0x41344c]
/usr/lib/libpthread.so.0(+0xf870) [0x7f901606c870]
/usr/lib/libcrypto.so.1.0.0(+0x6e618) [0x7f9015485618]
Error: Success
Signal code '2': Non-existent physical address.
Fault address: 0x7f8ff4e61008
The fault address is not part of any chunk.
Aborted (core dumped)I'm only getting this when I load a few torrents in. It's handled more before, but it won't work. No upgrades since installation, just tweaks to the configuration.
Using rtorrent 0.9.3-2.
Any help to debug or resolve would be great.
Last edited by wsiddall (2014-01-20 20:01:37)
Offline
do you have free space in your file systems? apparently people are getting similar errors with rtorrent when their file systems are getting full.
Offline
I had that problem originally, but the disk still has at least 80G left after the torrents had the files created.
Offline
Try updating the system, there have been updates to openssl and glibc recently.
Offline
Ok, so playing around and getting more info.
The crash happens during a check_hash operation, either when a download finishes or when a new session starts and there are completed downloads in the queue.
What I can't tell is if it is caused by the check hash operation, or if it's just rtorrent failing at a high CPU load.
Offline
It definitely shouldn't fail because of high cpu load, unless you have bad RAM or something (which was my initial thought of what could cause this actually)
do you have up to date system, like x33a suggested? My second thought was this could be issue in openssl, since its libcrypto.so that fails
Offline
Ok, it cleared up on it's own now, but now I have a separate problem which I should put up as a separate topic.
Thanks for the help
Offline
Please mark this thread as solved.
Offline
I have the same problem. Did it just solve itself or did you reinstall something?
Offline