We appear to have experienced this bug today as well with percona 5.5.27-28.1-log,
####
121108 12:35:25 InnoDB: Assertion failure in thread 140155688658688 in file buf0flu.c line 542
InnoDB: Failing assertion: (buf_pool->flush_list).count > 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
17:35:25 UTC - mysqld got signal 6 ;
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 http://bugs.percona.com/
key_buffer_size=33554432
read_buffer_size=131072
max_used_connections=30
max_threads=1000
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 = 2221025 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
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 = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7ab385]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x687584]
/lib64/libpthread.so.0(+0xf4a0)[0x7f79c1dd54a0]
/lib64/libc.so.6(gsignal+0x35)[0x7f79c0fa0885]
/lib64/libc.so.6(abort+0x175)[0x7f79c0fa2065]
/usr/sbin/mysqld[0x88cb34]
/usr/sbin/mysqld[0x88cb77]
/usr/sbin/mysqld[0x889af1]
/usr/sbin/mysqld[0x8bac63]
/usr/sbin/mysqld[0x83b3a0]
/lib64/libpthread.so.0(+0x77f1)[0x7f79c1dcd7f1]
/lib64/libc.so.6(clone+0x6d)[0x7f79c1053ccd]
You may download the Percona Server operations manual by visiting http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
121108 12:35:26 mysqld_safe Number of processes running now: 0
121108 12:35:26 mysqld_safe mysqld restarted
...
####
We appear to have experienced this bug today as well with percona 5.5.27-28.1-log,
####
121108 12:35:25 InnoDB: Assertion failure in thread 140155688658688 in file buf0flu.c line 542 >flush_ list).count > 0 bugs.mysql. com. dev.mysql. com/doc/ refman/ 5.5/en/ forcing- innodb- recovery. html bugs.percona. com/
InnoDB: Failing assertion: (buf_pool-
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://
InnoDB: about forcing recovery.
17:35:25 UTC - mysqld got signal 6 ;
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 http://
key_buffer_ size=33554432 size=131072 connections= 30 size)*max_ threads = 2221025 K bytes of memory
read_buffer_
max_used_
max_threads=1000
thread_count=6
connection_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0 mysqld( my_print_ stacktrace+ 0x35)[0x7ab385] mysqld( handle_ fatal_signal+ 0x4a4)[ 0x687584] libpthread. so.0(+0xf4a0) [0x7f79c1dd54a0 ] libc.so. 6(gsignal+ 0x35)[0x7f79c0f a0885] libc.so. 6(abort+ 0x175)[ 0x7f79c0fa2065] mysqld[ 0x88cb34] mysqld[ 0x88cb77] mysqld[ 0x889af1] mysqld[ 0x8bac63] mysqld[ 0x83b3a0] libpthread. so.0(+0x77f1) [0x7f79c1dcd7f1 ] libc.so. 6(clone+ 0x6d)[0x7f79c10 53ccd] www.percona. com/software/ percona- server/. You may find information
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 = 0 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
You may download the Percona Server operations manual by visiting
http://
in the manual which will help you identify the cause of the crash.
121108 12:35:26 mysqld_safe Number of processes running now: 0
121108 12:35:26 mysqld_safe mysqld restarted
...
####