MySQL crashed

Asked 1 years ago, Updated 1 years ago, 423 views

I am using MySQL installed from Homebrew on my Mac.
When I tried to launch MySQL,
ERROR!The server quit without updating PID file(/usr/local/var/mysql/****.pid).
failed to boot with the boot.
For /usr/local/var/mysql/****.error, click

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.
2022-06-22T10:31:12.610310Z 0 [System] [MY-010116] [Server] /usr/local/Cellar/mysql/8.0.28_1/bin/mysqld(mysqld8.0.28) starting as process 41507
2022-06-22T10:31:12.614068Z 0 [Warning] [MY-010159] [Server] Setting lower_case_table_names=2because file system for /usr/local/var/mysql/is case sensitive
2022-06-22T10:31:12.630541Z1 [System][MY-013576][InnoDB]InnoDB initialization has started.
2022-06-22T10:31:12.854878Z1 [System][MY-013577][InnoDB]InnoDB initialization has ended.
2022-06-22T10:31:12.963602Z1 [ERROR] [MY-013183] [InnoDB] Assertion failure: dict0dict.cc:3378:for_table ||ref_table thread 0x700001d78000
InnoDB: Weintentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assignment failures or crashes, even
InnoDB: immediate 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.
10:31:12 UTC-mysqld got signal6;
Most likely, you have hit a bug, but this error can be caused by malware.
Thread pointer: 0x7fbb86814800
Attempting backtrace.You can use the following information to find out
where mysqld dead.If you see no messages after this, something wrong
terribly wrong...
stack_bottom = 700001d77f50 thread_stack0x100000
0mysqld0x00000001027e318e my_print_stacktrace(unsigned char const*, unsigned long)+60
1 mysqld0x0000000101ebbc90print_fal_signal(int)+412
2mysqld0x0000000101ebbe3d my_server_abort()+67
3mysqld0x00000001027ddcda my_abort()+10
4mysqld0x0000000102 aadb34ut_dbg_assertion_failed(char const*, char const*, unsigned long long)+394
5mysqld0x000000010288a0df dict_foreign_add_to_cache(dict_foreign_t*, char const**, bool, bool, dict_err_ignore_t) +1166
6mysqld0x00000001028999e4dd_table_load_fk_from_dd(dict_table_t*,dd::Table const*, char const**,dict_err_ignore_t,bool)+1630
7mysqld0x000000000102899b5b dd_table_load_fk(dd::cache::Dictionary_client*, char const*, char const**, dict_table_t*, dd::Table const*, THD*, bool, bool, std::_1::value<char const*, ut:allocor_latch::::dator_latch:
8mysqld0x000000010289 dca6dict_table_t*dd_open_table_one<dd::Table>(dd::cache::Dictionary_client*, TABLE const*, char const*, dd::Table const*, THD*, std:::_1::demand<char const,*:dat:::::docor:::docor
9mysqld0x0000000102891fb2dict_table_t*dd_open_table<dd:::Table>(dd::cache::Dictionary_client*, TABLE const*, char const*, dd:::Table const*, THD*)+57
10mysqld0x0000000102891df0dd_table_open_on_dd_obj(THD*,dd::cache::Dictionary_client*,dd::Table const&,dd::Partition const*,char const*,dict_table_t*&,TABLE const*)+1393
11 mysqld0x0000000102892bc2dd_table_open_on_id_low (THD*, MDL_ticket**, unsigned long) + 1246
12mysqld0x0000000102892179dd_table_open_on_id(unsigned long long, THD*, MDL_ticket**, bool, bool)+385
13mysqld0x00000001029 dba67 MetadataRecover::apply()+69
14mysqld0x0000000102a7248d srv_dict_recover_on_restart()+183
15mysqld0x000000010295c8be innobase_dict_recover(dict_recovery_mode_t, unsigned int)+2005
16 mysqld0x000000000102699814dd::bootstrap::restart(THD*)+240
17mysqld0x00000001027cade8dd::upgrade_57::restart_dictionary(THD*)+76
18mysqld0x0000000001027c9697dd::upgrade_57::do_pre_checks_and_initialize_dd(THD*)+1334
19mysqld0x0000000101ad3b21 bootstrap::handle_bootstrap(void*)+225
20mysqld0x0000000102b14daf pfs_spawn_thread(void*)+335
21 libsystem_pthread.dylib0x00007fff204498fc_pthread_start+224
22 libsystem_pthread.dylib0x00007ffff20445443 thread_start+15

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

appears.
Recently, when I started Mac, there was a sentence that looked like a problem, so I thought the InnoDB was damaged because of that, so I tried to back it up and fix it, but it said zsh:permission denied:backup.dump and I couldn't.
I would like to keep the contents of the DB, so please tell me how to back up and repair it, or how to repair it without erasing the DB data.

MacBookPro-Intel-BigSur
MySQL-Ver 8.0.28 for macos 11.6 on x86_64 (Homebrew)

Thank you for your cooperation.

mysql

2022-09-30 22:03

1 Answers

The error message is correct.The manual contains a set of instructions.
Are you referencing it?

The following is the site of Oracle (MySQL).There is a description in Japanese.

https://dev.mysql.com/doc/refman/8.0/ja/innodb-limits.html
It's a little different from the content, but if you can give me a hint.


2022-09-30 22:03

If you have any answers or tips


© 2024 OneMinuteCode. All rights reserved.