Description:
Our mysql server crashes periodically and restarts. This causes unwanted downtime and disk IO, and also tends to break the slave replication.
InnoDB: ###### Diagnostic info printed to the standard error stream
InnoDB: Error: semaphore wait has lasted > 600 seconds
InnoDB: We intentionally crash the server, because it appears to be hung.
130424 19:27:18 InnoDB: Assertion failure in thread 140027430221568 in file srv0srv.c line 2910
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.
19:27: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=536870912
read_buffer_size=131072
max_used_connections=97
max_threads=2002
thread_count=67
connection_count=67
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4905183 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+0x2e)[0x7bcf5e]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x695ea4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f5aafe68cb0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f5aaf06d425]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x17b)[0x7f5aaf070b8b]
/usr/sbin/mysqld[0x870767]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f5aafe60e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f5aaf12acbd]
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.
130424 19:32:33 mysqld_safe Number of processes running now: 0
130424 19:32:33 mysqld_safe mysqld restarted
130424 19:32:42 [Note] Plugin 'FEDERATED' is disabled.
130424 19:32:42 InnoDB: The InnoDB memory heap is disabled
130424 19:32:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130424 19:32:42 InnoDB: Compressed tables use zlib 1.2.3
130424 19:32:42 InnoDB: Using Linux native AIO
130424 19:32:42 InnoDB: Initializing buffer pool, size = 10.0G
130424 19:32:44 InnoDB: Completed initialization of buffer pool
130424 19:32:44 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 1528713295424
130424 19:32:44 InnoDB: Database was not shut down normally!
How to repeat:
Run mysql.
Suggested fix:
Don't crash?
