[MDEV-30439]  mysqld got signal 11 after SST/IST Created: 2023-01-20  Updated: 2023-01-20

Status: Open
Project: MariaDB Server
Component/s: Galera SST
Affects Version/s: 10.8.6
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Brendan Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Environment:

Linux mdb-host-3 4.18.0-348.2.1.el8_5.x86_64 #1 SMP Mon Nov 8 13:30:15 EST 2021 x86_64 x86_64 x86_64 GNU/Linux



 Description   

We have a three node galera cluster running 10.8.6. We had two nodes fill up their disks and had to redo the cluster and now we can't get the two nodes to join the cluster again. (node 1 was set up as the bootstrap node)

We have 1 node running, but when we try to start either of the other nodes, we receive an error:

Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: 230120 17:37:01 [ERROR] mysqld got signal 11 ;
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: This could be because you hit a bug. It is also possible that this binary
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: or one of the libraries it was linked against is corrupt, improperly built,
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: or misconfigured. This error can also be caused by malfunctioning hardware.
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: We will try our best to scrape up some info that will hopefully help
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: diagnose the problem, but since we have already crashed,
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: something is definitely wrong and this may fail.
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: Server version: 10.6.8-MariaDB-log
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: key_buffer_size=134217728
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: read_buffer_size=131072
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: max_used_connections=3
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: max_threads=602
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: thread_count=6
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: It is possible that mysqld could use up to
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1456678 K  bytes of memory
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: Hope that's ok; if not, decrease some variables in the equation.
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: Thread pointer: 0x7fdf0c000c58
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: Attempting backtrace. You can use the following information to find out
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: where mysqld died. If you see no messages after this, something went
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: terribly wrong...
Jan 20 17:37:01 mdb-host-3 mariadbd[4458]: stack_bottom = 0x7fdfa876cc48 thread_stack 0x49000
Jan 20 17:37:02 mdb-host-3 mariadbd[4458]: /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x56040578911e]
Jan 20 17:37:03 mdb-host-3 mariadbd[4458]: /usr/sbin/mariadbd(handle_fatal_signal+0x485)[0x560405267745]

The odd thing we've noticed is that the SST finishes, and the cluster says it is ready and accepting connections, but if you try to perform any query, it seems to hang.


Generated at Thu Feb 08 10:16:16 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.