Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.5.8/storage/innobase/log/log0log.cc line 631

We have a 3 Node MariaDB-Galera cluster environment. We have set our Load Balancer to have connections going to one node at a time. The other were set for High Availability. On the node where connections are going MariaDB has stopped responding suddenly. MariaDB service status shows as it is running but we could not login to the MySQL. Each login attempt was thrown out.

This node could not communicate with other nodes.

Our environment details:
$ hostnamectl
Static hostname: xxxxxxxxxxxxxxxxxxx
Icon name: computer-vm
Chassis: vm
Machine ID: xxxxxxxxxxxxxxxxxxx
Boot ID: xxxxxxxxxxxxxxxxxxx
Virtualization: vmware
Operating System: CentOS Linux 7 (Core)
CPE OS Name: cpe:/o:centos:centos:7
Kernel: Linux 3.10.0-1160.80.1.el7.x86_64
Architecture: x86-64

$ rpm -qa | grep -i mariadb
MariaDB-common-10.5.8-1.el7.centos.x86_64
MariaDB-client-10.5.8-1.el7.centos.x86_64
MariaDB-server-10.5.8-1.el7.centos.x86_64
MariaDB-compat-10.5.8-1.el7.centos.x86_64

$ rpm -qa | grep -i galera
galera-4-26.4.6-1.el7.centos.x86_64

Following was found in mysqld.log file:

2022-12-22 11:07:33 0x7f93337fe700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.5.8/storage/innobase/log/log0log.cc line 631
InnoDB: Failing assertion: lsn >= log_sys.get_flushed_lsn()
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
221222 11:07:33 [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.5.8-MariaDB-log
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=329
max_threads=10002
thread_count=340
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 22149199 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
Can't start addr2line
/usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55801be2c37e]
/usr/sbin/mariadbd(handle_fatal_signal+0x307)[0x55801b83afe7]
/lib64/libpthread.so.0(+0xf630)[0x7f97872e4630]
/lib64/libc.so.6(gsignal+0x37)[0x7f978533d387]
/lib64/libc.so.6(abort+0x148)[0x7f978533ea78]
/usr/sbin/mariadbd(+0x64b6e9)[0x55801b5166e9]
/usr/sbin/mariadbd(+0xcad23c)[0x55801bb7823c]
/usr/sbin/mariadbd(+0xd64f1c)[0x55801bc2ff1c]
/usr/sbin/mariadbd(_ZN5tpool19thread_pool_generic13timer_generic7executeEPv+0x35)[0x55801bdb4e95]
/usr/sbin/mariadbd(_ZN5tpool4task7executeEv+0x2b)[0x55801bdb5fcb]
/usr/sbin/mariadbd(_ZN5tpool19thread_pool_generic11worker_mainEPNS_11worker_dataE+0x61)[0x55801bdb4441]
/lib64/libstdc++.so.6(+0xb5330)[0x7f9785a8c330]
/lib64/libpthread.so.0(+0x7ea5)[0x7f97872dcea5]
/lib64/libc.so.6(clone+0x6d)[0x7f9785405b0d]
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 /apps/mariadb/data
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 95625 95625 processes
Max open files 16384 16384 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 95625 95625 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