mysql 不能运行

Amazon 发布于 2017/01/20 11:26
阅读 308
收藏 0

2017-01-20T03:22:01.512714Z 0 [ERROR] [FATAL] InnoDB: Aborting because of a corrupt database page in the system tablespace. Or,  there was a failure in tagging the tablespace  as corrupt.
2017-01-20 11:22:01 0x7ffff06143c0  InnoDB: Assertion failure in thread 140737226294208 in file ut0ut.cc line 920
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
03:22:01 UTC - 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68214 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0 thread_stack 0x40000
0   mysqld                              0x0000000109194e4d my_print_stacktrace + 61
1   mysqld                              0x00000001090f49c0 handle_fatal_signal + 688
2   libsystem_platform.dylib            0x00007fffe79d4bba _sigtramp + 26
3   ???                                 0x00007fff57374b60 0x0 + 140734656629600
4   libsystem_c.dylib                   0x00007fffe785b420 abort + 129
5   mysqld                              0x0000000109420581 _Z23ut_dbg_assertion_failedPKcS0_m + 161
6   mysqld                              0x0000000109423d0c _ZN2ib5fatalD2Ev + 92
7   mysqld                              0x0000000109423dd9 _ZN2ib5fatalD1Ev + 9
8   mysqld                              0x000000010920be88 _Z20buf_page_io_completeP10buf_page_tb + 2680
9   mysqld                              0x0000000109222960 _ZL17buf_read_page_lowP7dberr_tbmmRK9page_id_tRK11page_size_tb + 864
10  mysqld                              0x00000001092229c8 _Z13buf_read_pageRK9page_id_tRK11page_size_t + 56
11  mysqld                              0x000000010920563f _Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb + 1743
12  mysqld                              0x0000000109407910 _Z31trx_rseg_get_n_undo_tablespacesPm + 352
13  mysqld                              0x00000001093e0bf0 _Z34innobase_start_or_create_for_mysqlv + 10832
14  mysqld                              0x00000001092d069a _ZL13innobase_initPv + 3962
15  mysqld                              0x00000001089142af _Z24ha_initialize_handlertonP13st_plugin_int + 79
16  mysqld                              0x000000010901fa61 _ZL17plugin_initializeP13st_plugin_int + 81
17  mysqld                              0x000000010901e77e _Z11plugin_initPiPPci + 1726
18  mysqld                              0x00000001090eb05f _Z11mysqld_mainiPPc + 3007
19  libdyld.dylib                       0x00007fffe77c7255 start + 1
20  ???                                 0x0000000000000007 0x0 + 7
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.
2017-01-20T03:22:11.735033Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-01-20T03:22:11.735249Z 0 [Warning] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2017-01-20T03:22:11.735292Z 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.7.12) starting as process 1250 ...
2017-01-20T03:22:11.737331Z 0 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/mysql/data/ is case insensitive
2017-01-20T03:22:11.738902Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-01-20T03:22:11.738931Z 0 [Note] InnoDB: Uses event mutexes
2017-01-20T03:22:11.738938Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-01-20T03:22:11.738942Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-01-20T03:22:11.739293Z 0 [Note] InnoDB: Number of pools: 1
2017-01-20T03:22:11.739405Z 0 [Note] InnoDB: Using CPU crc32 instructions
2017-01-20T03:22:11.749323Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-01-20T03:22:11.759476Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-01-20T03:22:11.775701Z 0 [ERROR] InnoDB: Database page corruption on disk or a failed file read of page [page id: space=0, page number=5]. You may have to recover from a backup.
2017-01-20T03:22:11.775737Z 0 [Note] InnoDB: Page dump in ascii and hex (16384 bytes):



各位,Mac下的mysql突然就不能用了,重启也失败 查看了日志,截取了部分,请帮忙看下


加载中
0
如比如比
如比如比
或许有帮助吧。http://www.voidcn.com/blog/tantexian/article/p-5038942.html
返回顶部
顶部