Adventures with various Segfaults due to defective RAM

Crash

If you get various segfaults on your Linux server, like these:

or:

or

or

etc. etc., then, no, your system is not suddenly crazy. Nor are you. It is highly likely that you RAM is defective. You should reboot your server and run the  RAM test from your boot manager (Grub always has such a test) to see if it can detect faulty RAM.

If you are operating a server that you can’t reboot because you can’t tolerate downtime, there is an excellent tool called memtester , which is a memory test for a running system. It is part of the Debian distribution, installit with apt-get install memtester  Check top to see how much free RAM there is available. Say you have 10GB RAM free, then ask memterst to test 8GB of it (so that 2GB are remaining free for the running system to operate). In my case, memtester indeed detected faults.

I ran

It outputted stuff like this:

So, when I replaced the RAM, the Segfaults stopped. You can run memtester  regularly to make sure the RAM is okay. Healty RAM is a very crucial part of your successful hosting operation!

In my case however, the segfaults corrupted MySQL tables, which I had to clean up. All’s well that ends well!

 

, , ,

Trackbacks/Pingbacks

  1. A solution for MySQL Assertion failure FIL_NULL | Michael FranzlMichael Franzl - January 25, 2014

    […] defective RAM module recently caused data corruption in MySQL tables. MySQL would log the following to /var/log/syslog  in […]

Leave a Reply

Powered by WordPress. Designed by Woo Themes