Sigint 11 on newly installed percona server

[JonathanLevin]

We installed Percona Server last night on three servers.
This morning we had all three of them crash with sigint 11.
We were previously using the standard MySQL 5.5.21 before moving to Percona Server 5.5.24

Here are the details from the error log:
Server 1:

08:34:44 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.

key_buffer_size=402653184
read_buffer_size=8388608
max_used_connections=14
max_threads=500
thread_count=6
connection_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 8591341 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fe768000990
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...
stack_bottom = 7fe7e17a6e78 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7a5d85]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x680e04]
/lib64/libpthread.so.0[0x398180f4a0]
/usr/sbin/mysqld[0x622f96]
/usr/sbin/mysqld(_Z24update_global_user_statsP3THDbl+0x3c2)[0x624a82]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0xaa)[0x58b10a]
/usr/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0xe58)[0x7278d8]
/usr/sbin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_info+0x125)[0x5294e5]
/usr/sbin/mysqld[0x52dfc9]
/usr/sbin/mysqld(handle_slave_sql+0x919)[0x52f399]
/lib64/libpthread.so.0[0x39818077f1]
/lib64/libc.so.6(clone+0x6d)[0x39814e5ccd]

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

Connection ID (thread ID): 1471
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

Server 2:

09:37:23 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.

key_buffer_size=268435456
read_buffer_size=4194304
max_used_connections=111
max_threads=800
thread_count=54
connection_count=54
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6825544 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f9104000990
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...
stack_bottom = 7f96f4042e78 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7a5d85]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x680e04]
/lib64/libpthread.so.0[0x355320f4a0]
/usr/sbin/mysqld[0x622f96]
/usr/sbin/mysqld(_Z24update_global_user_statsP3THDbl+0x3c2)[0x624a82]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0xaa)[0x58b10a]
/usr/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0xe58)[0x7278d8]
/usr/sbin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_info+0x125)[0x5294e5]
/usr/sbin/mysqld[0x52dfc9]
/usr/sbin/mysqld(handle_slave_sql+0x919)[0x52f399]
/lib64/libpthread.so.0[0x35532077f1]
/lib64/libc.so.6(clone+0x6d)[0x3552ee5ccd]

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

Server 3:

09:35:34 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.

key_buffer_size=402653184
read_buffer_size=8388608
max_used_connections=9
max_threads=800
thread_count=2
connection_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 13510216 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fc65c000990
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...
stack_bottom = 7fc67ab78e78 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7a5d85]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x680e04]
/lib64/libpthread.so.0[0x328fc0f4a0]
/usr/sbin/mysqld[0x622f96]
/usr/sbin/mysqld(_Z24update_global_user_statsP3THDbl+0x3c2)[0x624a82]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0xaa)[0x58b10a]
/usr/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0xe58)[0x7278d8]
/usr/sbin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_info+0x125)[0x5294e5]
/usr/sbin/mysqld[0x52dfc9]
/usr/sbin/mysqld(handle_slave_sql+0x919)[0x52f399]
/lib64/libpthread.so.0[0x328fc077f1]
/lib64/libc.so.6(clone+0x6d)[0x328f8e5ccd]

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

[JonathanLevin (boogybo)]

There is also a temporary table that crashed (in) replication. This could be connected. The temporary table was using the MEMORY engine.

[Jervin R (revin)]

Looks like a duplicate of https://bugs.launchpad.net/percona-server/+bug/1008278

[Raghavendra D Prabhu (raghavendra-prabhu)]

@Jonathan,
                does turning off userstats help? (userstat=0 in my.cnf). Since it is dynamic you can also turn it off at runtime.

[JonathanLevin (boogybo)]

Well, it isn't in the my.cnf, I turned it on manually.
The servers crashed again though and this time I will leave this variable off.

[Laurynas Biveinis (laurynas-biveinis)]

Indeed it is a duplicate of bug 1008278. Percona Server 5.5.25a will have the fix, until it is released, userstat needs to be disabled.

Closing the bug. Please let us know if you have any further questions.