mysql安装initializing database 报错
Beginning configuration step: Writing configuration file
Saving my.ini configuration file.
Saved my.ini configuration file.
Ended configuration step: Writing configuration file
Beginning configuration step: Updating Windows Firewall rules
Adding a Windows Firewall rule for MySQL80 on port 3306.
Attempting to add a Windows Firewall rule with command: netsh.exe advfirewall firewall add rule name="Port 3306" protocol=TCP localport=3306 dir=in action=allow
确定。
Successfully added the Windows Firewall rule.
Adding a Windows Firewall rule for MySQL80 on port 33060.
Attempting to add a Windows Firewall rule with command: netsh.exe advfirewall firewall add rule name="Port 33060" protocol=TCP localport=33060 dir=in action=allow
确定。
Successfully added the Windows Firewall rule.
Ended configuration step: Updating Windows Firewall rules
Beginning configuration step: Adjusting Windows service
Attempting to grant Network Service require filesystem permissions.
Granted permissions.
Adding new service
New service added
Ended configuration step: Adjusting Windows service
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.26.
Starting process with command: C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe --defaults-file="C:\ProgramData\MySQL\MySQL Server 8.0\my.ini" --console --initialize-insecure=on --lower-case-table-names=1.
'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe (mysqld 8.0.26) initializing of server in progress as process 8368
InnoDB initialization has started.
InnoDB initialization has ended.
A deprecated TLS version TLSv1 is enabled for channel mysql_main
A deprecated TLS version TLSv1.1 is enabled for channel mysql_main
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:2417:!index->is_clustered() || UT_LIST_GET_LEN(table->indexes) == 0 thread 8804
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to MySQL Bugs 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: MySQL :: MySQL 8.0 Reference Manual :: 15.21.3 Forcing InnoDB Recovery http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:27:50 UTC - mysqld got exception 0x80000003 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x1dd2bd5f100
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.
7ff6a30ea1a2 mysqld.exe!?my_errno@@YAHXZ()
7ffd6fe51881 ucrtbase.dll!raise()
7ffd6fe52851 ucrtbase.dll!abort()
7ff6a33159f2 mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff6a31db35c mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff6a31dad04 mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff6a330025c mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff6a31b42c1 mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff6a31a76ce mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff6a31b2ac7 mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff6a2365831 mysqld.exe!?create_tmp_table_from_fields@@YAPEAUTABLE@@PEAVTHD@@AEAV?$List@VCreate_field@@@@_N_KPEBD@Z()
7ff6a2365d57 mysqld.exe!?instantiate_tmp_table@@YA_NPEAVTHD@@PEAUTABLE@@@Z()
7ff6a2364fcd mysqld.exe!?create_tmp_table@@YAPEAUTABLE@@PEAVTHD@@PEAVTemp_table_param@@AEBV?$mem_root_deque@PEAVItem@@@@PEAUORDER@@_N4_K5PEBD@Z()
7ff6a20ffbc0 mysqld.exe!?convert_heap_table_to_ondisk@@YA_NPEAVTHD@@PEAUTABLE@@H@Z()
7ff6a210228d mysqld.exe!?mysql_schema_table@@YA_NPEAVTHD@@PEAULEX@@PEAUTABLE_LIST@@@Z()
7ff6a212e634 mysqld.exe!?open_and_lock_tables@@YA_NPEAVTHD@@PEAUTABLE_LIST@@IPEAVPrelocking_strategy@@@Z()
7ff6a2130c95 mysqld.exe!?open_tables@@YA_NPEAVTHD@@PEAPEAUTABLE_LIST@@PEAIIPEAVPrelocking_strategy@@@Z()
7ff6a21311aa mysqld.exe!?open_tables_for_query@@YA_NPEAVTHD@@PEAUTABLE_LIST@@I@Z()
7ff6a238f99c mysqld.exe!?mysql_create_view@@YA_NPEAVTHD@@PEAUTABLE_LIST@@W4enum_view_create_mode@@@Z()
7ff6a215d48c mysqld.exe!?mysql_execute_command@@YAHPEAVTHD@@_N@Z()
7ff6a21586df mysqld.exe!?dispatch_sql_command@@YAXPEAVTHD@@PEAVParser_state@@@Z()
7ff6a2003689 mysqld.exe!?next@File_command_iterator@bootstrap@@UEAAHAEAV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z()
7ff6a20030fe mysqld.exe!?end@Command_iterator@bootstrap@@UEAAXXZ()
7ff6a2003c47 mysqld.exe!?run_bootstrap_thread@bootstrap@@YA_NPEBDPEAUMYSQL_FILE@@P6A_NPEAVTHD@@@ZW4enum_thread_type@@@Z()
7ff6a34f9491 mysqld.exe!?set_compression_level@Zstd_comp@compression@transaction@binary_log@@UEAAXI@Z()
7ff6a30ea13c mysqld.exe!?my_thread_join@@YAHPEAUmy_thread_handle@@PEAPEAX@Z()
7ffd6fe01bb2 ucrtbase.dll!_configthreadlocale()
7ffd70517034 KERNEL32.DLL!BaseThreadInitThunk()
7ffd71f02651 ntdll.dll!RtlUserThreadStart()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (1dd2cf70f08): -- Copyright (c) 2017, 2021, Oracle and/or its affiliates.Status: NOT_KILLED
The manual page at MySQL :: MySQL 8.0 Reference Manual :: B.3.3.3 What to Do If MySQL Keeps Crashing 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 8368, was run successfully and exited with code -2147483645.
Failed to start process for MySQL Server 8.0.26.
Database initialization failed.
Ended configuration step: Initializing database (may take a long time)
无视继续安装即可。
我使用mysql安装包安装时出现同样情况，后来经老师提醒，才发现该报错可以无视掉。即安装程序即便中止在'database initialization failed'，但‘next'按钮仍可继续点击，接下来正常配置即可，最后安装完成。（压缩包安装出现这种问题我暂时还不会解决）