mysql 报mysqld got signal 11 问题,哪位可以帮忙分析下Log?

[复制链接]
查看11 | 回复9 | 2013-2-25 14:51:24 | 显示全部楼层 |阅读模式
121120 13:56:59 - 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=268435456
read_buffer_size=1048576
max_used_connections=57
max_threads=5000
thread_count=12
connection_count=11
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 10556987 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x2aab043e0e10
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 = 0x4aa800d0 thread_stack 0x80000
/usr/local/webserver/mysql/libexec/mysqld(my_print_stacktrace+0x24) [0x8a9e44]
/usr/local/webserver/mysql/libexec/mysqld(handle_segfault+0x33b) [0x5d1ffb]
/lib64/libpthread.so.0 [0x3ad5c0ebe0]
/usr/local/webserver/mysql/libexec/mysqld(Field_varstring::sql_type(String&) const+0x9a) [0x5a222a]
/usr/local/webserver/mysql/libexec/mysqld(store_column_type(TABLE*, Field*, charset_info_st*, unsigned int)+0x6a) [0x6ffeda]
/usr/local/webserver/mysql/libexec/mysqld [0x70e331]
/usr/local/webserver/mysql/libexec/mysqld(get_all_tables(THD*, TABLE_LIST*, Item*)+0x459) [0x7075f9]
/usr/local/webserver/mysql/libexec/mysqld(get_schema_tables_result(JOIN*, enum_schema_table_state)+0x1d0) [0x6fdb80]
/usr/local/webserver/mysql/libexec/mysqld(JOIN::exec()+0x439) [0x65b8f9]
/usr/local/webserver/mysql/libexec/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List[I]&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*)+0x198) [0x65dbd8]
/usr/local/webserver/mysql/libexec/mysqld(handle_select(THD*, LEX*, select_result*, unsigned long)+0x16f) [0x65e51f]
/usr/local/webserver/mysql/libexec/mysqld [0x5df08b]
/usr/local/webserver/mysql/libexec/mysqld(mysql_execute_command(THD*)+0x2786) [0x5e26b6]
/usr/local/webserver/mysql/libexec/mysqld(mysql_parse(THD*, char const*, unsigned int, char const**)+0x230) [0x5e6220]
/usr/local/webserver/mysql/libexec/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x987) [0x5e6bb7]
/usr/local/webserver/mysql/libexec/mysqld(do_command(THD*)+0xc2) [0x5e7712]
/usr/local/webserver/mysql/libexec/mysqld(do_handle_one_connection(THD*)+0x65a) [0x5d993a]
/usr/local/webserver/mysql/libexec/mysqld(handle_one_connection+0x9) [0x5d9fc9]
/lib64/libpthread.so.0 [0x3ad5c0677d]
/lib64/libc.so.6(clone+0x6d) [0x3ad54d325d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x2aab042ae1c0 is an invalid pointer
thd->thread_id=299827
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.
121120 13:56:59 mysqld_safe Number of processes running now: 0
121120 13:56:59 mysqld_safe mysqld restarted
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
121120 13:56:59InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 695697903098
121120 13:56:59InnoDB: 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 695703145472
InnoDB: Doing recovery: scanned up to log sequence number 695708388352
InnoDB: Doing recovery: scanned up to log sequence number 695713631232
InnoDB: Doing recovery: scanned up to log sequence number 695718874112
InnoDB: Doing recovery: scanned up to log sequence number 695724116992
InnoDB: Doing recovery: scanned up to log sequence number 695729359872
InnoDB: Doing recovery: scanned up to log sequence number 695734602752
InnoDB: Doing recovery: scanned up to log sequence number 695739845632
InnoDB: Doing recovery: scanned up to log sequence number 695740037589
121120 13:57:00InnoDB: 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 130678811, file name /home/mysql/binlog/binlog.000130
121120 13:57:34 InnoDB Plugin 1.0.6 started; log sequence number 695740037589
121120 13:57:34 [Warning] 'user' entry '[email protected]' ignored in --skip-name-resolve mode.
121120 13:57:34 [Warning] 'user' entry '@dev.da-mai.com' ignored in --skip-name-resolve mode.
121120 13:57:34 [ERROR] /usr/local/webserver/mysql/libexec/mysqld: Table './mysql/event' is marked as crashed and should be repaired
121120 13:57:34 [Warning] Checking table: './mysql/event'
121120 13:57:34 [ERROR] 1 client is using or hasn't closed the table properly
121120 13:57:34 [Note] Event Scheduler: Loaded 16 events
121120 13:57:34 [Note] /usr/local/webserver/mysql/libexec/mysqld: ready for connections.
Version: '5.5.3-m3'socket: '/tmp/mysql.sock'port: 3306Source distribution
121120 13:57:34 [Note] Event Scheduler: scheduler thread started with id 1
121120 13:57:34 [ERROR] /usr/local/webserver/mysql/libexec/mysqld: Table './damai/auth_item' is marked as crashed and should be repaired
121120 13:57:34 [Warning] Checking table: './damai/auth_item'
121120 13:57:34 [ERROR] /usr/local/webserver/mysql/libexec/mysqld: Table './damai/auth_assignment' is marked as crashed and should be repaired
121120 13:57:34 [Warning] Checking table: './damai/auth_assignment'
121120 13:57:34 [ERROR] /usr/local/webserver/mysql/libexec/mysqld: Table './damai/operation_log' is marked as crashed and should be repaired
121120 13:57:34 [Warning] Checking table: './damai/operation_log'
121120 13:57:38 [ERROR] /usr/local/webserver/mysql/libexec/mysqld: Table './trace/piwik_log_action' is marked as crashed and should be repaired
121120 13:57:38 [Warning] Checking table: './trace/piwik_log_action'
121120 13:57:41 [ERROR] /usr/local/webserver/mysql/libexec/mysqld: Table './damai/ztc0027' is marked as crashed and should be repaired
121120 13:57:41 [Warning] Checking table: './damai/ztc0027'
121120 13:57:41 [ERROR] /usr/local/webserver/mysql/libexec/mysqld: Table './damai/shop' is marked as crashed and should be repaired
121120 13:57:41 [Warning] Checking table: './damai/shop'
121120 13:57:41 [ERROR] /usr/local/webserver/mysql/libexec/mysqld: Table './damai/trade0002' is marked as crashed and should be repaired
121120 13:57:41 [Warning] Checking table: './damai/trade0002'
121120 13:57:43 [ERROR] /usr/local/webserver/mysql/libexec/mysqld: Table './trace/piwik_log_visit' is marked as crashed and should be repaired
121120 13:57:43 [Warning] Checking table: './trace/piwik_log_visit'
121120 13:57:43 [ERROR] /usr/local/webserver/mysql/libexec/mysqld: Table './trace/piwik_log_link_visit_action' is marked as crashed and should be repaired
121120 13:57:43 [Warning] Checking table: './trace/piwik_log_link_visit_action'
121120 13:57:45 [ERROR] /usr/local/webserver/mysql/libexec/mysqld: Table './mysql/proc' is marked as crashed and should be repaired
121120 13:57:45 [Warning] Checking table: './mysql/proc'
121120 13:57:45 [ERROR] 1 client is using or hasn't closed the table properly
121120 13:57:53 [ERROR] /usr/local/webserver/mysql/libexec/mysqld: Table './damai/message' is marked as crashed and should be repaired
121120 13:57:53 [Warning] Checking table: './damai/message'
121120 13:57:53 [ERROR] 1 client is using or hasn't closed the table properly

回复

使用道具 举报

千问 | 2013-2-25 14:51:24 | 显示全部楼层
这种log应该怎么看,不知如何下手
回复

使用道具 举报

千问 | 2013-2-25 14:51:24 | 显示全部楼层
类似ERROR] /usr/local/webserver/mysql/libexec/mysqld: Table './damai/auth_item' is marked as crashed and should be repaired
修复表 之前干了啥
回复

使用道具 举报

千问 | 2013-2-25 14:51:24 | 显示全部楼层
之前mysql自动重启了,所以才会出现reparied.现在
就想知道在log里如何查出会重启的原因
回复

使用道具 举报

千问 | 2013-2-25 14:51:24 | 显示全部楼层
不是说了吗
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.

回复

使用道具 举报

千问 | 2013-2-25 14:51:24 | 显示全部楼层
不是说了吗
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.

回复

使用道具 举报

千问 | 2013-2-25 14:51:24 | 显示全部楼层
表文件损坏,需要修改相关表!
回复

使用道具 举报

千问 | 2013-2-25 14:51:24 | 显示全部楼层
之前遇见过一次,一个表坏了,只要一读这个表,mysql就crash.
回复

使用道具 举报

千问 | 2013-2-25 14:51:24 | 显示全部楼层
日志确实提示表损坏了,同时也提示内存的使用可能超过了mysql支持的上限。
我之32位MYSQL-5.5 前做压力测试时把innodb缓冲池设置为2G,在400多用户并发的情况下,导致mysql总的内存消耗超过了4G,多次被linux强制关闭,然后又被mysql_safe脚本重启了,如此反复最后导致LINUX文件系统崩溃的情况。
回复

使用道具 举报

千问 | 2013-2-25 14:51:24 | 显示全部楼层
查哪可以知道是哪个表损坏导致crash
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

主题

0

回帖

4882万

积分

论坛元老

Rank: 8Rank: 8

积分
48824836
热门排行