Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: start up this services crash Version-Release number of selected component: mariadb-server-3:11.8.6-2.fc44 Additional info: reporter: libreport-2.17.15 type: CCpp reason: mariadbd killed by SIGABRT journald_cursor: s=16eee3e8bdad4b6291f7c9291626aa71;i=46e1;b=9daf45dbae52462c96891cb1af057454;m=1001dc52;t=650580822b3b8;x=d01ed302b0583ab3 executable: /usr/libexec/mariadbd cmdline: /usr/bin/mysqld --defaults-file=/home/e/.local/share/akonadi/mysql.conf --datadir=/home/e/.local/share/akonadi/db_data/ --socket=/run/user/1000/akonadi/mysql.socket --pid-file=/run/user/1000/akonadi/mysql.pid cgroup: 0::/user.slice/user-1000.slice/user/background.slice/akonadi_control.service rootdir: / uid: 1000 kernel: 6.19.14-300.fc44.x86_64 package: mariadb-server-3:11.8.6-2.fc44 runlevel: /bin/sh: line 1: runlevel: command not found comment: start up this services crash backtrace_rating: 4 crash_function: handle_fatal_signal Truncated backtrace: Thread no. 1 (14 frames) #1 handle_fatal_signal at /usr/src/debug/mariadb11.8-11.8.6-2.fc44.x86_64/sql/signal_handler.cc:310 #3 __syscall_cancel_arch at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56 #4 __internal_syscall_cancel at cancellation.c:49 #5 __futex_abstimed_wait_common64 at futex-internal.c:57 #6 __futex_abstimed_wait_common at futex-internal.c:87 #7 __futex_abstimed_wait_cancelable64 at futex-internal.c:139 #8 __pthread_cond_wait_common at pthread_cond_wait.c:421 #9 ___pthread_cond_wait at pthread_cond_wait.c:453 #10 __gthread_cond_wait at /usr/src/debug/gcc-16.0.1-0.10.fc44.x86_64/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/x86_64-redhat-linux/bits/gthr-default.h:911 #11 std::__condvar::wait at /usr/src/debug/gcc-16.0.1-0.10.fc44.x86_64/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/bits/std_mutex.h:174 #12 std::condition_variable::wait at ../../../../../libstdc++-v3/src/c++11/condition_variable.cc:41 #13 tpool::cache<tpool::aiocb, true>::wait at /usr/src/debug/mariadb11.8-11.8.6-2.fc44.x86_64/tpool/tpool_structs.h:188 #15 io_slots::wait at /usr/src/debug/mariadb11.8-11.8.6-2.fc44.x86_64/storage/innobase/os/os0file.cc:111 #16 os_aio_wait_until_no_pending_writes_low at /usr/src/debug/mariadb11.8-11.8.6-2.fc44.x86_64/storage/innobase/os/os0file.cc:3187
Created attachment 2138288 [details] File: proc_pid_status
Created attachment 2138289 [details] File: maps
Created attachment 2138290 [details] File: limits
Created attachment 2138291 [details] File: environ
Created attachment 2138292 [details] File: open_fds
Created attachment 2138293 [details] File: mountinfo
Created attachment 2138294 [details] File: os_info
Created attachment 2138295 [details] File: cpuinfo
Created attachment 2138296 [details] File: core_backtrace
Created attachment 2138297 [details] File: dso_list
Created attachment 2138298 [details] File: backtrace
Hi, I did not manage to reproduce the crash, could you please provide the contents of /home/e/.local/share/akonadi/mysql.conf ? Might be that you have a specific flag set that I do not and it is causing the crash.
after installation of Fedora 44, first time boot....
System was rebooted after a kernel update (7.0.9-204) and then I logged in to a GNOME desktop. Crash notification came up as the desktop was opening. reporter: libreport-2.17.15 type: CCpp reason: mariadbd killed by SIGABRT journald_cursor: s=60c0585bc36d45fcbf087f0a1cf151bf;i=16430058;b=d325ae62d69e43daa06ba382bf7ed900;m=3a63d4f;t=6523fb00380e4;x=27d234a395d054 executable: /usr/libexec/mariadbd cmdline: /usr/libexec/mysqld --defaults-file=/home/bdm/.local/share/akonadi/mysql.conf --datadir=/home/bdm/.local/share/akonadi/db_data/ --socket=/run/user/1000/akonadi/mysql.socket --pid-file=/run/user/1000/akonadi/mysql.pid cgroup: 0::/user.slice/user-1000.slice/user/background.slice/akonadi_control.service rootdir: / uid: 1000 kernel: 7.0.9-204.fc44.x86_64 package: mariadb-server-3:11.8.6-2.fc44 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: handle_fatal_signal
Mariadb crashed shortly after booting my laptop (USB boot). The only thing that I did was logging in, I didn't touch it afterwards until mariadb crashed. This is not the first mariadb crash that I have seen, the log says 2 times 15 days ago and another 3 times one month ago.
Updated to fedora 44, restarted and logged in. Problem occurred upon log-in and start of desktop. reporter: libreport-2.17.15 type: CCpp reason: mariadbd killed by SIGABRT journald_cursor: s=6a830a4d2bda45b7a58c57e804d880da;i=30bde;b=9a441aaecc2a42569bbe56fd00f580e0;m=339fea6b;t=653c8611d5333;x=dae18e14156a3ee6 executable: /usr/libexec/mariadbd cmdline: /usr/libexec/mysqld --defaults-file=/home/christopher/.local/share/akonadi/mysql.conf --datadir=/home/christopher/.local/share/akonadi/db_data/ --socket=/run/user/1000/akonadi/mysql.socket --pid-file=/run/user/1000/akonadi/mysql.pid cgroup: 0::/user.slice/user-1000.slice/user/background.slice/akonadi_control.service rootdir: / uid: 1000 kernel: 7.0.11-200.fc44.x86_64 package: mariadb-server-3:11.8.6-2.fc44 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: handle_fatal_signal comment: Updated to fedora 44, restarted and logged in. Problem occurred upon log-in and start of desktop.
Occurred during login to GNOME desktop, immediately the desktop appeared. reporter: libreport-2.17.15 type: CCpp reason: mariadbd killed by SIGABRT journald_cursor: s=60c0585bc36d45fcbf087f0a1cf151bf;i=1b5db194;b=c7d5cf73766e484a94d7f17e2a99ecdf;m=35b5f5f;t=655b9a91c609e;x=9d6aa2b1d2d93b7c executable: /usr/libexec/mariadbd cmdline: /usr/libexec/mysqld --defaults-file=/home/bdm/.local/share/akonadi/mysql.conf --datadir=/home/bdm/.local/share/akonadi/db_data/ --socket=/run/user/1000/akonadi/mysql.socket --pid-file=/run/user/1000/akonadi/mysql.pid cgroup: 0::/user.slice/user-1000.slice/user/background.slice/akonadi_control.service rootdir: / uid: 1000 kernel: 7.1.2-201.fc44.x86_64 package: mariadb-server-3:11.8.8-3.fc44 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: handle_fatal_signal comment: Occurred during login to GNOME desktop, immediately the desktop appeared.
Hello, thank you for the reports. I reported the issue to the MariaDB upstream as: https://jira.mariadb.org/browse/MDEV-40293
softwareupdate, reboot, crash reporter: libreport-2.17.15 type: CCpp reason: mariadbd killed by SIGABRT journald_cursor: s=0aa2217e59f54fbeb3a60901af23561e;i=a11a;b=2ea9a651743b48428e2ac1873f424319;m=aa03621;t=65633e6576561;x=8f8f4a92b40f521a executable: /usr/libexec/mariadbd cmdline: /usr/bin/mysqld --defaults-file=/home/andreas/.local/share/akonadi/mysql.conf --datadir=/home/andreas/.local/share/akonadi/db_data/ --socket=/run/user/1000/akonadi/mysql.socket --pid-file=/run/user/1000/akonadi/mysql.pid cgroup: 0::/user.slice/user-1000.slice/user/background.slice/akonadi_control.service rootdir: / uid: 1000 kernel: 7.1.3-200.fc44.x86_64 package: mariadb-server-3:11.8.8-3.fc44 runlevel: /bin/sh: Zeile 1: runlevel: Kommando nicht gefunden comment: softwareupdate, reboot, crash backtrace_rating: 4 crash_function: handle_fatal_signal