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

9:40:59 PM [mysql] Error: MySQL shutdown unexpectedly. 9:40:59 PM

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 10.4.32
    • N/A
    • None
    • None
    • Microsoft 11 pro

    Description

      2024-09-24 21:40:45 0 [Note] mysqld.exe: Aria engine: starting recovery
      recovered pages: 0% 11% 21% 31%240924 21:40:45 [ERROR] mysqld got exception 0xc0000005 ;
      Sorry, we probably made a mistake, and this is a bug.
       
      Your assistance in bug reporting will enable us to fix this for the next release.
      To report this bug, see https://mariadb.com/kb/en/reporting-bugs
       
      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed, 
      something is definitely wrong and this may fail.
       
      Server version: 10.4.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
      key_buffer_size=16777216
      read_buffer_size=262144
      max_used_connections=0
      max_threads=65537
      thread_count=0
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 20304 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      VCRUNTIME140.dll!memcmp()
      mysqld.exe!parse_user()
      mysqld.exe!parse_user()
      mysqld.exe!parse_user()
      mysqld.exe!parse_user()
      mysqld.exe!parse_user()
      mysqld.exe!parse_user()
      mysqld.exe!parse_user()
      mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
      mysqld.exe!?plugin_dl_foreach@@YA_NPEAVTHD@@PEBUst_mysql_const_lex_string@@P6AD0PEAUst_plugin_int@@PEAX@Z3@Z()
      mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
      mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
      mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@Z()
      mysqld.exe!?win_main@@YAHHPEAPEAD@Z()
      mysqld.exe!?mysql_service@@YAXPEAX@Z()
      mysqld.exe!?mysqld_main@@YAHHPEAPEAD@Z()
      mysqld.exe!strxnmov()
      KERNEL32.DLL!BaseThreadInitThunk()
      ntdll.dll!RtlUserThreadStart()
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
      information that should help you find out what is causing the crash.
      Writing a core file at C:\xampp\mysql\data
      Minidump written to C:\xampp\mysql\data\mysqld.dmp
      2024-09-24 21:40:58 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 12848
      2024-09-24 21:40:58 0 [Note] mysqld.exe: Aria engine: starting recovery
      recovered pages: 0% 11% 21% 31%240924 21:40:58 [ERROR] mysqld got exception 0xc0000005 ;
      Sorry, we probably made a mistake, and this is a bug.
       
      Your assistance in bug reporting will enable us to fix this for the next release.
      To report this bug, see https://mariadb.com/kb/en/reporting-bugs
       
      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed, 
      something is definitely wrong and this may fail.
       
      Server version: 10.4.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
      key_buffer_size=16777216
      read_buffer_size=262144
      max_used_connections=0
      max_threads=65537
      thread_count=0
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 20304 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      VCRUNTIME140.dll!memcmp()
      mysqld.exe!parse_user()
      mysqld.exe!parse_user()
      mysqld.exe!parse_user()
      mysqld.exe!parse_user()
      mysqld.exe!parse_user()
      mysqld.exe!parse_user()
      mysqld.exe!parse_user()
      mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
      mysqld.exe!?plugin_dl_foreach@@YA_NPEAVTHD@@PEBUst_mysql_const_lex_string@@P6AD0PEAUst_plugin_int@@PEAX@Z3@Z()
      mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
      mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
      mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@Z()
      mysqld.exe!?win_main@@YAHHPEAPEAD@Z()
      mysqld.exe!?mysql_service@@YAXPEAX@Z()
      mysqld.exe!?mysqld_main@@YAHHPEAPEAD@Z()
      mysqld.exe!strxnmov()
      KERNEL32.DLL!BaseThreadInitThunk()
      ntdll.dll!RtlUserThreadStart()
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
      information that should help you find out what is causing the crash.
      Writing a core file at C:\xampp\mysql\data
      Minidump written to C:\xampp\mysql\data\mysqld.dmp
      

      Attachments

        Activity

          danblack Daniel Black added a comment - - edited

          From:

          2024-09-24 15:26:58 0 [Note] InnoDB: 10.4.32 started; log sequence number 311789; transaction id 352
          2024-09-24 15:26:58 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
          2024-09-24 15:26:58 0 [Note] Plugin 'FEEDBACK' is disabled.
          2024-09-24 15:26:58 0 [Note] Server socket created on IP: '::'.
          2024-09-24 16:25:30 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 23356
          Cannot find checkpoint record at LSN (1,0x5556)
          2024-09-24 16:25:30 0 [ERROR] mysqld.exe: Aria recovery failed. Please run aria_chk -r on all Aria tables and delete all aria_log.######## files
          2024-09-24 16:25:30 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
          

          This is the the server crashed (no shutdown messages after "Server socket created" and both InnoDB and Aria failed to recovery.

          It seems after this point some things where done to assist recovery further with a multitude of other innodb and aria errors.

          The crash of both at the same time is odd. Do you have some storage reliability issues?

          Note currently that 10.4 is now EOL - https://mariadb.org/about/#maintenance-policy

          Recommending checking/replacing your storage, restoring from backup, and upgrading to a newer maintained MariaDB version.

          danblack Daniel Black added a comment - - edited From: 2024-09-24 15:26:58 0 [Note] InnoDB: 10.4.32 started; log sequence number 311789; transaction id 352 2024-09-24 15:26:58 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool 2024-09-24 15:26:58 0 [Note] Plugin 'FEEDBACK' is disabled. 2024-09-24 15:26:58 0 [Note] Server socket created on IP: '::'. 2024-09-24 16:25:30 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 23356 Cannot find checkpoint record at LSN (1,0x5556) 2024-09-24 16:25:30 0 [ERROR] mysqld.exe: Aria recovery failed. Please run aria_chk -r on all Aria tables and delete all aria_log.######## files 2024-09-24 16:25:30 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. This is the the server crashed (no shutdown messages after "Server socket created" and both InnoDB and Aria failed to recovery. It seems after this point some things where done to assist recovery further with a multitude of other innodb and aria errors. The crash of both at the same time is odd. Do you have some storage reliability issues? Note currently that 10.4 is now EOL - https://mariadb.org/about/#maintenance-policy Recommending checking/replacing your storage, restoring from backup, and upgrading to a newer maintained MariaDB version.

          People

            Unassigned Unassigned
            GiedrėNa Giedre NArvilaite
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.