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

MariaDB 10.3.27 crash on windows

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.3.27
    • 10.6.5
    • Microsoft Windows Server 2016 Standard
      VMware x-64 based PC.
      32 GB Memory
      mysqld Ver 10.3.27-MariaDB-log for Win64 on AMD64 (mariadb.org binary distribution)

    Description

      MariaDB server is getting crash by throwing the following error in .err file. Attached the .err file, crash dump file, my.ini file and "show variables" output for reference. It would be great if the reason and also the probable fix for the issue has been provided.

      InnoDB: ###### Diagnostic info printed to the standard error stream
      2021-01-19 22:19:04 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
      210119 22:19:04 [ERROR] mysqld got exception 0x80000003 ;
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware.
       
      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.3.27-MariaDB-log
      key_buffer_size=33554432
      read_buffer_size=8388608
      max_used_connections=66
      max_threads=65537
      thread_count=45
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 52116 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...
      mysqld.exe!my_sigabrt_handler()[my_thr_init.c:485]
      mysqld.exe!raise()[signal.cpp:547]
      mysqld.exe!abort()[abort.cpp:71]
      mysqld.exe!ib::fatal::~fatal()[ut0ut.cc:603]
      mysqld.exe!srv_error_monitor_thread()[srv0srv.cc:1833]
      KERNEL32.DLL!BaseThreadInitThunk()
      ntdll.dll!RtlUserThreadStart()
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
      information that should help you find out what is causing the crash.
      Writing a core file at C:\Program Files\McAfee\Network Security Manager\MariaDB\data\
      Minidump written to C:\Program Files\McAfee\Network Security Manager\MariaDB\data\mysqld.dmp
       

      Attachments

        1. WIN-G57FI8VPMSD.err
          8.73 MB
        2. WIN-4RVIN69VNHC.err
          1.28 MB
        3. stacks.txt
          140 kB
        4. screenshot-1.png
          screenshot-1.png
          453 kB
        5. mysqldpdb.7z
          9.36 MB
        6. mysqldexe.zip
          5.11 MB
        7. mysqld.dmp
          255 kB
        8. mysqld.dmp
          449 kB
        9. my.ini
          3 kB
        10. mdbvariables.txt
          458 kB

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              schandol srinivas chandolu
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.