Bug #105251 MySQL 8 Windows Service stops, standalone is fine
Submitted: 18 Oct 2021 16:28 Modified: 18 Oct 2021 17:32
Reporter: William Harrelson Email Updates:
Status: Unsupported Impact on me:
Category:MySQL Server Severity:S1 (Critical)
Version:8.0.25 OS:Windows (Server 2019)
Assigned to: CPU Architecture:Any
Tags: server, service, stopping, windows

[18 Oct 2021 16:28] William Harrelson
We've been running MySQL version 8.0.25 for a few months as a windows service on a Windows Server 2019 machine. A couple of days ago the machine re-booted, and now the service won't start.

The mysqld exe runs fine from the command line, but when started as a service it just starts, writes some lines to the log and shuts down. I've tried adding verbose logging but there is no clue there except that the line 'Event Scheduler: schedular thread started' which appears in the console for the command line never appears in the log.

Error log doesn't say much:
2021-10-17T17:43:02.834385Z 0 [System] [MY-010116] [Server] E:\xxx\xxx\bin\mysqld.exe (mysqld 8.0.25) starting as process 1228
2021-10-17T17:43:02.855801Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2021-10-17T17:43:03.496818Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2021-10-17T17:43:03.827140Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060
2021-10-17T17:43:03.922093Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2021-10-17T17:43:03.922996Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.

and that's it...

Chat from community:
From the command line, you ran the exact command used by the service, and the server keeps running, accepts connections?
--Yes, that's correct, exact same command on command line as on service start. (Except --console added on command line) Yes, keeps running and accepts connections, WordPress on top appears to work flawlessly.

Those times in the log above correspond exactly to when the server "didn't start" as you say?

When you start the service, MySQL appears in the Task Manager process list then disappears?

What does the Windows event log say about it?

--event log at that time:
Faulting application name: mysqld.exe, version:, time stamp: 0x6082efcd
Faulting module name: mysqld.exe, version:, time stamp: 0x6082efcd
Exception code: 0xc0000409
Fault offset: 0x00000000016c36f9
Faulting process id: 0x4cc
Faulting application start time: 0x01d7c37e6ef93f16
Faulting application path: E:\Bitnami\mysql\bin\mysqld.exe
Faulting module path: E:\Bitnami\mysql\bin\mysqld.exe
Report Id: 06d678f5-d3cc-4b0c-8ce9-e3cacab037bf
Faulting package full name:
Faulting package-relative application ID:

which appears to be STATUS_STACK_BUFFER_OVERRUN but I don't know what to do about that.

What does services.msc say about the service
- sc querex wampstackMySQL returns:
WIN32_EXIT_CODE : 0 (0x0)
WAIT_HINT : 0x7d0
PID : 0

So, community says appears to be an issue for bugs.mysql.com

How to repeat:
No clue how to repeat.  Problem appeared after a server re-boot.  Other server with same system configuration runs fine after re-boot.  Server works fine
[18 Oct 2021 17:32] MySQL Verification Team
Thank you for the bug report. This bug system does not support wampserver instances instalation, please upgrade to 8.0.26 using Oracle MySQL install package in this process remember to backup data directory.