MariaDB 10.5.8 from glibc-2.30 to glibc-2.32 crash?
by cgw from LinuxQuestions.org on (#5DJDV)
I upgraded to slackware-current 2021-01-30 and (non-kernel updates from) 2021-01-31 and have been unable to start MariaDB since 2021-01-30. Specifically, I was at mariadb-10.5.8-i586-1 and failed with mariadb-10.5.8-i586-2, which was described as a recompile against glibc-2.32. I have built with mariadb.SlackBuild on my system and still get the same error, which I have posted to jira.mariadb.org.
Here is the .err:
Slackware-current:
Linux [cut] 5.10.11-smp #1 SMP Wed Jan 27 13:11:41 CST 2021 i686 Intel(R) Xeon(TM) CPU 2.80GHz GenuineIntel GNU/Linux


Here is the .err:
2021-01-31 14:15:37 0 [Note] InnoDB: Using Linux native AIOEverything else on this system seems to work. Anybody else have trouble or insight?
2021-01-31 14:15:37 0 [Note] InnoDB: Uses event mutexes
2021-01-31 14:15:37 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-01-31 14:15:37 0 [Note] InnoDB: Number of pools: 1
2021-01-31 14:15:37 0 [Note] InnoDB: Using generic crc32 instructions
2021-01-31 14:15:37 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
2021-01-31 14:15:37 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2021-01-31 14:15:37 0 [Note] InnoDB: Completed initialization of buffer pool
2021-01-31 14:15:37 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
210131 14:15:37 [ERROR] mysqld got signal 4 ;
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.5.8-MariaDB-log
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 = 466473 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(my_print_stacktrace)[0x12db9ae]
??:0(handle_fatal_signal)[0xc40992]
addr2line: 'linux-gate.so.1': No such file
linux-gate.so.1(__kernel_sigreturn+0x0)[0xb7f82554]
??:0(my_dlerror)[0x12f6250]
??:0(std::unique_lock<std::mutex>::unlock())[0x118ae9c]
??:0(std::unique_lock<std::mutex>::unlock())[0x118047f]
??:0(std::unique_lock<std::mutex>::unlock())[0x1202753]
??:0(std::unique_lock<std::mutex>::unlock())[0x1206618]
??:0(std::unique_lock<std::mutex>::unlock())[0x1206c17]
??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x862f98]
??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0xfefbdc]
??:0(ha_initialize_handlerton(st_plugin_int*))[0xc43b2d]
??:0(sys_var_pluginvar::sys_var_pluginvar(sys_var_chain*, char const*, st_plugin_int*, st_mysql_sys_var*))[0x9e70cc]
??:0(plugin_init(int*, char**, int))[0x9e87da]
??:0(unireg_abort)[0x8e456c]
??:0(mysqld_main(int, char**))[0x8eab35]
??:0(main)[0x8a7467]
??:0(__libc_start_main)[0xb75ff05a]
??:0(_start)[0x8dd811]
The manual page at https://mariadb.com/kb/en/how-to-pro...ce-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 15973 15973 processes
Max open files 32186 32186 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 15973 15973 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
Slackware-current:
Linux [cut] 5.10.11-smp #1 SMP Wed Jan 27 13:11:41 CST 2021 i686 Intel(R) Xeon(TM) CPU 2.80GHz GenuineIntel GNU/Linux