MySQL Bugs: #111625: MySql service wont start - "something has gone terribly wrong"

Bug #111625	MySql service wont start - "something has gone terribly wrong"
Submitted:	29 Jun 2023 23:35	Modified:	4 Jul 2023 12:29
Reporter:	Lachlan McEwen	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	8.0.33.0	OS:	Windows
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
I was adding a table and the workbench crashed. I am now unable to restart the MySql service, it says it started and then stopped again.

This is in the error log:

information that should help you find out what is causing the crash.
2023-06-28T03:23:46.832781Z 0 [Warning] [MY-011068] [Server] The syntax 'sync_master_info' is deprecated and will be removed in a future release. Please use sync_source_info instead.
2023-06-28T03:23:46.832818Z 0 [Warning] [MY-010915] [Server] '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.
2023-06-28T03:23:46.834668Z 0 [System] [MY-010116] [Server] C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld.exe (mysqld 8.0.33) starting as process 18060
2023-06-28T03:23:46.865048Z 0 [Warning] [MY-013907] [InnoDB] Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=100663296. Please use innodb_redo_log_capacity instead.
2023-06-28T03:23:46.869547Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2023-06-28T03:23:47.300245Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2023-06-28T03:23:47.336005Z 1 [System] [MY-011090] [Server] Data dictionary upgrading from version '80022' to '80023'.
2023-06-28T03:23:47.408746Z 1 [Warning] [MY-013021] [InnoDB] A transaction id in a record of table `mysql`.`tablespaces` is newer than the system-wide maximum.
2023-06-28T03:23:47Z UTC - mysqld got exception 0xc0000005 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x1d3d96454c0
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...
7ff7dbb4189b    mysqld.exe!?init@Rpl_info_values@@QEAA_NXZ()
7ff7dbb40c62    mysqld.exe!?init@Rpl_info_values@@QEAA_NXZ()
7ff7dba6ed7e    mysqld.exe!?init@Rpl_info_values@@QEAA_NXZ()
7ff7dba6a238    mysqld.exe!?init@Rpl_info_values@@QEAA_NXZ()
7ff7dabb6eee    mysqld.exe!?run_bootstrap_thread@bootstrap@@YA_NPEBDPEAUMYSQL_FILE@@P6A_NPEAVTHD@@@ZW4enum_thread_type@@@Z()
7ff7dc147029    mysqld.exe!?my_init_dynamic_array@@YA_NPEAUDYNAMIC_ARRAY@@IIPEAXII@Z()
7ff7dbbc3a8c    mysqld.exe!?my_thread_self_setname@@YAXPEBD@Z()
7ffc22971bb2    ucrtbase.dll!_configthreadlocale()
7ffc231c7614    KERNEL32.DLL!BaseThreadInitThunk()
7ffc251a26f1    ntdll.dll!RtlUserThreadStart()

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

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.

How to repeat:
Try to start the mysql service

Hi Mr. McEwen,

Thank you for your bug report.

However, it is not clear to us whether you report a bug in Workbench or in the MySQL Server.

Please, clarify this.

Next, what we need is a fully repeatable case that crashes Workbench or Server. We can not proceed without it. It should consist of a set of commands that always lead to the crash.

Next, we do not need the entire database. We just need the tables that are involved in that particular statement.

Can't repeat.

Hi,

Please, let us know if you need any other info ........

Hi, 

Thanks for your reply.

The bug is with MySql server becuase I cant start the mysql service.

To repeat I copy the files that I provided into the c;\programdata\mysql folder and try to start the MySql service.

Hi,

We did not have problems with starting MySQL 8.0.33 service at all.

And you have not sent us a fully repeatable test case that would show the problem.

to repeat:
- stop the mysql service
- rename the c:/programdata/mysql(version)/data folder
- make a new data folder and copy in the files that I provided
- try to start the mysql service

it will fail and the error will be logged to the .err file in the data folder

Hi Mr. McEwen,

Sorry, what you are doing is not supported  AT ALL.

Each datadir for the particular release of MySQL server must be configured properly with --initialize , as described in our manual.

Not a bug.