MySQL Bugs: #118805: mysqld fails to start

Bug #118805	mysqld fails to start
Submitted:	9 Aug 12:04	Modified:	19 Aug 7:27
Reporter:	Michael Brice	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Pluggable Authentication	Severity:	S2 (Serious)
Version:	8.0.30, 8.0.43, 8.4.6	OS:	Windows (11 Pro)
Assigned to:		CPU Architecture:	x86 (64 bit)

Description:
User root has lost privileges so I am trying to start mysql with the --skip-grant-tables option.

I added the following to the end of the my.ini file
# For debugging and recovery only #
skip-grant-tables

Then attempted to restart the mysql service
The error log contained the following content

2025-08-09T11:27:44.583326Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: trx0sys.cc:643:UT_LIST_GET_LEN(trx_sys->mysql_trx_list) == 0 thread 6456

How to repeat:
Any attempt to start mysql service fails with the same error diagnostics

We're sorry, but the bug system is not the appropriate forum for asking help on using MySQL products. Your problem is not the result of a bug.

For details on getting support for MySQL products see http://www.mysql.com/support/
You can also check our forums (free) at http://forums.mysql.com/

Thank you for your interest in MySQL.

I am rather surprised at the response I have received. I provide details of a scenario where MySQL fails to start. Rather than taking the issue seriously I am told to contact the help desk as I do not know how to start MySQL. If I am polite I might say that the individual providing this response did not take the time to read and validate my experience. I have worked in IT for over 40 years, and this looks like a simple bug. I don't expect a constructive response.

I could repeat the issue on 8.0.43.
o) Started server like:
D:\my\mysql-commercial-8.0.43-winx64>bin\mysqld --basedir=. --datadir=data --console --innodb-buffer-pool-size=8G --innodb-redo-log-capacity=2G --innodb-log-buffer-size=512M --skip-log-bin  --log-error-verbosity=3 

o) ran some random inserts into some tables

o) shutdown cleanly

o) tried start again with --skip-grant-tables

2025-08-19T06:20:52.138321Z 0 [Note] [MY-011240] [Server] Plugin mysqlx reported: 'Using SSL configuration from MySQL Server'
2025-08-19T06:20:52.154821Z 0 [Note] [MY-011243] [Server] Plugin mysqlx reported: 'Using OpenSSL for TLS connections'
2025-08-19T06:20:52.156688Z 0 [System] [MY-010931] [Server] D:\my\mysql-commercial-8.0.43-winx64\bin\mysqld.exe: ready for connections. Version: '8.0.43-commercial'  socket: ''  port: 0  MySQL Enterprise Server - Commercial.
2025-08-19T06:20:52.157196Z 0 [ERROR] [MY-010131] [Server] TCP/IP, --shared-memory, or --named-pipe should be configured on NT OS
2025-08-19T06:20:52.157509Z 0 [ERROR] [MY-010119] [Server] Aborting
2025-08-19T06:20:52.284744Z 0 [Note] [MY-012330] [InnoDB] FTS optimize thread exiting.
2025-08-19T06:20:52.928104Z 0 [Note] [MY-010120] [Server] Binlog end
2025-08-19T06:20:52.929098Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'mysqlx'
<cut>

2025-08-19T06:20:52.937948Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'InnoDB'
2025-08-19T06:20:52.938281Z 0 [Note] [MY-013072] [InnoDB] Starting shutdown...
2025-08-19T06:20:52.939989Z 0 [Note] [MY-011946] [InnoDB] Buffer pool(s) load completed at 250819  8:20:52
2025-08-19T06:20:52.940289Z 0 [Note] [MY-011944] [InnoDB] Dumping buffer pool(s) to D:\my\mysql-commercial-8.0.43-winx64\data\ib_buffer_pool
2025-08-19T06:20:52.948913Z 0 [Note] [MY-011944] [InnoDB] Buffer pool(s) dump completed at 250819  8:20:52
2025-08-19T06:20:53.381944Z 0 [Note] [MY-013084] [InnoDB] Log background threads are being closed...
2025-08-19T06:20:53.740442Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: trx0sys.cc:644:UT_LIST_GET_LEN(trx_sys->mysql_trx_list) == 0 thread 40564
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.
2025-08-19T06:20:53Z 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...
7ff6624a627d    mysqld.exe!my_print_stacktrace()[stacktrace.cc:478]
7ff6622ea6ef    mysqld.exe!print_fatal_signal()[signal_handler.cc:159]
7ff6622ea4ba    mysqld.exe!my_server_abort()[signal_handler.cc:271]
7ff6624a1566    mysqld.exe!my_abort()[my_init.cc:269]
7ff66254ea76    mysqld.exe!ut_dbg_assertion_failed()[ut0dbg.cc:100]
7ff66218c5fa    mysqld.exe!trx_sys_close()[trx0sys.cc:644]
7ff660ff9dbb    mysqld.exe!srv_shutdown()[srv0start.cc:3074]
7ff6612aab90    mysqld.exe!innodb_shutdown()[ha_innodb.cc:1615]
7ff6612aa9d1    mysqld.exe!ha_finalize_handlerton()[handler.cc:740]
7ff6610713a3    mysqld.exe!plugin_deinitialize()[sql_plugin.cc:1121]
7ff66100f927    mysqld.exe!reap_plugins()[sql_plugin.cc:1190]
7ff6612448a4    mysqld.exe!plugin_shutdown()[sql_plugin.cc:2090]
7ff6611a63fd    mysqld.exe!clean_up()[mysqld.cc:2648]
7ff6612983ce    mysqld.exe!unireg_abort()[mysqld.cc:2499]
7ff6621e95d2    mysqld.exe!setup_conn_event_handler_threads()[mysqld.cc:3348]
7ff6611a5299    mysqld.exe!win_main()[mysqld.cc:8289]
7ff66116a75a    mysqld.exe!mysql_service()[mysqld.cc:8384]
7ff66116a5e1    mysqld.exe!mysqld_main()[mysqld.cc:8600]
7ff66205ed24    mysqld.exe!__scrt_common_main_seh()[exe_common.inl:288]
7ffea78fe8d7    KERNEL32.DLL!BaseThreadInitThunk()
7ffea96dc34c    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.

Verified on 8.0.43

Same on 8.4.6.

2025-08-19T07:50:10.223535Z 0 [System] [MY-010931] [Server] D:\my\mysql-commercial-8.4.6-winx64\bin\mysqld.exe: ready for connections. Version: '8.4.6-commercial'  socket: ''  port: 0  MySQL Enterprise Server - Commercial.
2025-08-19T07:50:10.224687Z 0 [ERROR] [MY-010131] [Server] TCP/IP, --shared-memory, or --named-pipe should be configured on NT OS
2025-08-19T07:50:10.224985Z 0 [ERROR] [MY-010119] [Server] Aborting
<cut>
2025-08-19T07:50:10.959742Z 0 [Note] [MY-013072] [InnoDB] Starting shutdown...
2025-08-19T07:50:10.960598Z 0 [Note] [MY-011946] [InnoDB] Buffer pool(s) load completed at 250819  9:50:10
2025-08-19T07:50:10.961078Z 0 [Note] [MY-011944] [InnoDB] Dumping buffer pool(s) to D:\my\mysql-commercial-8.4.6-winx64\data\ib_buffer_pool
2025-08-19T07:50:10.967580Z 0 [Note] [MY-011944] [InnoDB] Buffer pool(s) dump completed at 250819  9:50:10
2025-08-19T07:50:11.426941Z 0 [Note] [MY-013084] [InnoDB] Log background threads are being closed...
2025-08-19T07:50:11.864553Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: trx0sys.cc:644:UT_LIST_GET_LEN(trx_sys->mysql_trx_list) == 0 thread 27148
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.4/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2025-08-19T07:50:11Z 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...
7ff6dcc79e79    mysqld.exe!my_print_stacktrace()[stacktrace.cc:478]
7ff6dc6ff8af    mysqld.exe!print_fatal_signal()[signal_handler.cc:323]
7ff6dc6ff67a    mysqld.exe!my_server_abort()[signal_handler.cc:448]
7ff6dcc74dd2    mysqld.exe!my_abort()[my_init.cc:272]
7ff6dcd3bc4a    mysqld.exe!ut_dbg_assertion_failed()[ut0dbg.cc:100]
7ff6dc51c4c6    mysqld.exe!trx_sys_close()[trx0sys.cc:644]
7ff6dbc28127    mysqld.exe!srv_shutdown()[srv0start.cc:3076]
7ff6dbc27724    mysqld.exe!innodb_shutdown()[ha_innodb.cc:1610]
7ff6dbc27339    mysqld.exe!ha_finalize_handlerton()[handler.cc:742]
7ff6dbd97b3f    mysqld.exe!plugin_deinitialize()[sql_plugin.cc:1130]
7ff6dbd976ad    mysqld.exe!reap_plugins()[sql_plugin.cc:1199]
7ff6dbf45daa    mysqld.exe!plugin_shutdown()[sql_plugin.cc:2069]
7ff6dbf444ed    mysqld.exe!clean_up()[mysqld.cc:2757]
7ff6dc090661    mysqld.exe!unireg_abort()[mysqld.cc:2563]
7ff6dc66f256    mysqld.exe!setup_conn_event_handler_threads()[mysqld.cc:3445]
7ff6dbe63822    mysqld.exe!win_main()[mysqld.cc:9911]
7ff6dbfddb3a    mysqld.exe!mysql_service()[mysqld.cc:10014]
7ff6dbfdd9c1    mysqld.exe!mysqld_main()[mysqld.cc:10231]
7ff6dc445f84    mysqld.exe!__scrt_common_main_seh()[exe_common.inl:288]
7ffea78fe8d7    KERNEL32.DLL!BaseThreadInitThunk()
7ffea96dc34c    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.

Hello from MySQL User Group in Japan.

Is it same as #108304 (marked as Not a Bug) ?

MySQL Bugs: #108304: mysqld.exe crashes --skip-grant-tables without --shared-memory or --named-pipe
https://bugs.mysql.com/bug.php?id=108304