100714 11:05:46 - 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=8384512 read_buffer_size=131072 max_used_connections=42 max_threads=1000 threads_connected=29 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2194336 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x2aaaf8016200 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 = 0x45cba110 thread_stack 0x40000 /opt/third-party/mysql/product/current/bin/mysqld(my_print_stacktrace+0x20) [0x9d9824] /opt/third-party/mysql/product/current/bin/mysqld(handle_segfault+0x368) [0x5ece78] /lib64/libpthread.so.0 [0x374020de70] /opt/third-party/mysql/product/current/bin/mysqld(Item_sum::print(String*, enum_query_type)+0x8e) [0x523900] /opt/third-party/mysql/product/current/bin/mysqld(Item::print_item_w_name(String*, enum_query_type)+0x64) [0x5013fe] /opt/third-party/mysql/product/current/bin/mysqld(st_select_lex::print(THD*, String*, enum_query_type)+0x1a0) [0x655594] /opt/third-party/mysql/product/current/bin/mysqld(st_select_lex_unit::print(String*, enum_query_type)+0xeb) [0x4ee693] /opt/third-party/mysql/product/current/bin/mysqld(mysqld_show_create(THD*, TABLE_LIST*)+0xda6) [0x760e34] /opt/third-party/mysql/product/current/bin/mysqld(mysql_execute_command(THD*)+0x37b6) [0x5fbfa6] /opt/third-party/mysql/product/current/bin/mysqld(mysql_parse(THD*, char const*, unsigned int, char const**)+0x20a) [0x6034a2] /opt/third-party/mysql/product/current/bin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x1362) [0x5f7c98] /opt/third-party/mysql/product/current/bin/mysqld(do_command(THD*)+0x114) [0x5f6932] /opt/third-party/mysql/product/current/bin/mysqld(handle_one_connection+0xd31) [0x5f1ca9] /lib64/libpthread.so.0 [0x37402062f7] /lib64/libc.so.6(clone+0x6d) [0x373fad1b6d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x12df8c50 = SHOW CREATE TABLE `test`.`macsi_games_daily` thd->thread_id=4133 thd->killed=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. 100714 11:05:46 mysqld_safe Number of processes running now: 0 100714 11:05:46 mysqld_safe mysqld restarted InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 100714 11:05:47 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Last MySQL binlog file position 0 8536262, file name /opt/third-party/mysql/product/current/log/binarylog/binlog.047253 100714 11:05:47 InnoDB: Started; log sequence number 178 77930512 100714 11:05:47 [Note] Recovering after a crash using /opt/third-party/mysql/product/current/log/binarylog/binlog 100714 11:05:47 [Note] Starting crash recovery... 100714 11:05:47 [Note] Crash recovery finished. 100714 11:05:47 [Note] Event Scheduler: Loaded 0 events 100714 11:05:47 [Note] /opt/third-party/mysql/product/current/bin/mysqld: ready for connections. Version: '5.1.32-enterprise-gpl-pro-log' socket: '/opt/third-party/mysql/product/current/tmp/mysql.sock' port: 6033 MySQL Enterprise Server - Pro Edition (GPL) 100714 11:05:53 - 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=8384512 read_buffer_size=131072 max_used_connections=11 max_threads=1000 threads_connected=11 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2194336 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x7d900e0 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 = 0x45c2c110 thread_stack 0x40000 /opt/third-party/mysql/product/current/bin/mysqld(my_print_stacktrace+0x20) [0x9d9824] /opt/third-party/mysql/product/current/bin/mysqld(handle_segfault+0x368) [0x5ece78] /lib64/libpthread.so.0 [0x374020de70] /opt/third-party/mysql/product/current/bin/mysqld(Item_sum::print(String*, enum_query_type)+0x7f) [0x5238f1] /opt/third-party/mysql/product/current/bin/mysqld(Item::print_item_w_name(String*, enum_query_type)+0x64) [0x5013fe] /opt/third-party/mysql/product/current/bin/mysqld(st_select_lex::print(THD*, String*, enum_query_type)+0x1a0) [0x655594] /opt/third-party/mysql/product/current/bin/mysqld(st_select_lex_unit::print(String*, enum_query_type)+0xeb) [0x4ee693] /opt/third-party/mysql/product/current/bin/mysqld(mysqld_show_create(THD*, TABLE_LIST*)+0xda6) [0x760e34] /opt/third-party/mysql/product/current/bin/mysqld(mysql_execute_command(THD*)+0x37b6) [0x5fbfa6] /opt/third-party/mysql/product/current/bin/mysqld(mysql_parse(THD*, char const*, unsigned int, char const**)+0x20a) [0x6034a2] /opt/third-party/mysql/product/current/bin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x1362) [0x5f7c98] /opt/third-party/mysql/product/current/bin/mysqld(do_command(THD*)+0x114) [0x5f6932] /opt/third-party/mysql/product/current/bin/mysqld(handle_one_connection+0xd31) [0x5f1ca9] /lib64/libpthread.so.0 [0x37402062f7] /lib64/libc.so.6(clone+0x6d) [0x373fad1b6d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x7d9b590 = SHOW CREATE TABLE `test`.`macsi_games_daily` thd->thread_id=11 thd->killed=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. 100714 11:05:53 mysqld_safe Number of processes running now: 0 100714 11:05:53 mysqld_safe mysqld restarted InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 100714 11:05:53 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Last MySQL binlog file position 0 8536262, file name /opt/third-party/mysql/product/current/log/binarylog/binlog.047253 100714 11:05:53 InnoDB: Started; log sequence number 178 77930512 100714 11:05:53 [Note] Recovering after a crash using /opt/third-party/mysql/product/current/log/binarylog/binlog 100714 11:05:53 [Note] Starting crash recovery... 100714 11:05:53 [Note] Crash recovery finished. 100714 11:05:54 [Note] Event Scheduler: Loaded 0 events 100714 11:05:54 [Note] /opt/third-party/mysql/product/current/bin/mysqld: ready for connections. Version: '5.1.32-enterprise-gpl-pro-log' socket: '/opt/third-party/mysql/product/current/tmp/mysql.sock' port: 6033 MySQL Enterprise Server - Pro Edition (GPL) 100714 11:05:54 - 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=8384512 read_buffer_size=131072 max_used_connections=1 max_threads=1000 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2194336 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x1ed23750 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 = 0x41acd110 thread_stack 0x40000 /opt/third-party/mysql/product/current/bin/mysqld(my_print_stacktrace+0x20) [0x9d9824] /opt/third-party/mysql/product/current/bin/mysqld(handle_segfault+0x368) [0x5ece78] /lib64/libpthread.so.0 [0x374020de70] /opt/third-party/mysql/product/current/bin/mysqld(Item_sum::print(String*, enum_query_type)+0x7f) [0x5238f1] /opt/third-party/mysql/product/current/bin/mysqld(Item::print_item_w_name(String*, enum_query_type)+0x64) [0x5013fe] /opt/third-party/mysql/product/current/bin/mysqld(st_select_lex::print(THD*, String*, enum_query_type)+0x1a0) [0x655594] /opt/third-party/mysql/product/current/bin/mysqld(st_select_lex_unit::print(String*, enum_query_type)+0xeb) [0x4ee693] /opt/third-party/mysql/product/current/bin/mysqld(mysqld_show_create(THD*, TABLE_LIST*)+0xda6) [0x760e34] /opt/third-party/mysql/product/current/bin/mysqld(mysql_execute_command(THD*)+0x37b6) [0x5fbfa6] /opt/third-party/mysql/product/current/bin/mysqld(mysql_parse(THD*, char const*, unsigned int, char const**)+0x20a) [0x6034a2] /opt/third-party/mysql/product/current/bin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x1362) [0x5f7c98] /opt/third-party/mysql/product/current/bin/mysqld(do_command(THD*)+0x114) [0x5f6932] /opt/third-party/mysql/product/current/bin/mysqld(handle_one_connection+0xd31) [0x5f1ca9] /lib64/libpthread.so.0 [0x37402062f7] /lib64/libc.so.6(clone+0x6d) [0x373fad1b6d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x1ed7f650 = SHOW CREATE TABLE `test`.`macsi_games_daily` thd->thread_id=1 thd->killed=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. 100714 11:05:54 mysqld_safe Number of processes running now: 0 100714 11:05:54 mysqld_safe mysqld restarted InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 100714 11:05:54 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Last MySQL binlog file position 0 8536262, file name /opt/third-party/mysql/product/current/log/binarylog/binlog.047253 100714 11:05:55 InnoDB: Started; log sequence number 178 77930512 100714 11:05:55 [Note] Recovering after a crash using /opt/third-party/mysql/product/current/log/binarylog/binlog 100714 11:05:55 [Note] Starting crash recovery... 100714 11:05:55 [Note] Crash recovery finished. 100714 11:05:55 [Note] Event Scheduler: Loaded 0 events 100714 11:05:55 [Note] /opt/third-party/mysql/product/current/bin/mysqld: ready for connections. Version: '5.1.32-enterprise-gpl-pro-log' socket: '/opt/third-party/mysql/product/current/tmp/mysql.sock' port: 6033 MySQL Enterprise Server - Pro Edition (GPL) 100714 11:05:58 - 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=8384512 read_buffer_size=131072 max_used_connections=12 max_threads=1000 threads_connected=12 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2194336 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x231de970 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 = 0x4624f110 thread_stack 0x40000 /opt/third-party/mysql/product/current/bin/mysqld(my_print_stacktrace+0x20) [0x9d9824] /opt/third-party/mysql/product/current/bin/mysqld(handle_segfault+0x368) [0x5ece78] /lib64/libpthread.so.0 [0x374020de70] /opt/third-party/mysql/product/current/bin/mysqld(Item_sum::print(String*, enum_query_type)+0x7f) [0x5238f1] /opt/third-party/mysql/product/current/bin/mysqld(Item::print_item_w_name(String*, enum_query_type)+0x64) [0x5013fe] /opt/third-party/mysql/product/current/bin/mysqld(st_select_lex::print(THD*, String*, enum_query_type)+0x1a0) [0x655594] /opt/third-party/mysql/product/current/bin/mysqld(st_select_lex_unit::print(String*, enum_query_type)+0xeb) [0x4ee693] /opt/third-party/mysql/product/current/bin/mysqld(mysqld_show_create(THD*, TABLE_LIST*)+0xda6) [0x760e34] /opt/third-party/mysql/product/current/bin/mysqld(mysql_execute_command(THD*)+0x37b6) [0x5fbfa6] /opt/third-party/mysql/product/current/bin/mysqld(mysql_parse(THD*, char const*, unsigned int, char const**)+0x20a) [0x6034a2] /opt/third-party/mysql/product/current/bin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x1362) [0x5f7c98] /opt/third-party/mysql/product/current/bin/mysqld(do_command(THD*)+0x114) [0x5f6932] /opt/third-party/mysql/product/current/bin/mysqld(handle_one_connection+0xd31) [0x5f1ca9] /lib64/libpthread.so.0 [0x37402062f7] /lib64/libc.so.6(clone+0x6d) [0x373fad1b6d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x231e9e00 = SHOW CREATE VIEW `test`.`macsi_games_daily` thd->thread_id=12 thd->killed=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. 100714 11:05:58 mysqld_safe Number of processes running now: 0 100714 11:05:58 mysqld_safe mysqld restarted InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 100714 11:05:59 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Last MySQL binlog file position 0 8536262, file name /opt/third-party/mysql/product/current/log/binarylog/binlog.047253 100714 11:05:59 InnoDB: Started; log sequence number 178 77930512 100714 11:05:59 [Note] Recovering after a crash using /opt/third-party/mysql/product/current/log/binarylog/binlog 100714 11:05:59 [Note] Starting crash recovery... 100714 11:05:59 [Note] Crash recovery finished. 100714 11:05:59 [Note] Event Scheduler: Loaded 0 events 100714 11:05:59 [Note] /opt/third-party/mysql/product/current/bin/mysqld: ready for connections. Version: '5.1.32-enterprise-gpl-pro-log' socket: '/opt/third-party/mysql/product/current/tmp/mysql.sock' port: 6033 MySQL Enterprise Server - Pro Edition (GPL) 100714 11:06:06 - 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=8384512 read_buffer_size=131072 max_used_connections=15 max_threads=1000 threads_connected=15 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2194336 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x17f15aa0 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 = 0x46111110 thread_stack 0x40000 /opt/third-party/mysql/product/current/bin/mysqld(my_print_stacktrace+0x20) [0x9d9824] /opt/third-party/mysql/product/current/bin/mysqld(handle_segfault+0x368) [0x5ece78] /lib64/libpthread.so.0 [0x374020de70] /opt/third-party/mysql/product/current/bin/mysqld(Item_sum::print(String*, enum_query_type)+0x7f) [0x5238f1] /opt/third-party/mysql/product/current/bin/mysqld(Item::print_item_w_name(String*, enum_query_type)+0x64) [0x5013fe] /opt/third-party/mysql/product/current/bin/mysqld(st_select_lex::print(THD*, String*, enum_query_type)+0x1a0) [0x655594] /opt/third-party/mysql/product/current/bin/mysqld(st_select_lex_unit::print(String*, enum_query_type)+0xeb) [0x4ee693] /opt/third-party/mysql/product/current/bin/mysqld(mysqld_show_create(THD*, TABLE_LIST*)+0xda6) [0x760e34] /opt/third-party/mysql/product/current/bin/mysqld(mysql_execute_command(THD*)+0x37b6) [0x5fbfa6] /opt/third-party/mysql/product/current/bin/mysqld(mysql_parse(THD*, char const*, unsigned int, char const**)+0x20a) [0x6034a2] /opt/third-party/mysql/product/current/bin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x1362) [0x5f7c98] /opt/third-party/mysql/product/current/bin/mysqld(do_command(THD*)+0x114) [0x5f6932] /opt/third-party/mysql/product/current/bin/mysqld(handle_one_connection+0xd31) [0x5f1ca9] /lib64/libpthread.so.0 [0x37402062f7] /lib64/libc.so.6(clone+0x6d) [0x373fad1b6d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x17f20380 = SHOW CREATE VIEW `test`.`macsi_games_daily` thd->thread_id=16 thd->killed=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. 100714 11:06:06 mysqld_safe Number of processes running now: 0 100714 11:06:07 mysqld_safe mysqld restarted InnoDB: Log scan progressed past the checkpoint lsn 178 77930512 100714 11:06:07 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 178 78069323 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 5 row operations to undo InnoDB: Trx id counter is 0 200259584 100714 11:06:07 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 161906, file name /opt/third-party/mysql/product/current/log/binarylog/binlog.047257 InnoDB: Starting in background the rollback of uncommitted transactions 100714 11:06:08 InnoDB: Rolling back trx with id 0 200259313, 5 rows to undo 100714 11:06:08 InnoDB: Started; log sequence number 178 78069323 100714 11:06:08 [Note] Recovering after a crash using /opt/third-party/mysql/product/current/log/binarylog/binlog 100714 11:06:08 [Note] Starting crash recovery... 100714 11:06:08 [Note] Crash recovery finished. InnoDB: Rolling back of trx id 0 200259313 completed 100714 11:06:08 InnoDB: Rollback of non-prepared transactions completed 100714 11:06:08 [Note] Event Scheduler: Loaded 0 events 100714 11:06:08 [Note] /opt/third-party/mysql/product/current/bin/mysqld: ready for connections. Version: '5.1.32-enterprise-gpl-pro-log' socket: '/opt/third-party/mysql/product/current/tmp/mysql.sock' port: 6033 MySQL Enterprise Server - Pro Edition (GPL) 100714 11:06:17 - 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=8384512 read_buffer_size=131072 max_used_connections=12 max_threads=1000 threads_connected=12 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2194336 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0xc9ea390 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 = 0x45e24110 thread_stack 0x40000 /opt/third-party/mysql/product/current/bin/mysqld(my_print_stacktrace+0x20) [0x9d9824] /opt/third-party/mysql/product/current/bin/mysqld(handle_segfault+0x368) [0x5ece78] /lib64/libpthread.so.0 [0x374020de70] /opt/third-party/mysql/product/current/bin/mysqld(Item_sum::print(String*, enum_query_type)+0x8e) [0x523900] /opt/third-party/mysql/product/current/bin/mysqld(Item::print_item_w_name(String*, enum_query_type)+0x64) [0x5013fe] /opt/third-party/mysql/product/current/bin/mysqld(st_select_lex::print(THD*, String*, enum_query_type)+0x1a0) [0x655594] /opt/third-party/mysql/product/current/bin/mysqld(st_select_lex_unit::print(String*, enum_query_type)+0xeb) [0x4ee693] /opt/third-party/mysql/product/current/bin/mysqld(mysqld_show_create(THD*, TABLE_LIST*)+0xda6) [0x760e34] /opt/third-party/mysql/product/current/bin/mysqld(mysql_execute_command(THD*)+0x37b6) [0x5fbfa6] /opt/third-party/mysql/product/current/bin/mysqld(mysql_parse(THD*, char const*, unsigned int, char const**)+0x20a) [0x6034a2] /opt/third-party/mysql/product/current/bin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x1362) [0x5f7c98] /opt/third-party/mysql/product/current/bin/mysqld(do_command(THD*)+0x114) [0x5f6932] /opt/third-party/mysql/product/current/bin/mysqld(handle_one_connection+0xd31) [0x5f1ca9] /lib64/libpthread.so.0 [0x37402062f7] /lib64/libc.so.6(clone+0x6d) [0x373fad1b6d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0xc9f5840 = SHOW CREATE TABLE `test`.`macsi_games_weekly` thd->thread_id=12 thd->killed=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. 100714 11:06:17 mysqld_safe Number of processes running now: 0 100714 11:06:17 mysqld_safe mysqld restarted InnoDB: Log scan progressed past the checkpoint lsn 178 77930512 100714 11:06:17 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 178 78069542 100714 11:06:18 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 161906, file name /opt/third-party/mysql/product/current/log/binarylog/binlog.047257 100714 11:06:19 InnoDB: Started; log sequence number 178 78069542 100714 11:06:19 [Note] Recovering after a crash using /opt/third-party/mysql/product/current/log/binarylog/binlog 100714 11:06:19 [Note] Starting crash recovery... 100714 11:06:19 [Note] Crash recovery finished. 100714 11:06:19 [Note] Event Scheduler: Loaded 0 events 100714 11:06:19 [Note] /opt/third-party/mysql/product/current/bin/mysqld: ready for connections. Version: '5.1.32-enterprise-gpl-pro-log' socket: '/opt/third-party/mysql/product/current/tmp/mysql.sock' port: 6033 MySQL Enterprise Server - Pro Edition (GPL)