Повреждение MySQL на MacBook Pro - PullRequest
0 голосов
/ 22 мая 2019

Последние несколько дней, когда я испытываю постоянные сбои mysql, похоже, что база данных повреждает ant, чем mysql постоянно перезапускается, но не может быть стабильной.Я проверил диск, но выглядит хорошо.Мне нужен совет, как прочитать эту ошибку и что проверить?

в журнале ошибок я нашел эту ошибку

2019-05-22T13:29:28.226689Z 0 [System] [MY-010116] [Server] /usr/local/opt/mysql/bin/mysqld (mysqld 8.0.16) starting as process 88218
2019-05-22T13:29:28.232672Z 0 [Warning] [MY-010159] [Server] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive
2019-05-22T13:29:28.326779Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-05-22T13:29:29.326903Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-05-22T13:29:30.401687Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-05-22T13:29:31.475526Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-05-22T13:29:32.545354Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-05-22T13:29:33.637548Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35
2019-05-22T13:29:33.637575Z 1 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:2509:success thread 123145356632064
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/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
13:29:33 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x7fabcb081400
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 = 7000033cdea0 thread_stack 0x46000
0   mysqld                              0x000000010b9d7443 my_print_stacktrace(unsigned char*, unsigned long) + 60
1   mysqld                              0x000000010b0a98d6 handle_fatal_signal + 438
2   libsystem_platform.dylib            0x00007fff6d9b6b5d _sigtramp + 29
3   ???                                 0x000000010ff19b76 0x0 + 4562459510
4   libsystem_c.dylib                   0x00007fff6d8706a6 abort + 127
5   mysqld                              0x000000010bccabdc ut_dbg_assertion_failed(char const*, char const*, unsigned long) + 332
6   mysqld                              0x000000010bb1ba53 Fil_shard::open_file(fil_node_t*, bool) + 791
7   mysqld                              0x000000010bb1d79d Fil_shard::open_system_tablespaces(unsigned long, unsigned long*) + 159
8   mysqld                              0x000000010bb1d86d Fil_system::open_all_system_tablespaces() + 57
9   mysqld                              0x000000010bc951a6 srv_start(bool, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) + 3002
10  mysqld                              0x000000010bb9180d innobase_ddse_dict_init(dict_init_mode_t, unsigned int, List<dd::Object_table const>*, List<Plugin_tablespace const>*) + 451
11  mysqld                              0x000000010b89cdba dd::bootstrap::DDSE_dict_init(THD*, dict_init_mode_t, unsigned int) + 108
12  mysqld                              0x000000010b9bdbae dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*) + 1805
13  mysqld                              0x000000010ad5e92a bootstrap::handle_bootstrap(void*) + 185
14  mysqld                              0x000000010bd1eea0 pfs_spawn_thread(void*) + 320
15  libsystem_pthread.dylib             0x00007fff6d9bf2eb _pthread_body + 126
16  libsystem_pthread.dylib             0x00007fff6d9c2249 _pthread_start + 66
17  libsystem_pthread.dylib             0x00007fff6d9be40d thread_start + 13

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): 
Connection ID (thread ID): 1
Status: NOT_KILLED
...