Skip to main content

Testing upgrading to MySQL 8.0.28 today and finding that MySQL crashes whenever I start up Tomcat. Anyone else hit this issue?

I'm on Windows Server 2012 R2.  A bit of searching indicates this might be a bug in mysql or database corruption.

This is the error I'm seeing in MySQL:

 

InnoDB: record PHYSICAL RECORD: n_fields 1; compact format; info bits 0
0: len 8; hex 696e66696d756d00; asc infimum ;;
2022-01-23T22:08:35.551075Z 0 [error] [MY-012442] [InnoDB] page [page id: space=89, page number=50] (252 records, index id 1841).
2022-01-23T22:08:35.553428Z 0 [error] [MY-012443] [InnoDB] Submit a detailed bug report to http://bugs.mysql.com
2022-01-23T22:22:45.205333Z 0 [error] [MY-012611] [InnoDB] Operating system error number 995 in a file operation.
2022-01-23T22:22:45.208138Z 0 [error] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
2022-01-23T22:22:45.313841Z 0 [error] [MY-012611] [InnoDB] Operating system error number 995 in a file operation.
2022-01-23T22:22:45.316145Z 0 [error] [MY-012617] [InnoDB] The error means that the I/O operation has been aborted because of either a thread exit or an application request. Retry attempt is made.
2022-01-23T22:22:45.313908Z 0 [error] [MY-013183] [InnoDB] Assertion failure: os0file.cc:3776:ret || GetLastError() != ERROR_IO_PENDING thread 7928

I saw a similar crash after successfully upgrade to 8.0.28.  mysqld crashed right after starting tomcat8 on my JSS server.  I'm running on the same OS.  Did you find an answer to this issue?

I noticed that my MSI was 8.0.27, but it somehow managed to upgrade to 8.0.28, which isn't listed as the recommended upgrade for JSS.  Another DBA in our organization had issues after upgrading to 8.0.28 on Linux OS.  I'm attempting to install 8.0.27 instead as that version should not have this issue.

@tbiles I rolled back and put it on the backburner, haven't had a chance to look at it since.

@tbiles I rolled back and put it on the backburner, haven't had a chance to look at it since.


Yeah, me too.  I have the 8.0.27 MSI but no matter what I do, it still tries to install 8.0.28, so there is something not working right with that MySQL installer.  I prefer to use MSI installers on Windows but I might have to punt and use the zip method if this isn't going to work properly.  There is clearly an incompatibility with 8.0.28 as it crashes immediately when starting the JAMF Tomcat instance.

I ran into the same problem while trying to install MySQL 8.0.28 on Win2012 R2.

The MSI installer worked fine but when Jamf is initializing the MySQL service gets stopped and has to be restarted via Server Tools in order to work. I can login and DB seems healthy, but something is definitly wrong if it has to be started manually. I rolled back and installed 8.0.27(.1), which worked instantly with JSS 10.36.

Yeah, me too.  I have the 8.0.27 MSI but no matter what I do, it still tries to install 8.0.28, so there is something not working right with that MySQL installer.  I prefer to use MSI installers on Windows but I might have to punt and use the zip method if this isn't going to work properly.  There is clearly an incompatibility with 8.0.28 as it crashes immediately when starting the JAMF Tomcat instance.


While installing using MSI installer 8.0.27.1 it automatically chooses 8.0.28. If you click on "MySQL Server" you can choose what version you want to install from the available upgrades. Hope this helps, if it's the same problem.

This seems to have been resolved in Jamf 10.37.2, no issues for me since updating to that version of Jamf and MySQL 8.0.28.

This seems to have been resolved in Jamf 10.37.2, no issues for me since updating to that version of Jamf and MySQL 8.0.28.


Are you running Windows 2012 R2 as the OS?

Are you running Windows 2012 R2 as the OS?


Yes, that is correct.

I have the same Problem here with 10.37.2 and MySQL 8.0.28 on Win2012R2. (Error 995 is in the Error Log, too)

Currently talking with support and hope 10.38 fixes it....

Bye, Frido.

I have the same Problem here with 10.37.2 and MySQL 8.0.28 on Win2012R2. (Error 995 is in the Error Log, too)

Currently talking with support and hope 10.38 fixes it....

Bye, Frido.


I've heard from others that the latest release fixed the issue and works
with MySQL 8.0.28, though I've not upgraded yet myself. Thanks for the
feedback.

--
Tim Biles
DevOps Engineering 3 | ITSS | itss.d.umn.edu
Research Cyberinfrastructure Champion | rcc.umn.edu
University of Minnesota Duluth | www.d.umn.edu
tbiles@d.umn.edu| 218-726-6959

Puzzling for me is that MySQL 8.0.28 is listed as compatible with 10.37.2, when there apparently is a problem (but might be limited to certain circumstances)

Reply


Terms & ConditionsCookie settings