Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-32835

MySQL Crash when rebooted the VM everything works fine

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 10.11.6
    • N/A
    • N/A
    • 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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            Areeb Muhammad Areeb Ali
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.