Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.5.13
-
None
Description
On shutdown mariadb logs "InnoDB: FTS optimize thread exiting." then gets a signal 11 error after 3 minutes.
Seems to be a regression of MDEV-25518, but I'm not sure.
2022-06-21 18:30:26 0 [Note] InnoDB: FTS optimize thread exiting.
|
380621 18:33:46 [ERROR] mysqld got signal 11 ;
|
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.13-MariaDB-log
|
key_buffer_size=26214400
|
read_buffer_size=131072
|
max_used_connections=24
|
max_threads=122
|
thread_count=0
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 75347 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 0x40000
|
/ngfw/usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55f43b80ae6e]
|
/ngfw/usr/sbin/mariadbd(handle_fatal_signal+0x485)[0x55f43b2a1fa5]
|