Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.2.36, 10.3.29
-
None
-
KVM machine with ubuntu bionic cloud image. Dockerised deployment of mariadb 10.3.29 from mariadb repository based on ubuntu bionic docker image:
$ uname -a
Linux os-ctrl-1 4.15.0-109-generic #110-Ubuntu SMP Tue Jun 23 02:39:32 UTC 2020 x8
$ docker exec -it mariadb mysql --version
mysql Ver 15.1 Distrib 10.3.29-MariaDB, for debian-linux-gnu (x86_64) using readline 5.26_64 x86_64 x86_64 GNU/Linux
KVM machine with ubuntu bionic cloud image. Dockerised deployment of mariadb 10.3.29 from mariadb repository based on ubuntu bionic docker image: $ uname -a Linux os-ctrl-1 4.15.0-109-generic #110-Ubuntu SMP Tue Jun 23 02:39:32 UTC 2020 x8 $ docker exec -it mariadb mysql --version mysql Ver 15.1 Distrib 10.3.29-MariaDB, for debian-linux-gnu (x86_64) using readline 5.26_64 x86_64 x86_64 GNU/Linux
Description
Starting with mariadb 10.3.29 when deploying a three node galera cluster, we are seeing crashes with errors like in [1].
Please find attached the log files from all three nodes and their configurations. A core dump of the crash in [1] can also be provided.
[1]
2021-06-01 9:06:16 0 [ERROR] WSREP: Trx 236236 tries to abort slave trx 236238. This could be caused by:
|
1) unsupported configuration options combination, please check documentation.
|
2) a bug in the code.
|
3) a database corruption.
|
Node consistency compromized, need to abort. Restart the node to resync with cluster.
|
210601 9:06:16 [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: 10.3.29-MariaDB-1:10.3.29+maria~bionic-log
|
key_buffer_size=67108864
|
read_buffer_size=131072
|
max_used_connections=1
|
max_threads=10002
|
thread_count=12
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 22055535 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
|
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x5647d689bb8e]
|
/usr/sbin/mysqld(handle_fatal_signal+0x515)[0x5647d63308c5]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12980)[0x7fd6316ed980]
|
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fd631328fb7]
|
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fd63132a921]
|
/usr/sbin/mysqld(+0x90a914)[0x5647d64ba914]
|
/usr/sbin/mysqld(+0x90f83c)[0x5647d64bf83c]
|
/usr/sbin/mysqld(handle_manager+0x1f3)[0x5647d6142a83]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76db)[0x7fd6316e26db]
|
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7fd63140b71f]
|
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.
|
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 unlimited unlimited bytes
|
Max resident set unlimited unlimited bytes
|
Max processes unlimited unlimited processes
|
Max open files 1048576 1048576 files
|
Max locked memory 16777216 16777216 bytes
|
Max address space unlimited unlimited bytes
|
Max file locks unlimited unlimited locks
|
Max pending signals 64055 64055 signals
|
Max msgqueue size 819200 819200 bytes
|
Max nice priority 0 0
|
Max realtime priority 0 0
|
Max realtime timeout unlimited unlimited us
|
Core pattern: core
|
Attachments
Issue Links
- is duplicated by
-
MDEV-26697 MariaDB keeps rebooting after upgrade from 10.3.23 to 10.3.31
- Closed
- relates to
-
MDEV-24978 SIGABRT in __libc_message
- Closed