2023-07-07  9:27:36 0 [Note] Starting MariaDB 10.11.3-MariaDB-1 source revision  as process 86804
2023-07-07  9:27:36 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2023-07-07  9:27:36 0 [Note] InnoDB: Using transactional memory
2023-07-07  9:27:36 0 [Note] InnoDB: Number of transaction pools: 1
2023-07-07  9:27:36 0 [Note] InnoDB: Using generic crc32 instructions
2023-07-07  9:27:36 0 [Note] InnoDB: Using liburing
2023-07-07  9:27:36 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2023-07-07  9:27:36 0 [Note] InnoDB: Completed initialization of buffer pool
2023-07-07  9:27:36 0 [Note] InnoDB: File system buffers for log disabled (block size=4096 bytes)
2023-07-07  9:27:36 0 [Warning] InnoDB: Retry attempts for reading partial data failed.
2023-07-07 09:27:36 0x3ff8016c820  InnoDB: Assertion failure in file ./storage/innobase/log/log0recv.cc line 1190
InnoDB: Failing assertion: err == DB_SUCCESS
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 mariadbd 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.
230707  9:27:36 [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.11.3-MariaDB-1 source revision:
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 = 468022 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/mariadbd(my_print_stacktrace+0x36)[0x2aa2be93076]
/usr/sbin/mariadbd(handle_fatal_signal+0x58a)[0x2aa2b9a34aa]
[0x3ffdfafa356]
/lib/s390x-linux-gnu/libc.so.6(+0x9861a)[0x3ff7f29861a]
/lib/s390x-linux-gnu/libc.so.6(gsignal+0x20)[0x3ff7f248758]
/lib/s390x-linux-gnu/libc.so.6(abort+0x10c)[0x3ff7f22b5a4]
/usr/sbin/mariadbd(+0x67d116)[0x2aa2b5fd116]
/usr/sbin/mariadbd(+0xd40ac0)[0x2aa2bcc0ac0]
/usr/sbin/mariadbd(+0xd4190e)[0x2aa2bcc190e]
/usr/sbin/mariadbd(+0xdd1622)[0x2aa2bd51622]
/usr/sbin/mariadbd(+0xcfd1be)[0x2aa2bc7d1be]
/usr/sbin/mariadbd(_Z24ha_initialize_handlertonP13st_plugin_int+0x78)[0x2aa2b9a6b08]
/usr/sbin/mariadbd(+0x7e7ae0)[0x2aa2b767ae0]
/usr/sbin/mariadbd(_Z11plugin_initPiPPci+0x978)[0x2aa2b768c08]
/usr/sbin/mariadbd(+0x6cd490)[0x2aa2b64d490]
/usr/sbin/mariadbd(_Z11mysqld_mainiPPc+0x48c)[0x2aa2b65346c]
/lib/s390x-linux-gnu/libc.so.6(+0x2b84a)[0x3ff7f22b84a]
/lib/s390x-linux-gnu/libc.so.6(__libc_start_main+0xa2)[0x3ff7f22b932]
/usr/sbin/mariadbd(+0x6c7b48)[0x2aa2b647b48]
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        0                    unlimited            bytes
Max resident set          unlimited            unlimited            bytes
Max processes             15885                15885                processes
Max open files            32183                32183                files
Max locked memory         524455936            524455936            bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       15885                15885                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

Kernel version: Linux version 5.10.0-23-s390x (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.179-1 (2023-05-12)

Aborted