MySQL Forums
Forum List  »  General

Random MySQL crash on Windows
Posted by: Anthony Azzopardi
Date: October 05, 2022 05:10AM


We are running MySQL 8.0.27 on Windows Server 2019.

We have experienced an unexpected crash. The issue started with an error in both the Mysql log and the event viewer. The server was online for 13 hours from the first entry until a full crash.

--Event viewer (multiple entries of same error for over 12 hours until server crashed fully)

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: mysqld.exe (5240) consumed 437558235136 bytes, mtreportsrv.exe (2624) consumed 524464128 bytes, and mtreportsrv.exe (2108) consumed 519372800 bytes.

--MySQL Logs

2022-10-05T03:13:49.734784Z 539387 [ERROR] [MY-011072] [Server] Binary logging not possible. Message: An error occurred during sync stage of the commit. 'binlog_error_action' is set to 'ABORT_SERVER'. Server is being stopped..
03:13:49 UTC - mysqld got exception 0x80000003 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x2102e0d40f0
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...

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (2102d2dd358): COMMIT
Connection ID (thread ID): 539387

A restart was done in normal mode, Engine crashed again

2022-10-05T03:49:32.878021Z 0 [ERROR] [MY-010249] [Server] Can't create thread to handle new connection(errno= 1)
2022-10-05T04:05:24.997084Z 2579 [ERROR] [MY-010934] [Server] Out of memory (Needed 8071304 bytes)
2022-10-05T04:05:24.998690Z 2579 [ERROR] [MY-010934] [Server] Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space
2022-10-05T04:06:01.341288Z 2314 [ERROR] [MY-012611] [InnoDB] Operating system error number 1784 in a file operation.
2022-10-05T04:06:01.342869Z 2314 [ERROR] [MY-012646] [InnoDB] File .\#innodb_temp\temp_9.ibt: 'Windows aio' returned OS error 1884. Cannot continue operation
2022-10-05T04:06:01.344749Z 2314 [ERROR] [MY-012981] [InnoDB] Cannot continue operation.

Another restart in recovery mode was done and the engine started.

We stopped the engine one more time and removed temp file mentioned above, started engine in normal mode and all is working fine.

When checking our monitoring systems we did not exceed the memory threshold nor disk space (since an error in logs mentions virtual memory).

Has anyone experienced such behavior please?

Options: ReplyQuote

Written By
Random MySQL crash on Windows
October 05, 2022 05:10AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.