Percona mysql 5.5 restarting frequently

[sankar]

Hi Everyone,

   We are regularly facing mysql crashing problem in one of production servers.

FYI..

130407 17:05:58 InnoDB: Assertion failure in thread 140062226646784 in file btr0cur.c line 314
InnoDB: Failing assertion: btr_page_get_prev(get_block->frame, mtr) == page_get_page_no(page)
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:05:58 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=524288000
read_buffer_size=2097152
max_used_connections=2
max_threads=500
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2566128 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x6f0a13b0
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 = 7f62c743fe58 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7a8d05]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x685304]
/lib64/libpthread.so.0[0x3e8220f490]
/lib64/libc.so.6(gsignal+0x35)[0x3e81e32905]
/lib64/libc.so.6(abort+0x175)[0x3e81e340e5]
/usr/sbin/mysqld[0x870417]
/usr/sbin/mysqld[0x8720a0]
/usr/sbin/mysqld[0x9210ef]
/usr/sbin/mysqld[0x923759]
/usr/sbin/mysqld[0x8183d6]
/usr/sbin/mysqld[0x8030f1]
/usr/sbin/mysqld(_ZN7handler12ha_write_rowEPh+0x5d)[0x68a36d]
/usr/sbin/mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x60)[0x573330]
/usr/sbin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x7bb
)[0x578b1b]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x14d8)[0x5890b8]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x333)[0x58c7e3]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x15b2)[0x58de42]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0xd7)[0x6279a7]
/usr/sbin/mysqld(handle_one_connection+0x51)[0x627ae1]
/lib64/libpthread.so.0[0x3e822077e1]
/lib64/libc.so.6(clone+0x6d)[0x3e81ee577d]

Please suggest us how to resolve this issue..

Thanks in advance..
Shan

[Valerii Kravchuk (valerii-kravchuk)]

We had similar bug report in the past (had never been verified):

https://bugs.launchpad.net/percona-server/+bug/995258

Please, provide your my.cnf file content. Try to identify table that leads to crash when accessed, and run CHECK TABLE ... EXTENDED on it, and share any output.

Had you ever restored this server from xtrabackup backup?

[Launchpad Janitor (janitor)]

[Expired for Percona Server 5.5 because there has been no activity for 60 days.]

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2933