Upgrading Percona Server from 5.5.23 to 5.5.24 fails

[Olaf van Zandwijk]

I've got Debian Squeeze and upgraded the Debian packages

   percona-server-client-5.5 (5.5.23-rel25.3-240.squeeze => 5.5.24-rel26.0-256.squeeze)
   percona-server-common-5.5 (5.5.23-rel25.3-240.squeeze => 5.5.24-rel26.0-256.squeeze)
   percona-server-server-5.5 (5.5.23-rel25.3-240.squeeze => 5.5.24-rel26.0-256.squeeze)

The server starts but immediately crashes with the following logging (two different cases). It doesn't matter what query is executed, the server will crash.

Downgrading the packages back to 5.5.23 'resolves' this problem and the server starts normally again and accepts queries.

=== Example error 1 ===
11:28:49 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=33554432
read_buffer_size=102400
max_used_connections=0
max_threads=1000
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 8337018 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x2be63f80
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 = 7eff8653ce78 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7c3435]
120605 13:28:49 [Note] Event Scheduler: Loaded 0 events
120605 13:28:49 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.24-55-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Percona Server (GPL), Release 26.0
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x692484]
/lib/libpthread.so.0(+0xeff0)[0x7f05fb6deff0]
/usr/sbin/mysqld[0x632ca6]
/usr/sbin/mysqld(_Z24update_global_user_statsP3THDbl+0x3c2)[0x634792]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0xaa)[0x598d9a]
/usr/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0xcf4)[0x740ce4]
/usr/sbin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_info+0x125)[0x532e75]
/usr/sbin/mysqld[0x5379b9]
/usr/sbin/mysqld(handle_slave_sql+0x919)[0x538d89]
/usr/sbin/mysqld(pfs_spawn_thread+0x59)[0x9700e9]
/lib/libpthread.so.0(+0x68ca)[0x7f05fb6d68ca]
/lib/libc.so.6(clone+0x6d)[0x7f05fa97792d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (2be6f8a0): BEGIN
Connection ID (thread ID): 2
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.

=== Example error 2 ===
11:16:40 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=33554432
read_buffer_size=102400
max_used_connections=0
max_threads=1000
thread_count=1
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 8337018 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x2b759f10
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 = 7f572d60ec18 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7c3435]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x692484]
/lib/libpthread.so.0(+0xeff0)[0x7f5da230cff0]
/usr/sbin/mysqld[0x632ca6]
/usr/sbin/mysqld(_Z24update_global_user_statsP3THDbl+0x3c2)[0x634792]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0xaa)[0x598d9a]
/usr/sbin/mysqld[0x59b18d]
/usr/sbin/mysqld(_Z19do_handle_bootstrapP3THD+0x16a)[0x59b46a]
/usr/sbin/mysqld(handle_bootstrap+0x51)[0x59b4f1]
/usr/sbin/mysqld(pfs_spawn_thread+0x59)[0x9700e9]
/lib/libpthread.so.0(+0x68ca)[0x7f5da23048ca]
/lib/libc.so.6(clone+0x6d)[0x7f5da15a592d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (2b761040): USE mysql
Connection ID (thread ID): 1
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.

[Jervin R (revin)]

This looks like a duplicate of bug 1008278 , can you try disabling userstat?

SET GLOBAL userstat=0;

[Olaf van Zandwijk (olafz)]

I hadn't related bug 1008278 to this one, but apparently it is: setting userstat to 0 solves this issue.

[Olaf van Zandwijk (olafz)]

In addition to my previous comment: we are *not* using Master-Master replication as opposed to the bugreport in bug 1008278. In our case there is no relation to replication at all, even without replication and only with userstat set to 1 the server crashes at startup.

[Olaf van Zandwijk (olafz)]

I marked it as duplicate of bug 1008609