Rtorrent keeps crashing ()

As stated above(now it’s a new problem), my webUI is not responding, and nothing seems to work. This happend suddenly after working without problem for the better part of a year, it just disconnected on me from one minute to another. How can i get a read-only fault all of a sudden, and of course - how do I fix it?

Quickbox is running on a Hetzner server, witch I formatted to ubuntu 16.04. Nothing else is running on my server, and I am the only user. I (obviously) have SSH acces, so apparently the box running but not running.

I added some logs from the apache server

Best regards

apache2.service - LSB: Apache2 web server
Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: failed (Result: exit-code) since Sun 2018-03-18 14:53:24 CET; 3min 52s ago
Docs: man:systemd-sysv-generator(8)
Process: 997 ExecStart=/etc/init.d/apache2 start (code=exited, status=1/FAILURE)

Mar 18 14:53:24 happymediainc systemd[1]: Starting LSB: Apache2 web server…
Mar 18 14:53:24 happymediainc apache2[997]: * Starting Apache httpd web server apache2
Mar 18 14:53:24 happymediainc apache2[997]: mktemp: failed to create file via template ‘/tmp/tmp.XXXXXXXXXX’: Read-onl
Mar 18 14:53:24 happymediainc apache2[997]: /etc/init.d/apache2: 72: /etc/init.d/apache2: cannot create : Directory no
Mar 18 14:53:24 happymediainc apache2[997]: *
Mar 18 14:53:24 happymediainc apache2[997]: * The apache2 configtest failed.
Mar 18 14:53:24 happymediainc systemd[1]: apache2.service: Control process exited, code=exited status=1
Mar 18 14:53:24 happymediainc systemd[1]: Failed to start LSB: Apache2 web server.
Mar 18 14:53:24 happymediainc systemd[1]: apache2.service: Unit entered failed state.
Mar 18 14:53:24 happymediainc systemd[1]: apache2.service: Failed with result ‘exit-code’.

Okay, I got the interface working by re-mounting filesystem and forcing rw.
Now i’m working on preventing rtorrent from crashing. It runs for a minute, but the crashes with the following message. It looks like a re-install but is there a way to avoid it?

Caught SIGBUS, dumping stack:
rtorrent() [0x415f2b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390) [0x7fd37ec14390]
/usr/lib/libtorrent.so.19(+0x14099e) [0x7fd37fe2a99e]

Error: Success
Signal code ‘2’: Non-existent physical address.
Fault address: 0x7fd3588b9000
The fault address is not part of any chunk.
Aborted

When a disk goes into read-only mode, this may be an issue where the disk is on it’s way out. Another possibility is that it’s simply running out of usable space. Just curios, what is the output for either lsblk or df -h?

Hi.

Thanks for the reply. As you stated, and I suspected, the disk died on me. So much for zero redundancy! I tried installing quickbox on-top of the other installation, as a last ditch effort, and lost SSH acces. So now i got my self a new server instead.

As I don’t have acces, I can’t be of much help in providing output.

No worries, as we both know now unfortunately, the disk died. Hope your new server endures the test of time. :smiley:

1 Like