Marko Mäkelä added a comment - 2023-09-07 07:25 Hi! Thank you for the report. The reports of corruption could match MDEV-31767 . Can you check if an upgrade to MariaDB Server 11.0.3 would fix this?

Marko Mäkelä added a comment - 2023-09-07 07:30 The crashes in stderr.txt probably occur somewhere inside InnoDB, during an INSERT operation. Unfortunately, the built-in stack trace report does not correctly resolve InnoDB symbols for some reason. Can you please try to follow the instructions https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ to produce a full stack trace of the crash? danblack should be able to assist you with setting up and using a debug image. We successfully used that to analyze MDEV-32049 . Even though an upgrade to 11.0.3 may make the error go away, I would like to find and fix that crash, because InnoDB is not supposed to crash anymore, no matter what, in the spirit of MDEV-13542 .

Daniel Black added a comment - 2023-09-07 08:19 - edited First, can you build your own image from: Dockerfile FROM mariadb:11.0.2   RUN sed -i -e 's/main/main main\/debug/' /etc/apt/sources.list.d/mariadb.list && \ apt-get update \ && apt-get install -y linux-tools-common gdbserver gdb curl mariadb-server-core-dbgsym=11.0.2 ; \ rm -rf /var/lib/apt/lists/* buildah bud --tag m11.0.2debug . Other dockerfile builders obviously acceptable. podman run --user mysql -v volumename:/var/lib/mysql m11.0.2debug gdb -ex r -ex 'thread apply all bt -frame-arguments all full' --args mariadbd Just translate the podman/docker cmd into how nomad runs things.

Kamil Cukrowski added a comment - 2023-10-04 10:10 As I updated to 11.0.3 and I do not have a way to reproduce, I believe this can be closed to cleanup. Thanks!