Comment 2 for bug 1078346

pservit (pservit) wrote :


Today 2 of 3 nodes crashed with similar backtrace:

16:40:13 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 Server better by reporting any
bugs at

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

Thread pointer: 0x588a2c00
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...
121121 10:40:15 [Note] WSREP: (0cb18548-322e-11e2-0800-bf8bb6ded1ca, 'tcp://') reconnecting to b2aaa747-32f1-11e2-
0800-9dbb5a52fe4a (tcp://, attempt 0
stack_bottom = 7fe9da186e48 thread_stack 0x40000

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fe91833f960): is an invalid pointer
Connection ID (thread ID): 98095

You may download the Percona Server operations manual by visiting You may find information
in the manual which will help you identify the cause of the crash.
121121 10:40:17 mysqld_safe Number of processes running now: 0
121121 10:40:17 mysqld_safe WSREP: not restarting wsrep node automatically

I tried to start mysql again but it crashed with same backtrace.
After downgrade to 5.5.24-23.6 it started successfully.