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

assert [FATAL] InnoDB: Unable to find charset-collation for 254 after upgrade from 10.11.4 to 11.0

    XMLWordPrintable

Details

    Description

      Once the I have upgraded from 10.11.4 version - MariaDB did not start.

      Crash dump is not showing symbols (dbgsym package is installed):

      Reading symbols from /usr/sbin/mariadbd...
      (No debugging symbols found in /usr/sbin/mariadbd)
      (gdb)

      Error log is showing:

      2023-06-09 9:23:25 0 [Note] InnoDB: Number of transaction pools: 1
      2023-06-09 9:23:25 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
      2023-06-09 9:23:25 0 [Note] InnoDB: Initializing buffer pool, total size = 4.000GiB, chunk size = 64.000MiB
      2023-06-09 9:23:25 0 [Note] InnoDB: Completed initialization of buffer pool
      2023-06-09 9:23:25 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
      2023-06-09 9:23:25 0 [Note] InnoDB: Upgrading the change buffer
      2023-06-09 9:23:25 0 [ERROR] [FATAL] InnoDB: Unable to find charset-collation for 254
      230609 9:23:25 [ERROR] mysqld got signal 6 ;
      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: 11.0.2-MariaDB-1:11.0.2+maria~ubu2204 source revision: 0005f2f06c8e1aea4915887decad67885108a929
      key_buffer_size=33554432
      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 = 25202972 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...
      stack_bottom = 0x0 thread_stack 0x49000
      /usr/sbin/mariadbd(my_print_stacktrace+0x32)[0x55712e8b1a62]
      /usr/sbin/mariadbd(handle_fatal_signal+0x488)[0x55712e384e28]
      libc_sigaction.c:0(__restore_rt)[0x7feb2b458520]
      nptl/pthread_kill.c:44(__pthread_kill_implementation)[0x7feb2b4aca7c]
      posix/raise.c:27(__GI_raise)[0x7feb2b458476]
      stdlib/abort.c:81(__GI_abort)[0x7feb2b43e7f3]
      /usr/sbin/mariadbd(+0x69753b)[0x55712df9953b]
      /usr/sbin/mariadbd(+0x6812f7)[0x55712df832f7]
      /usr/sbin/mariadbd(+0xdf703f)[0x55712e6f903f]
      /usr/sbin/mariadbd(+0xdd3c92)[0x55712e6d5c92]
      /usr/sbin/mariadbd(+0x6b2ebc)[0x55712dfb4ebc]
      /usr/sbin/mariadbd(+0x691449)[0x55712df93449]
      /usr/sbin/mariadbd(+0xd7aad9)[0x55712e67cad9]
      /usr/sbin/mariadbd(_Z24ha_initialize_handlertonP13st_plugin_int+0x86)[0x55712e3880b6]
      /usr/sbin/mariadbd(+0x83d686)[0x55712e13f686]
      /usr/sbin/mariadbd(_Z11plugin_initPiPPci+0x91d)[0x55712e14084d]
      /usr/sbin/mariadbd(+0x70bb91)[0x55712e00db91]
      /usr/sbin/mariadbd(_Z11mysqld_mainiPPc+0x424)[0x55712e013324]
      nptl/libc_start_call_main.h:58(__libc_start_call_main)[0x7feb2b43fd90]
      csu/libc-start.c:128(call_init)[0x7feb2b43fe40]
      /usr/sbin/mariadbd(_start+0x25)[0x55712e007b05]
      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...
      Working directory at /var/lib/mysql
      Resource Limits:
      Limit Soft Limit Hard Limit Units
      Max cpu time unlimited unlimited seconds
      Max file size unlimited unlimited bytes
      Max data size unlimited unlimited bytes
      Max stack size 8388608 unlimited bytes
      Max core file size 0 unlimited bytes
      Max resident set unlimited unlimited bytes
      Max processes 256359 256359 processes
      Max open files 65535 65535 files
      Max locked memory unlimited unlimited bytes
      Max address space unlimited unlimited bytes
      Max file locks unlimited unlimited locks
      Max pending signals 256359 256359 signals
      Max msgqueue size 819200 819200 bytes
      Max nice priority 0 0
      Max realtime priority 0 0
      Max realtime timeout unlimited unlimited us
      Core pattern: |/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g – %E

      Kernel version: Linux version 5.15.0-73-generic (buildd@bos03-amd64-060) (gcc (Ubuntu 11.3.0-1ubuntu1~22.04.1) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38 ) #80-Ubuntu SMP Mon May 15 15:18:26 UTC 2023

      Attachments

        1. data.tar.xz
          3.11 MB
        2. docker-mariadb@debug.service.log.gz
          1.65 MB
        3. gdb_output.log
          12 kB
        4. t_table.sql
          5 kB

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              Erland22 Erlandas
              Votes:
              1 Vote for this issue
              Watchers:
              12 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.