[MDEV-28519] mysqld got exception 0x80000003 Created: 2022-05-09  Updated: 2022-06-15  Resolved: 2022-06-15

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.4.24
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Aran Ariel Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Environment:

Windows 11 Home using Xampp server 3.3.0

Attachments: Text File mysql_error.log     Text File mysqld got exception 0x80000003.txt     File test.sql    

 Description   

Everything appeared to be working fine, until I started receiving the following error.
This is a new installation of Xampp server on Windows 11 home.

Attached are the results of the mysql error log.

This is the the message received from the Xampp control panel:

2:00:11 PM [mysql] Status change detected: stopped
2:00:11 PM [mysql] Error: MySQL shutdown unexpectedly.
2:00:11 PM [mysql] This may be due to a blocked port, missing dependencies,
2:00:11 PM [mysql] improper privileges, a crash, or a shutdown by another method.
2:00:11 PM [mysql] Press the Logs button to view error logs and check
2:00:11 PM [mysql] the Windows Event Viewer for more clues
2:00:11 PM [mysql] If you need more help, copy and post this
2:00:11 PM [mysql] entire log window on the forums

 Comments   
Comment by Daniel Black [ 2022-05-09 ]

The log file is showing a crash recovery. Do you have logs of the original crash?

How was your demo2 database created? Was it running the same mariadb version when it was installed?

Comment by Marko Mäkelä [ 2022-05-10 ]

To get proper stack traces, .pdb files would be needed. I’ve heard that unlike the packages that MariaDB distributes for Microsoft Windows, XAMPP does not include them.

Comment by Aran Ariel [ 2022-05-11 ]

Hi Daniel, yes I have the logs of the original crash and apologies for the delay in reply. I created the demos database manually in phpmyadmin and the table was created using a script that I have just now uploaded. I reccovered by reinstalling xampp. Attaced iis the errror log

Comment by Aran Ariel [ 2022-05-11 ]

Thank you Marko ... got it

Comment by Daniel Black [ 2022-05-11 ]

Your uploaded mysql_error.log appears to be the same as the original mysqld got exception 0x80000003.txt. Do you have the original one of the crash before the startup in crash recovery mode?

I tried your sql file on 10.4.25+16cebed54065ad9e18953aa86d48f6007d53c2d3 and 10.4.24 linux containers and they both loaded successfully.

10.4.25+16cebed54065ad9e18953aa86d48f6007d53c2d3

 
$ podman run --rm --env MARIADB_ROOT_PASSWORD=bob --env MARIADB_DATABASE=test --env MARIADB_USER=test --env MARIADB_PASSWORD=test -v /tmp/d:/docker-entrypoint-initdb.d:z quay.io/mariadb-foundation/mariadb-devel:10.4
 
2022-05-11 03:51:36+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.4.25+maria~focal started.
 
 
 
2022-05-11 03:51:52+00:00 [Note] [Entrypoint]: Giving user test access to schema test
 
 
 
2022-05-11 03:51:52+00:00 [Note] [Entrypoint]: /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/test.sql
 
 
 
2022-05-11 03:51:53+00:00 [Note] [Entrypoint]: Stopping temporary server

So this could either be a windows specific bug or something hardware related. Can you check the event viewer to see if there's anything specific there. This is such a basic sql test I cannot force aspects of it that would not be tested in CI.

Generated at Thu Feb 08 10:01:22 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.