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

main.flush_ssl failed in buildbot upon Aria recovery

    XMLWordPrintable

Details

    Description

      http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/15836

      10.4 f95288211ce1023e0d268229fbe5febb

      main.flush_ssl                           w4 [ fail ]
              Test ended at 2019-11-23 05:15:15
       
      CURRENT_TEST: main.flush_ssl
       
       
      Server [mysqld.1 - pid: 9540, winpid: 9540, exit: 256] failed during test run
      Server log from this test:
      ----------SERVER LOG START-----------
      2019-11-23  5:15:15 0 [Note] D:/win32-debug/build/sql//Debug/mysqld.exe (mysqld 10.4.11-MariaDB-debug-log) starting as process 11260 ...
      Cannot find checkpoint record at LSN (1,0x8ef7)
      2019-11-23  5:15:15 0 [ERROR] mysqld.exe: Aria recovery failed. Please run aria_chk -r on all Aria tables and delete all aria_log.######## files
      2019-11-23  5:15:15 0 [ERROR] Plugin 'Aria' init function returned error.
      2019-11-23  5:15:15 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
      

      http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/15832

      10.4 cb6d7c3ee3e3e90ed46d3d1d58be6bac

      main.flush_ssl                           w1 [ fail ]
              Test ended at 2019-11-22 11:18:36
       
      CURRENT_TEST: main.flush_ssl
       
       
      Server [mysqld.1 - pid: 10488, winpid: 10488, exit: 65280] failed during test run
      Server log from this test:
      ----------SERVER LOG START-----------
      2019-11-22 11:18:34 0 [Note] D:/win32-debug/build/sql//Debug/mysqld.exe (mysqld 10.4.11-MariaDB-debug-log) starting as process 10728 ...
      Assertion failed: log_record_type_descriptor[type].rclass == LOGRECTYPE_FIXEDLENGTH || log_record_type_descriptor[type].rclass == LOGRECTYPE_PSEUDOFIXEDLENGTH, file D:\win32-debug\build\src\storage\maria\ma_loghandler.c, line 2531
      191122 11:18:34 [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.4.11-MariaDB-debug-log
      key_buffer_size=1048576
      read_buffer_size=131072
      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 = 3635 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]
      ucrtbase.DLL!raise()
      ucrtbase.DLL!abort()
      ucrtbase.DLL!_get_wpgmptr()
      ucrtbase.DLL!_get_wpgmptr()
      ucrtbase.DLL!_wassert()
      mysqld.exe!translog_get_total_chunk_length()[ma_loghandler.c:2528]
      mysqld.exe!translog_get_next_chunk()[ma_loghandler.c:6887]
      mysqld.exe!translog_variable_length_header()[ma_loghandler.c:7059]
      mysqld.exe!translog_read_record_header_from_buffer()[ma_loghandler.c:7173]
      mysqld.exe!translog_read_record_header()[ma_loghandler.c:7227]
      mysqld.exe!parse_checkpoint_record()[ma_recovery.c:3256]
      mysqld.exe!maria_apply_log()[ma_recovery.c:339]
      mysqld.exe!maria_recovery_from_log()[ma_recovery.c:239]
      mysqld.exe!ha_maria_init()[ha_maria.cc:3612]
      mysqld.exe!ha_initialize_handlerton()[handler.cc:557]
      mysqld.exe!plugin_initialize()[sql_plugin.cc:1438]
      mysqld.exe!plugin_init()[sql_plugin.cc:1720]
      mysqld.exe!init_server_components()[mysqld.cc:5199]
      mysqld.exe!win_main()[mysqld.cc:5722]
      mysqld.exe!mysql_service()[mysqld.cc:5964]
      mysqld.exe!mysqld_main()[mysqld.cc:6156]
      mysqld.exe!main()[main.cc:25]
      mysqld.exe!__scrt_common_main_seh()[exe_common.inl:288]
      KERNEL32.DLL!BaseThreadInitThunk()
      ntdll.dll!RtlInitializeExceptionChain()
      ntdll.dll!RtlInitializeExceptionChain()
      The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      information that should help you find out what is causing the crash.
      Writing a core file at D:\win32-debug\build\mysql-test\var\1\mysqld.1\data\
      Minidump written to D:\win32-debug\build\mysql-test\var\1\mysqld.1\data\mysqld.dmp
      ----------SERVER LOG END-------------
      

      Attachments

        Activity

          People

            vlad.lesin Vladislav Lesin
            elenst Elena Stepanova
            Votes:
            1 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.