56,677
社区成员
发帖
与我相关
我的任务
分享我的mysql起不来，求指教
我的mysql在运行过程中挂了，起不来，下面是错误信息，求各位指教，我用的是mariadb 5.5
140529 09:47:46 mysqld_safe Starting mysqld daemon with databases from /data/mariadb
140529 9:47:46 InnoDB: The InnoDB memory heap is disabled
140529 9:47:46 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140529 9:47:46 InnoDB: Compressed tables use zlib 1.2.3
140529 9:47:46 InnoDB: Initializing buffer pool, size = 1010.0M
140529 9:47:46 InnoDB: Completed initialization of buffer pool
140529 9:47:46 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 111655782
140529 9:47:46 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 111678490
140529 9:47:46 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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
140529 9:47:46 InnoDB: Waiting for the background threads to start
InnoDB: Error: trying to access page number 7539 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
140529 9:47:46 InnoDB: Assertion failure in thread 140080771475200 in file fil0fil.c line 5451
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
140529 9:47:46 [ERROR] mysqld got signal 6 ;
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.
To report this bug, see http://kb.askmonty.org/en/reporting-bugs
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.
Server version: 5.5.34-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=1002
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2329269 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x0
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 = 0x0 thread_stack 0x48000
mysys/stacktrace.c:247(my_print_stacktrace)[0x9ca449]
sql/signal_handler.cc:153(handle_fatal_signal)[0x6956ea]
??:0(??)[0x31d780f710]
??:0(??)[0x31d7432925]
??:0(??)[0x31d7434105]
fil/fil0fil.c:5517(_fil_io)[0x874c02]
buf/buf0rea.c:234(buf_read_page_low)[0x84a8dc]
buf/buf0rea.c:455(buf_read_page)[0x84b39c]
buf/buf0buf.c:2577(buf_page_get_gen)[0x83ca88]
include/fut0fut.ic:53(fut_get_ptr)[0x87a2dc]
fsp/fsp0fsp.c:2113(fseg_inode_get)[0x87a3a9]
fsp/fsp0fsp.c:3645(fseg_free_step_not_header)[0x87a548]
trx/trx0purge.c:465(trx_purge_free_segment)[0x800fe1]
trx/trx0purge.c:655(trx_purge_truncate_history)[0x8014b6]
trx/trx0purge.c:1086(trx_purge_fetch_next_rec)[0x8015f0]
row/row0purge.c:749(row_purge)[0x8ce59f]
que/que0que.c:1259(que_thr_step)[0x8c4be5]
trx/trx0purge.c:1220(trx_purge)[0x7feede]
srv/srv0srv.c:4192(srv_purge_thread)[0x7f4ef4]
??:0(??)[0x31d78079d1]
??:0(??)[0x31d74e8b6d]
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.
140529 09:47:46 mysqld_safe mysqld from pid file /data/mariadb/mariadb.pid ended
140529 09:47:46 mysqld_safe Starting mysqld daemon with databases from /data/mariadb
140529 9:47:46 InnoDB: The InnoDB memory heap is disabled
140529 9:47:46 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140529 9:47:46 InnoDB: Compressed tables use zlib 1.2.3
140529 9:47:46 InnoDB: Initializing buffer pool, size = 1010.0M
140529 9:47:46 InnoDB: Completed initialization of buffer pool
140529 9:47:46 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 111655782
140529 9:47:46 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 111678490
140529 9:47:46 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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
140529 9:47:46 InnoDB: Waiting for the background threads to start
InnoDB: Error: trying to access page number 7539 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
140529 9:47:46 InnoDB: Assertion failure in thread 140080771475200 in file fil0fil.c line 5451
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
140529 9:47:46 [ERROR] mysqld got signal 6 ;
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.
To report this bug, see http://kb.askmonty.org/en/reporting-bugs
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.
Server version: 5.5.34-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=1002
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2329269 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x0
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 = 0x0 thread_stack 0x48000
mysys/stacktrace.c:247(my_print_stacktrace)[0x9ca449]
sql/signal_handler.cc:153(handle_fatal_signal)[0x6956ea]
??:0(??)[0x31d780f710]
??:0(??)[0x31d7432925]
??:0(??)[0x31d7434105]
fil/fil0fil.c:5517(_fil_io)[0x874c02]
buf/buf0rea.c:234(buf_read_page_low)[0x84a8dc]
buf/buf0rea.c:455(buf_read_page)[0x84b39c]
buf/buf0buf.c:2577(buf_page_get_gen)[0x83ca88]
include/fut0fut.ic:53(fut_get_ptr)[0x87a2dc]
fsp/fsp0fsp.c:2113(fseg_inode_get)[0x87a3a9]
fsp/fsp0fsp.c:3645(fseg_free_step_not_header)[0x87a548]
trx/trx0purge.c:465(trx_purge_free_segment)[0x800fe1]
trx/trx0purge.c:655(trx_purge_truncate_history)[0x8014b6]
trx/trx0purge.c:1086(trx_purge_fetch_next_rec)[0x8015f0]
row/row0purge.c:749(row_purge)[0x8ce59f]
que/que0que.c:1259(que_thr_step)[0x8c4be5]
trx/trx0purge.c:1220(trx_purge)[0x7feede]
srv/srv0srv.c:4192(srv_purge_thread)[0x7f4ef4]
??:0(??)[0x31d78079d1]
??:0(??)[0x31d74e8b6d]
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.
140529 09:47:46 mysqld_safe mysqld from pid file /data/mariadb/mariadb.pid ended
...全文
请发表友善的回复…
发表回复
九月茅桃 2014-06-07
- 打赏
- 举报
看到这里：
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=1002
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2329269 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
是否会是内存溢出了。
可以参考一下：http://blog.csdn.net/mchdba/article/details/13290891
gateslu 2014-05-29
- 打赏
- 举报
我是在虚拟机上运行的，今天电脑死机了，然后物理机也一起死了，虚拟机重新起来之后就不行了，难道每次都需要这样弄么？求指导！
rucypli 2014-05-29
- 打赏
- 举报
准备用备份还原吧
benluobo 2014-05-29
- 打赏
- 举报
可能跟你的硬盘有关
你可以试着换服务器
benluobo 2014-05-29
- 打赏
- 举报
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.
