[MDEV-32835] MySQL Crash when rebooted the VM everything works fine Created: 2023-11-18  Updated: 2024-01-16  Resolved: 2024-01-16

Status: Closed
Project: MariaDB Server
Component/s: N/A
Affects Version/s: 10.11.6
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Muhammad Areeb Ali Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: crash, innodb, mariadb, repair, serverdown
Environment:

Windows Server 2022 on proxmox VM 40gb RAM with AMD EPYCAMD EPYC™ 7502P 20 vCPU core



 Description   

Dear Support Team,

I trust this message finds you well. I am reaching out to bring your attention to a critical issue encountered with my dedicated MariaDB node this morning.

The MariaDB server unexpectedly ceased operations, resulting in a complete server shutdown. Upon inspection, the logs revealed the following error:

231118 8:30:25 [ERROR] mysqld got exception 0xc0000005;
This could be due to hitting a bug. It's also possible that this binary or one of the linked libraries is corrupt, improperly built, or misconfigured. Malfunctioning hardware could also be a cause.

To restore this, I promptly restarted the VM. However, after the complete reboot of my vm everything works fine now.
one more thing yesterday I forcefully turn off my VM after that this will happen plz guide me how can I repair my server

Here are pertinent details about the environment:

Server Version: MariaDB 10.11.5
Source Revision: 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c
Configuration Settings (my.ini):

[mysqld]
datadir=C:/Program Files/MariaDB 10.11/data
port=3306
 
InnoDB Buffer Pool Size (Consider your available RAM)
innodb_buffer_pool_size = 18G
 
InnoDB Log File Size
innodb_log_file_size = 2G # Increased for better performance
 
InnoDB File Format
innodb_file_format = Barracuda
 
InnoDB Log Configuration
innodb_flush_log_at_trx_commit = 2
innodb_doublewrite = 0
 
InnoDB Concurrency and I/O Settings
innodb_thread_concurrency = 0
innodb_io_capacity = 4000 # Increased
innodb_io_capacity_max = 8000 # Increased
innodb_buffer_pool_instances = 8
 
Query Cache (Enable it with a larger size)
query_cache_type = 1
query_cache_size = 512M # Increased for better performance
 
Thread and Table Cache Settings
thread_cache_size = 16
table_open_cache = 2048
 
Memory for Temporary Tables
max_heap_table_size = 256M
tmp_table_size = 256M
 
Join and Sort Buffer Sizes
join_buffer_size = 8M # Increased
sort_buffer_size = 8M # Increased
 
Maximum Connections
max_connections = 400
 
character-set-server=utf8mb4
 
[client]
port=3306
plugin-dir=C:\Program Files\MariaDB 10.11/lib/plugin

Given the nature of the error message and the recent forced VM stop, I am seeking your guidance on how to prevent this issue from reoccurring and ensure the stability of our MariaDB instance.

Thank you for your prompt attention to this matter. I look forward to your assistance in resolving this critical issue.



 Comments   
Comment by Daniel Black [ 2023-11-19 ]

Can you include the full backtrace of information and some information around the queries?

Can you install the debug symbols - https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/#installing-debugging-symbols-with-the-zip-package-on-windows.

Why did you make this block MDEV-32827? Given Galera isn't supported on Windows I don't see how the two could be related.

Comment by Vladislav Vaintroub [ 2023-11-19 ]

danblack, the debug symbols for the server(only) are also part of normal package. The crashing thread backtrace is usually good quality, perhaps Areeb can attach the error log. If mariadb.dmp or mysqld.dmp was produced in the data directory, you can attach it as well, it can be analyzed here.
Areeb, you can also safely disregard "corrupted, improperly built" or blaming hardware in the error message. It is just a mariadb bug.

Comment by Daniel Black [ 2023-11-23 ]

Areeb please provide the full error log and we might be able to correct this. There isn't sufficient information here to even guess as to what might be the cause.

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