Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Today I experienced this error a second time in two weeks and I wonder why that is?

Is it more a hardware- or software-related thing? (e.g. what should I check?)

That DB server didn't have any problems until now...

share|improve this question
up vote 0 down vote accepted

don't you have this message in log?

This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail.

share|improve this answer
I do have this comment, but the hardware seems ok (disks, filesystem and memory), so any hints on other possible causes might be valuable... – Michael Siebert May 29 '12 at 12:16
There is a bug in mysql or some of it's libraries. Dump/restore table and upgrade system. If it won't help - post a bug to mysql bugtracker. – DukeLion May 29 '12 at 14:10

I think the problem was that we had different mysql server versions in replication due to the fact that one server has a pending OS upgrade. I installed MariaDB, set up the replication, and everything works now

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.