There was another crash with the binary provided in the issue 37223.
131216 6:39:18 InnoDB: Assertion failure in thread 140026689693440 in
file buf0buf.ic line 749
InnoDB: Failing assertion: buf_page_in_file(bpage)
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.
12:39:18 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=37
max_threads=3002
thread_count=29
connection_count=29
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads =
6602304 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
/opt/percona-server-5.5.34/bin/mysqld(my_print_stacktrace+0x35)[0x7eb555]
/opt/percona-server-5.5.34/bin/mysqld(handle_fatal_signal+0x3f4)[0x6a5a84]
/lib64/libpthread.so.0[0x31e000f500]
/lib64/libc.so.6(gsignal+0x35)[0x31df8328e5]
/lib64/libc.so.6(abort+0x175)[0x31df8340c5]
/opt/percona-server-5.5.34/bin/mysqld[0x8a6506]
/opt/percona-server-5.5.34/bin/mysqld[0x8a69fe]
/opt/percona-server-5.5.34/bin/mysqld[0x8a6ca0]
/opt/percona-server-5.5.34/bin/mysqld[0x84c3bd]
/lib64/libpthread.so.0[0x31e0007851]
/lib64/libc.so.6(clone+0x6d)[0x31df8e894d]
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.
There was another crash with the binary provided in the issue 37223.
131216 6:39:18 InnoDB: Assertion failure in thread 140026689693440 in in_file( bpage) bugs.mysql. com. dev.mysql. com/doc/ refman/ 5.5/en/ forcing- innodb- recovery. html bugs.percona. com/
file buf0buf.ic line 749
InnoDB: Failing assertion: buf_page_
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.
12:39:18 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= 37 size)*max_ threads =
read_buffer_
max_used_
max_threads=3002
thread_count=29
connection_count=29
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
6602304 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0 server- 5.5.34/ bin/mysqld( my_print_ stacktrace+ 0x35)[0x7eb555] server- 5.5.34/ bin/mysqld( handle_ fatal_signal+ 0x3f4)[ 0x6a5a84] libpthread. so.0[0x31e000f5 00] libc.so. 6(gsignal+ 0x35)[0x31df832 8e5] libc.so. 6(abort+ 0x175)[ 0x31df8340c5] server- 5.5.34/ bin/mysqld[ 0x8a6506] server- 5.5.34/ bin/mysqld[ 0x8a69fe] server- 5.5.34/ bin/mysqld[ 0x8a6ca0] server- 5.5.34/ bin/mysqld[ 0x84c3bd] libpthread. so.0[0x31e00078 51] libc.so. 6(clone+ 0x6d)[0x31df8e8 94d] 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
/opt/percona-
/opt/percona-
/lib64/
/lib64/
/lib64/
/opt/percona-
/opt/percona-
/opt/percona-
/opt/percona-
/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.
The assertion is still the same