[debian-mysql] Bug#1035944: mariadb: upgrade issue: mariadb-server-10.5 fails to restart after upgrading mariadb-common

[Otto Kekäläinen]

After some experimentation I found out that updating libkrb5-3 so that
/usr/lib/x86_64-linux-gnu/libkrb5.so.3 upgrades will stop MariaDB from
crashing.

$ apt install libk5crypto3 libkrb5-3
...
libssl3 amd64 3.0.8-1
libgssapi-krb5-2 amd64 1.20.1-1+b1
libkrb5support0 amd64 1.20.1-1+b1
libkrb5-3 amd64 1.20.1-1+b1

I made a quick bash one-liner to install all packages from 'apt
upgrade' step one-by-one to find out which one exactly causes MariaDB
to crash, and the result was also libk5crypto3.

Here is a more complete stack trace with debug symbols installed and
addr2line working:


230514  5:19:28 [ERROR] mysqld got signal 11 ;
Server version: 10.5.19-MariaDB-0+deb11u2 source revision:
f8a85af8ca1c937b8d4f847477bd282f80251cde
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 =
467880 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
2023-05-14  5:19:28 0 [Note] InnoDB: Buffer pool(s) load completed at
230514  5:19:28
??:0(my_print_stacktrace)[0x556f175e616e]
??:0(handle_fatal_signal)[0x556f170def45]
libc_sigaction.c:0(__restore_rt)[0x7f443ea8cf90]
krb/prng.c:151(krb5_c_random_os_entropy)[0x7f443cd95de0]
??:0(krb5_init_context_profile)[0x7f443ce06cbf]
??:0(plugin_init())[0x7f443cee7569]
/usr/lib/mysql/plugin/auth_gssapi.so(+0x2330)[0x7f443cee7330]
??:0(sys_var_pluginvar::sys_var_pluginvar(sys_var_chain*, char const*,
st_plugin_int*, st_mysql_sys_var*, char const*))[0x556f16ef3562]
??:0(plugin_init(int*, char**, int))[0x556f16ef44d7]
??:0(unireg_abort)[0x556f16e1c0e6]
??:0(mysqld_main(int, char**))[0x556f16e21dc4]
x86/libc-start.c:74(__libc_start_call_main)[0x7f443ea7818a]
csu/libc-start.c:128(call_init)[0x7f443ea78245]
??:0(_start)[0x556f16e16daa]


I think the solution would be for libk5crypto3 to have instead of

Depends: libc6 (>= 2.33), libkrb5support0 (>= 1.16)

to have

Depends: libc6 (>= 2.33), libkrb5support0 (>= 1.20)