WampServer

We installed Wamp 3.3.0 64 bit on Windows Datacenter Server 2019 and had nothing but problems with MySQL crashing. Here are the details:

Description:
1) The server did NOT crash running a specific query.

2) The log file generated an error "Operating system error number 1460 in a file operation." and "Assertion failure: os0file.cc:7022:slot->is_reserved thread 9968"

3) The MySQL attempted a backtrace and came back with " File .\undo_002: 'aio write' returned OS error 1560. Cannot continue operation"

4) The MySQL instance crashed.

5) I expected MySQl would recover from this operation but it did not.

6) We have searched your bug database and stack over flow, no one has this issue

It happens once a week but there is no way to reproduce. CPU spikes to
100% and then MySQL crashes. We then have to stop and start the service
for it to recover. Brand new server 24GB ram with SSD drives 4 CPU
Sockets and 16 Virtual Processors running on Hypervison with average CPU
of 28%

MySQL Bug reporting said it's a bug with v 8.0.30 and to rename the jemalloc to force the system to use the old malloc.

That did not work, any advise? Should we go back to the 32bit version and MySQL 5.7?

Hi,

MySQL says it's a bug. Wampserver is not intended to correct MySQL bugs.

You can upgrade to a more recent version of MySQL, e.g. 8.0.33 64bit.

All addons for Wampserver can be found at https://wampserver.aviatechno.net/

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons

Oracle says it's not a bug but a Windows Server issue. Here we go. Pointing fingers at each other. Oracle says it's Microsoft, Microsoft says it's Oracle.

See forum thread at MySQL I am battling with


[28 Jun 15:23] MySQL Eng User

How can you say this is NOT a bug when your company posted and say it IS a bug. Look at the URL below:

[support.oracle.com]

Windows Servers Crashing in jemalloc.dll and libcrypto-1_1-x64.dll (Doc ID 2904830.1)
Last updated on NOVEMBER 25, 2022

[29 Jun 12:23] MySQL Verification Team
Hi,

Yes, you are correct. The bug is in those two libraries that you are mentioning.

However, neither of those two libraries is made by us. Both are made by Microsoft. We can not fix something which is not our code and for which we do not have a source code.

That is why our bug, that you mentioned can not be fixed, since the bug is in the Windows OS. You can not read that, since this is internal information. Simply, that bug was waiting for he new versions of those Microsoft libraries, but Microsoft has not addressed those issues in the newer versions of the said libraries.

Not a bug.

Hi,

Try using MySQL 8.0.33 and……

- Verify that all VC ++ packages are installed and with the latest versions.
To do this, use the tool:
Checks VC++ packages installed
Do not use a previously loaded tool. Make a new download to make sure you are using the correct version.
To download missing packages, do not rely on Microsoft links, they are not reliable, download packages on http://wampserver.aviatechno.net in section Visual C++ Redistribuable Packages
Do not forget that if you have a 64 bit Windows, you must install both 32 and 64 bit versions of each package.
You must install each package "as an administrator", so right-click the exe file and then run as Administrator.

See : Best way to install Visual C++ Redistributable Packages
at the bottom of the site https://wampserver.aviatechno.net/

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons

It won't let me install the 8.0.33, it says that I have WAMP server 3.3.0 installed and this addon can only be done with 3.3.1

Install Wampserver 3.3.1 update.,

---------------------------------------------------------------
Documentation Apache - Documentation PHP - Documentation MySQL - Wampserver install files & addons

We are now getting this error message running 8.0.33 and Oracle says its a Windows Server 2019 issue.

2023-07-21T22:27:51.129125Z 0 [ERROR] [MY-012646] [InnoDB] File .\undo_001: 'aio write' returned OS error 0. Cannot continue operation
2023-07-21T22:27:51.133639Z 0 [ERROR] [MY-012981] [InnoDB] Cannot continue operation.