Mariadb fails to start following automatic upgrade to 11.0.2 - Unable to find charset-collation for 271

230629 12:03:58 mysqld_safe Starting mariadbd daemon with databases from /usr/local/var/mysql

2023-06-29 12:03:58 0 [Warning] Setting lower_case_table_names=2 because file system for /usr/local/var/mysql/ is case insensitive

2023-06-29 12:03:58 0 [Note] Starting MariaDB 11.0.2-MariaDB source revision 0005f2f06c8e1aea4915887decad67885108a929 as process 76835

2023-06-29 12:03:58 0 [Note] InnoDB: Compressed tables use zlib 1.2.11

2023-06-29 12:03:58 0 [Note] InnoDB: Number of transaction pools: 1

2023-06-29 12:03:58 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions

2023-06-29 12:03:58 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB

2023-06-29 12:03:58 0 [Note] InnoDB: Completed initialization of buffer pool

2023-06-29 12:03:58 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=32612426383

2023-06-29 12:03:58 0 [Note] InnoDB: Starting final batch to recover 127 pages from redo log.

2023-06-29 12:03:58 0 [Note] InnoDB: Upgrading the change buffer

2023-06-29 12:03:58 0 [ERROR] [FATAL] InnoDB: Unable to find charset-collation for 271

230629 12:03:58 [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 source revision: 0005f2f06c8e1aea4915887decad67885108a929

key_buffer_size=134217728

read_buffer_size=131072

max_used_connections=0

max_threads=153

thread_count=0

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 468026 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

0   mariadbd                            0x00000001102bde02 my_print_stacktrace + 60

Printing to addr2line failed

0   mariadbd                            0x000000010fc94c85 handle_fatal_signal + 717

0   libsystem_platform.dylib            0x00007ff81e93ddfd _sigtramp + 29

0   ???                                 0x0000000000000080 0x0 + 128

0   libsystem_c.dylib                   0x00007ff81e873d24 abort + 123

0   mariadbd                            0x000000011026c2f3 _ZN2ib5fatalD2Ev + 77

0   mariadbd                            0x000000011026c327 _ZN2ib5fatalD1Ev + 9

0   mariadbd                            0x00000001101fe022 _Z8cmp_datammbPKhmS0_m + 953

0   mariadbd                            0x00000001101fe164 _Z29cmp_dtuple_rec_with_match_lowPK8dtuple_tPKhPK12dict_index_tPKtmPm + 257

0   mariadbd                            0x00000001101e31e8 _Z26page_cur_search_with_matchPK8dtuple_t15page_cur_mode_tPmS3_P10page_cur_tP8rtr_info + 472

0   mariadbd                            0x0000000110356db3 _ZL10ibuf_mergeP11fil_space_tP9btr_cur_tP5mtr_t + 2042

0   mariadbd                            0x000000011035626e _Z12ibuf_upgradev + 1022

0   mariadbd                            0x000000011024d1b0 _Z9srv_startb + 6805

0   mariadbd                            0x000000011019849f _ZL11innodb_initPv + 2338

0   mariadbd                            0x000000010fc959b7 _Z24ha_initialize_handlertonP13st_plugin_int + 122

0   mariadbd                            0x000000010fe78c65 _ZL17plugin_initializeP11st_mem_rootP13st_plugin_intPiPPcb + 211

0   mariadbd                            0x000000010fe784a6 _Z11plugin_initPiPPci + 2462

0   mariadbd                            0x000000010fd86a0f _ZL22init_server_componentsv + 1554

0   mariadbd                            0x000000010fd82f09 _Z11mysqld_mainiPPc + 1245

0   dyld                                0x0000000112cd252e start + 462

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.

Core pattern: /cores/core.%P

230629 12:03:58 mysqld_safe mysqld from pid file /usr/local/var/mysql/Peters-MacBook-Pro-2.local.pid ended