Mysql频繁Crash挂掉，求助
如题，Mysql频繁Crash，Tomcat也死。
求高人帮忙看下。下面是Mysql的错误日志。
Version: '5.5.21-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
06:58:11 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=16777216
read_buffer_size=524288
max_used_connections=1
max_threads=800
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 = 844709 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x36b67c0
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 = 7f7f533a9e68 thread_stack 0x40000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x35)[0x79b455]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x403)[0x66a613]
/lib64/libpthread.so.0(+0xf500)[0x7f7f530a9500]
/lib64/libc.so.6(memcpy+0x63)[0x7f7f522c80b3]
/usr/local/mysql/bin/mysqld(_mi_rec_unpack+0x253)[0x7c26a3]
/usr/local/mysql/bin/mysqld(_mi_read_dynamic_record+0x2a8)[0x7c2b88]
/usr/local/mysql/bin/mysqld(mi_rnext_same+0x23c)[0x7d5a5c]
/usr/local/mysql/bin/mysqld(_ZN9ha_myisam15index_next_sameEPhPKhj+0x2f)[0x7aae2f]
/usr/local/mysql/bin/mysqld[0x592be2]
/usr/local/mysql/bin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x79)[0x5987b9]
/usr/local/mysql/bin/mysqld[0x59e01d]
/usr/local/mysql/bin/mysqld(_ZN4JOIN4execEv+0x925)[0x5b2125]
/usr/local/mysql/bin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x1c3)[0x5ade73]
/usr/local/mysql/bin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x179)[0x5b3bd9]
/usr/local/mysql/bin/mysqld[0x571c61]
/usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x2216)[0x577236]
/usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x18a)[0x57980a]
/usr/local/mysql/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1321)[0x57b3b1]
/usr/local/mysql/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x167)[0x610037]
/usr/local/mysql/bin/mysqld(handle_one_connection+0x54)[0x6100a4]
/lib64/libpthread.so.0(+0x7851)[0x7f7f530a1851]
/lib64/libc.so.6(clone+0x6d)[0x7f7f5232711d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f7f2c002bb0): is an invalid pointer
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.
120912 14:58:11 mysqld_safe Number of processes running now: 0
120912 14:58:11 mysqld_safe mysqld restarted
120912 14:58:11 [Warning] option 'wait_timeout': unsigned value 315360000 adjusted to 31536000
120912 14:58:11 [Note] Plugin 'FEDERATED' is disabled.
120912 14:58:11 InnoDB: The InnoDB memory heap is disabled
120912 14:58:11 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120912 14:58:11 InnoDB: Compressed tables use zlib 1.2.3
120912 14:58:11 InnoDB: Using Linux native AIO
120912 14:58:11 InnoDB: Initializing buffer pool, size = 128.0M
120912 14:58:11 InnoDB: Completed initialization of buffer pool
120912 14:58:11 InnoDB: highest supported file format is Barracuda.
120912 14:58:11 InnoDB: Waiting for the background threads to start
120912 14:58:12 InnoDB: 1.1.8 started; log sequence number 387006257
120912 14:58:12 [Note] Recovering after a crash using mysql-bin
120912 14:58:12 [Note] Starting crash recovery...
120912 14:58:12 [Note] Crash recovery finished.
120912 14:58:12 [Note] Event Scheduler: Loaded 0 events
120912 14:58:12 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
[解决办法]
日志文件报什么错误贴出来。
[解决办法]
看看各参数的配置吧,特别是innodb的相关参数.
[解决办法]
CNF中的内容是什么，内存多大，
key_buffer_size 、 read_buffer_size、 sort_buffer_size是否设置过大，执行什么操作
磁盘空间如何
[解决办法]
贴一下错误日志，特别是把错误有关的部分贴出来以供分析。
[解决办法]
应该是主从复制遇到了一个BUG吧。
参考：
http://hcymysql.blog.51cto.com/5223301/956948
[解决办法]
可以参考下这篇文章：http://hcymysql.blog.51cto.com/5223301/956948
[解决办法]
贴出来带error的日志部分
