Description:
In the production environment, I discovered that the mysqld service automatically shut down.
The following logs are extracted from the .err file (timezone: UTC+9), with four main segments:
[1] 14:12:16 - First occurrence of write failure to #ib_16384_0.dblwr file
[2] 2025-08-08 23:17:11 0x1868 INNODB MONITOR OUTPUT - First monitoring output
[3] 2025-08-08 23:28:42 0x1868 INNODB MONITOR OUTPUT - Final monitoring output
[4] Log entries immediately preceding mysqld service termination
This section describes only the content of the fourth segment. Additional log information will be submitted as an attachment.
[4]
2025-08-08T14:28:47.129217Z 0 [Warning] [MY-012638] [InnoDB] Retry attempts for writing partial data failed.
2025-08-08T14:28:47.129462Z 0 [ERROR] [MY-013676] [InnoDB] I/O error while writing to file: .\#ib_16384_0.dblwr. Retrying ...
InnoDB: ###### Diagnostic info printed to the standard error stream
2025-08-08T14:28:50.891291Z 0 [ERROR] [MY-012872] [InnoDB] [FATAL] Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
2025-08-08T14:28:50.897769Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: srv0srv.cc:1879:ib::fatal triggered thread 6240
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-08T14:28:50Z 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...
2025-08-08T14:28:57.144929Z 0 [Warning] [MY-012638] [InnoDB] Retry attempts for writing partial data failed.
2025-08-08T14:28:57.145175Z 0 [ERROR] [MY-013676] [InnoDB] I/O error while writing to file: .\#ib_16384_0.dblwr. Retrying ...
7ff7e49ce318 mysqld.exe!my_print_stacktrace()[stacktrace.cc:430]
7ff7e3b41751 mysqld.exe!print_fatal_signal()[signal_handler.cc:159]
7ff7e3b41493 mysqld.exe!my_server_abort()[signal_handler.cc:270]
7ff7e49b293a mysqld.exe!my_abort()[my_init.cc:264]
7ff7e4b83729 mysqld.exe!ut_dbg_assertion_failed()[ut0dbg.cc:100]
7ff7e4a96973 mysqld.exe!ib::fatal::~fatal()[ut0ut.cc:523]
7ff7e4a61e56 mysqld.exe!srv_error_monitor_thread()[srv0srv.cc:1882]
7ff7e4a47a3e mysqld.exe!Detached_thread::operator()<void (__cdecl*)(void)>()[os0thread-create.h:193]
7ff7e4a47bc5 mysqld.exe!std::thread::_Invoke<std::tuple<Detached_thread,void (__cdecl*)(void)>,0,1>()[thread:56]
7ffefacb268a ucrtbase.dll!_o_exp()
7ffefd9d7974 KERNEL32.DLL!BaseThreadInitThunk()
7ffefe6da371 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.
How to repeat:
We encountered this issue unexpectedly while using MySQL via Entity Framework Core (EF Core), without any explicit row or table locking in place. The server is a Dell PowerEdge R250 configured with RAID 1 storage.
