安装mySQL8出现问题

安装mySQL8出现问题

第一次根据教程安装,datebase出现问题,查看log没看懂,点击Execute尝试第二次,结果datebase那一步直接消失了,进行start service失败

我就按照教学把mysql卸载了重新安装,还是到了datebase这一步,按日志搜索都是一些已经安装成功后才出现过的这些错误日志,实在是不知道怎么办了. 注: 计算机名字都是英文

Beginning configuration step: Initializing database (may take a long time)

Attempting to run MySQL Server with --initialize-insecure option...
Starting process for MySQL Server 8.0.33...
Starting process with command: D:\Tools Code\Mysql\bin\mysqld.exe --defaults-file="D:\Tools Code\Mysql\my.ini" --console --initialize-insecure=on --lower-case-table-names=1...
D:\Tools Code\Mysql\bin\mysqld.exe (mysqld 8.0.33) initializing of server in progress as process 26404
InnoDB initialization has started.
InnoDB initialization has ended.
root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
Invalid (old?) table or database name '系统'
Invalid (old?) table or database name '系统'
Invalid (old?) table or database name '系统'
Invalid (old?) table or database name '系统'
Invalid (old?) table or database name '系统'
Invalid (old?) table or database name '系统'
Invalid (old?) table or database name '系统'
Invalid (old?) table or database name '系统'
Invalid (old?) table or database name '系统'
Invalid (old?) table or database name '系统'
Invalid (old?) table or database name '系统'
Assertion failure: dict0dict.cc:2456:!index->is_clustered() || UT_LIST_GET_LEN(table->indexes) == 0 thread 16188
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-08-01T15:41:04Z UTC - mysqld got exception 0x16 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x27ac330aef0
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...
7ff797eb3298    mysqld.exe!?my_print_stacktrace@@YAXPEBEK@Z()
7ff79702c711    mysqld.exe!?print_fatal_signal@@YAXH@Z()
7ff79702c453    mysqld.exe!?my_server_abort@@YAXXZ()
7ff797e96c4a    mysqld.exe!?my_abort@@YAXXZ()
7ff798064859    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()
7ff797f4d0c6    mysqld.exe!?open@Zstd_dec@compression@transaction@binary_log@@UEAA_NXZ()
7ff797f4c8a4    mysqld.exe!?open@Zstd_dec@compression@transaction@binary_log@@UEAA_NXZ()
7ff79805bcd8    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()
7ff797eea3b6    mysqld.exe!?open@Zstd_dec@compression@transaction@binary_log@@UEAA_NXZ()
7ff797edbed6    mysqld.exe!?open@Zstd_dec@compression@transaction@binary_log@@UEAA_NXZ()
7ff797ee8b3c    mysqld.exe!?open@Zstd_dec@compression@transaction@binary_log@@UEAA_NXZ()
7ff79720bfc1    mysqld.exe!?create_tmp_table_from_fields@@YAPEAUTABLE@@PEAVTHD@@AEAV?$List@VCreate_field@@@@_N_KPEBD@Z()
7ff79720c527    mysqld.exe!?instantiate_tmp_table@@YA_NPEAVTHD@@PEAUTABLE@@@Z()
7ff79720b757    mysqld.exe!?create_tmp_table@@YAPEAUTABLE@@PEAVTHD@@PEAVTemp_table_param@@AEBV?$mem_root_deque@PEAVItem@@@@PEAUORDER@@_N4_K5PEBD@Z()
7ff796f801b7    mysqld.exe!?convert_heap_table_to_ondisk@@YA_NPEAVTHD@@PEAUTABLE@@H@Z()
7ff796f82c5d    mysqld.exe!?mysql_schema_table@@YA_NPEAVTHD@@PEAULEX@@PEAVTable_ref@@@Z()
7ff796fb08a4    mysqld.exe!?open_and_lock_tables@@YA_NPEAVTHD@@PEAVTable_ref@@IPEAVPrelocking_strategy@@@Z()
7ff796fb30e5    mysqld.exe!?open_tables@@YA_NPEAVTHD@@PEAPEAVTable_ref@@PEAIIPEAVPrelocking_strategy@@@Z()
7ff796fb35ea    mysqld.exe!?open_tables_for_query@@YA_NPEAVTHD@@PEAVTable_ref@@I@Z()
7ff797248755    mysqld.exe!?mysql_create_view@@YA_NPEAVTHD@@PEAVTable_ref@@W4enum_view_create_mode@@@Z()
7ff796fe55bb    mysqld.exe!?mysql_execute_command@@YAHPEAVTHD@@_N@Z()
7ff796fe03ef    mysqld.exe!?dispatch_sql_command@@YAXPEAVTHD@@PEAVParser_state@@@Z()
7ff796e96784    mysqld.exe!?next@File_command_iterator@bootstrap@@UEAAHAEAV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z()
7ff796e962be    mysqld.exe!?end@Command_iterator@bootstrap@@UEAAXXZ()
7ff796e96ef8    mysqld.exe!?run_bootstrap_thread@bootstrap@@YA_NPEBDPEAUMYSQL_FILE@@P6A_NPEAVTHD@@@ZW4enum_thread_type@@@Z()
7ff798427029    mysqld.exe!?my_init_dynamic_array@@YA_NPEAUDYNAMIC_ARRAY@@IIPEAXII@Z()
7ff797ea3a8c    mysqld.exe!?my_thread_self_setname@@YAXPEBD@Z()
7fff67759363    ucrtbase.dll!_recalloc()
7fff68ae26ad    KERNEL32.DLL!BaseThreadInitThunk()
7fff69faaa68    ntdll.dll!RtlUserThreadStart()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (27adcd40030): -- Copyright (c) 2017, 2023, Oracle and/or its affiliates.
--
-- This program is free software; you can redistribute it and/or modify
-- it under the terms of the GNU General Public License as published by
-- the Free Software Foundation; version 2 of the License.
--
-- This program is distributed in the hope that it will be useful,
-- but WITHOUT ANY WARRANTY; without even the implied warranty of
-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-- GNU General Public License for more details.
--
-- You should have received a copy of the GNU General Public License
-- along with this program; if not, write to the Free Software
-- Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
--
-- View: innodb_lock_waits
--
-- Give a snapshot of which InnoDB locks transactions are waiting for.
-- The lock waits are ordered by the age of the lock descending.
--
-- Versions: 8.0+
--
-- mysql> select * from sys.innodb_lock_waits\G
-- *************************** 1. row ********************
Connection ID (thread ID): 6
Status: NOT_KILLED
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.
Process for mysqld, with ID 26404, was run successfully and exited with code -2147483645.
Failed to start process for MySQL Server 8.0.33.
Database initialization failed.
Ended configuration step: Initializing database (may take a long time)
不知道你这个问题是否已经解决, 如果还没有解决的话:
  • 以下回答由chatgpt基于相关博客总结生成:

    我将尽力回答你的问题。请描述你要解决的具体问题或提供相应的问题描述。


如果你已经解决了该问题, 非常希望你能够分享一下解决方案, 写成博客, 将相关链接放在评论区, 以帮助更多的人 ^-^

根据你提供的日志信息，有可能是下边的问题：
（1）"Invalid (old?) table or database name '系统'" 错误可能是由于数据表或数据库名称中包含了非法字符导致的，要确保使用的表名和数据库名是合法的，不包含任何特殊字符。

你是在什么环境下安装sq 8的？