Xtradb cluster 5.6 crash in production


I had a production system running for half year without problem up until recently when it crashed. I try to figure out what have caused the issue.

It is a 2 node master-master xtradb 5.6 cluster on 2 Debian Wheezy 7 linuxes.

Here is the relevant log:

mysql error log:

17:05:33 UTC - mysqld got signal 11 ;
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.
Please help us make Percona XtraDB Cluster better by reporting any
bugs at [url]https://bugs.launchpad.net/percona-xtradb-cluster[/url]

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 233144 K bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f40fc177630
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong…
Segmentation fault


Nov 18 18:05:34 sql kernel: [9921358.749531] mysqld[25732]: segfault at 30 ip 00000000005e09f8 sp 00007f41717d7f50 error 4 in mysqld[400000+bd6000]

Thank you.

I have the same problem for 3 years. Now i have 5.6 percona, earlier it was 5.5, etc.

I have 5 nodes, and zabbix restarter for crushed nodes. But sometime they can crush all just in time.

Any ideas?

defiler this crash report without stack trace says not much. Also, it is not common to see mysqld segfaulting. Is this btw a 32 or 64 bit OS? Did you notice any problems with memory usage maybe?