在配置文件my.ini中添加 skip-grants-table 参数后，程序无法启动
在给别人排错时遇到的问题，8.0.32 windows客户端：不添加skip-grants-table，可以正常启动。添加后就会报下面的错误：<p class="MsoNormal"><span lang="EN-US"> TCP/IP,--shared-memory, or --named-pipe should be configured on NT OS<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> </span></p>
解决方法：my.ini 文件的mysqld下添加shared-memory
https://blog.csdn.net/BigData_Mining/article/details/107040617
附上错误日志：前半部分是正常启动的日志
日志中，最后一部分提示的错误原因
看起来是数据文件损坏了或其他原因导致，如果确定只是因为多加了 --skip-grants-table 就导致报错的话，可以去报bug了
2023-04-05T12:55:37.579043Z 0 TCP/IP, --shared-memory, or --named-pipe should be configured on NT OS
2023-04-05T12:55:37.579470Z 0 Aborting
2023-04-05T12:55:38.701829Z 0 Assertion failure: trx0sys.cc:643:UT_LIST_GET_LEN(trx_sys->mysql_trx_list) == 0 thread 6320
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.
2023-04-05T12:55:38Z UTC - mysqld got exception 0x16 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
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...
7ff72e6a8408 mysqld.exe!?my_print_stacktrace@@YAXPEBEK@Z()
7ff72d826c01 mysqld.exe!?print_fatal_signal@@YAXH@Z()
7ff72d826943 mysqld.exe!?my_server_abort@@YAXXZ()
7ff72e68a75a mysqld.exe!?my_abort@@YAXXZ()
7ff72e8e62a9 mysqld.exe!?deallocate@?$allocator@V?$sub_match@V?$_String_const_iterator@V?$_String_val@U?$_Simple_types@D@std@@@std@@@std@@@std@@@std@@QEAAXQEAV?$sub_match@V?$_String_const_iterator@V?$_String_val@U?$_Simple_types@D@std@@@std@@@std@@@2@_K@Z()
7ff72e7a982e mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff72e8904ef mysqld.exe!?deallocate@?$allocator@V?$sub_match@V?$_String_const_iterator@V?$_String_val@U?$_Simple_types@D@std@@@std@@@std@@@std@@@std@@QEAAXQEAV?$sub_match@V?$_String_const_iterator@V?$_String_val@U?$_Simple_types@D@std@@@std@@@std@@@2@_K@Z()
7ff72e78441a mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff72d611dfb mysqld.exe!?ha_finalize_handlerton@@YAHPEAUst_plugin_int@@@Z()
7ff72d62ff34 mysqld.exe!?memcached_shutdown@@YAXXZ()
7ff72d635a48 mysqld.exe!?plugin_unlock_list@@YAXPEAVTHD@@PEAPEAUst_plugin_int@@_K@Z()
7ff72d634690 mysqld.exe!?plugin_shutdown@@YAXXZ()
7ff72d5cdb02 mysqld.exe!?check_valid_arguments_processor@Item_func@@UEAA_NPEAE@Z()
7ff72d5e0c0c mysqld.exe!?underflow@?$basic_stringbuf@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@MEAAHXZ()
7ff72d5df5bc mysqld.exe!?setup_conn_event_handler_threads@@YAXXZ()
7ff72d5e3159 mysqld.exe!?win_main@@YAHHPEAPEAD@Z()
7ff72d5db875 mysqld.exe!?mysql_service@@YAHPEAX@Z()
7ff72d5dbe7b mysqld.exe!?mysqld_main@@YAHHPEAPEAD@Z()
7ff72eecc9d4 mysqld.exe!?vio_write_shared_memory@@YA_KPEAUVio@@PEBE_K@Z()
7ffc705a26bd KERNEL32.DLL!BaseThreadInitThunk()
7ffc7194a9f8 ntdll.dll!RtlUserThreadStart()
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.
页:
[1]