=================================================================== CRASH 1 =================================================================== Version: '5.0.27-standard' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 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=402653184 read_buffer_size=2093056 max_used_connections=66 max_connections=100 threads_connected=54 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 802415 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x9ee1170 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... Cannot determine thread, fp=0x7be5c64c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x816e9a0 handle_segfault + 656 0x8372aa4 ha_delete_hash_node + 180 0x837369d ha_remove_all_nodes_to_page + 93 0x82faaff btr_search_drop_page_hash_index + 1423 0x8321c8d buf_LRU_search_and_free_block + 541 0x8322072 buf_LRU_get_free_block + 242 0x831b0da buf_page_init_for_read + 42 0x8322bcb buf_read_page_low + 219 0x8323681 buf_read_ahead_linear + 1217 0x83196f1 buf_page_get_gen + 833 0x82f6101 btr_pcur_move_to_next_page + 257 0x82ca98c row_search_for_mysql + 8444 0x822acc3 _ZN11ha_innobase13general_fetchEPcjj + 83 0x822afdd _ZN11ha_innobase8rnd_nextEPc + 109 0x821a3a5 _Z13rr_sequentialP14st_read_record + 37 0x81c1a46 _Z10sub_selectP4JOINP13st_join_tableb + 102 0x81c1df5 _Z9do_selectP4JOINP4ListI4ItemEP8st_tableP9Procedure + 517 0x81d0c64 _ZN4JOIN4execEv + 5604 0x81d1ba4 _Z12mysql_selectP3THDPPP4ItemP13st_table_listjR4ListIS1_ES2_jP8st_orderSB_S2_SB_mP13select_resultP18st_select_lex_unitP13st_sel + 180 0x81d223c _Z13handle_selectP3THDP6st_lexP13select_resultm + 300 0x8186381 _Z21mysql_execute_commandP3THD + 5521 0x818cb30 _Z11mysql_parseP3THDPcj + 320 0x818d911 _Z16dispatch_command19enum_server_commandP3THDPcj + 3297 0x818e258 _Z10do_commandP3THD + 136 0x818e97c handle_one_connection + 1548 0xc443cc (?) New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x9d890b0 = SELECT dkp_pointhistory.id, dkp_users.id as userid, name, points, reason, location, date, class FROM dkp_pointhistory, dkp_users WHERE forItem='1' AND dkp_pointhistory.guild='13585' AND dkp_pointhistory.user = dkp_users.id AND tableid = '1' ORDER BY dkp_pointhistory.date DESC thd->thread_id=3187 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 071103 10:02:14 mysqld restarted 071103 10:02:14 InnoDB: Database was not shut down normally! =================================================================== CRASH 2 =================================================================== Version: '5.0.27-standard' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL) 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=402653184 read_buffer_size=2093056 max_used_connections=89 max_connections=100 threads_connected=34 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 802415 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x7cb8eac8 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... Cannot determine thread, fp=0x7d5dfb2c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x816e9a0 handle_segfault + 656 0x8372abf ha_delete_hash_node + 207 0x837369d ha_remove_all_nodes_to_page + 93 0x82faaff btr_search_drop_page_hash_index + 1423 0x82fb579 btr_search_build_page_hash_index + 409 Stack trace seems successful - bottom reached Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x9d25cf8 = SELECT id FROM dkp_users ORDER BY ID DESC thd->thread_id=4404 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 071103 06:00:25 mysqld restarted =================================================================== CRASH 3 =================================================================== 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=402653184 read_buffer_size=2093056 max_used_connections=62 max_connections=100 threads_connected=59 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 802415 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x7ce0b6c8 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... Cannot determine thread, fp=0x7d746a4c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x816e9a0 handle_segfault + 656 0x8372abf ha_delete_hash_node + 207 0x837369d ha_remove_all_nodes_to_page + 93 0x82faaff btr_search_drop_page_hash_index + 1423 0x82fb579 btr_search_build_page_hash_index + 409 root@zedd [/var/log]# vi mysqld.stack stackzedd [/var/log]# resolve_stack_dump -s /usr/lib/mysql/mysqld.sym -n mysqld.s 0x816e9a0 handle_segfault + 656 0x8368629 rec_get_offsets_func + 601 0x82f81f9 btr_search_guess_on_hash + 1497 0x82eddb0 btr_cur_search_to_nth_level + 1104 0x82c8015 row_sel_get_clust_rec_for_mysql + 149 0x82c9496 row_search_for_mysql + 3078 0x822acc3 _ZN11ha_innobase13general_fetchEPcjj + 83 0x822ad9a _ZN11ha_innobase10index_nextEPc + 58 0x8220936 _ZN7handler15read_range_nextEv + 86 0x82207e2 _ZN7handler21read_multi_range_nextEPP18st_key_multi_range + 34 0x821293b _ZN18QUICK_RANGE_SELECT8get_nextEv + 331 0x821a2ad _Z8rr_quickP14st_read_record + 29 0x821c919 _Z8filesortP3THDP8st_tableP13st_sort_fieldjP10SQL_SELECTyPy + 4889 0x81c7fac _Z17create_sort_indexP3THDP4JOINP8st_orderyy + 396 0x81cfe58 _ZN4JOIN4execEv + 2008 0x81d1ba4 _Z12mysql_selectP3THDPPP4ItemP13st_table_listjR4ListIS1_ES2_jP8st_orderSB_S2_SB_mP13select_resultP18st_select_lex_unitP13st_sel + 180 0x81d223c _Z13handle_selectP3THDP6st_lexP13select_resultm + 300 0x8186381 _Z21mysql_execute_commandP3THD + 5521 0x818cb30 _Z11mysql_parseP3THDPcj + 320 0x818d911 _Z16dispatch_command19enum_server_commandP3THDPcj + 3297 0x818e258 _Z10do_commandP3THD + 136 0x818e97c handle_one_connection + 1548 0xc443cc (?) 0xa98c3e (?) New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x8bdd4c8 = SELECT * FROM dkp_pointhistory WHERE user='155044' AND guild='' AND tableid='1' AND forItem=1 ORDER BY date DESC thd->thread_id=927 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash.