Description:
== the below show in errlog
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.
...
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...
== the below are show in /var/log/messages
Jul 14 11:05:59 prd-hms-db01 AgentFramework[17458]: VCS ERROR V-16-1-13067 Thread(4145712016) Agent is calling clean for resource(MySQL_App) because the resource became OFFLINE unexpectedly, on its own.
Jul 14 11:05:59 prd-hms-db01 Had[17445]: VCS ERROR V-16-1-13067 (prd-hms-db01.prod.laxigames.com) Agent is calling clean for resource(MySQL_App) because the resource became OFFLINE unexpectedly, on its own.
Jul 14 11:05:59 prd-hms-db02 Had[8112]: VCS ERROR V-16-1-13067 (prd-hms-db01.prod.laxigames.com) Agent is calling clean for resource(MySQL_App) because the resource became OFFLINE unexpectedly, on its own.
Jul 14 11:06:00 prd-hms-db01 AgentFramework[17458]: VCS ERROR V-16-1-13068 Thread(4145712016) Resource(MySQL_App) - clean completed successfully
How to repeat:
not sure. it was happened once so far.
Suggested fix:
not sure.
