- 論壇徽章:
- 0
|
設備突然無法啟動mysqld，
日志如下：Starting MySQLStarting mysqld daemon with databases from /var/lib/mysql
STOPPING server from pid file /var/lib/mysql/mysql.pid。后邊就是在打點.......
101002 19:08:58 [Warning] Asked for 196608 thread stack, but got 126976
101002 19:08:58 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...
101002 19:08:58 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 25 3243784353.
InnoDB: Doing recovery: scanned up to log sequence number 25 3243784861
101002 19:08:58 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 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=0
read_buffer_size=1044480
max_used_connections=0
max_connections=200
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 408798 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=(nil)
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=0xbff3ecb8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x808fd07
0x82ee608
0x826ac19
0x8269835
0x82173d4
0x8218435
0x81fc791
0x823c303
0x81479e9
0x82ebdbc
0x831563a
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
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.
101002 19:08:58 mysqld ended
請高手幫忙 �。�！拜托了！ |
|
免費注冊
發(fā)表于 2010-10-02 20:16
發(fā)表于 2010-10-02 22:02
