Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: crash Version-Release number of selected component: mariadb-server-3:11.8.8-1.fc45 Additional info: reporter: libreport-2.17.15 type: CCpp reason: mariadbd killed by SIGABRT journald_cursor: s=8bf3348a8308430692a9b94bd1599c24;i=142f76;b=33867a861f1245baa3b7cec118a91026;m=1192c2a7;t=655900a6175c3;x=7a9930e34467d4cf executable: /usr/libexec/mariadbd cmdline: /usr/libexec/mysqld --defaults-file=/home/larsmartinhambro/.local/share/akonadi/mysql.conf --datadir=/home/larsmartinhambro/.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.0-0.rc7.260611g9716c086c8e8.50.fc45.x86_64 package: mariadb-server-3:11.8.8-1.fc45 runlevel: /bin/sh: linje 1: runlevel: command not found backtrace_rating: 4 crash_function: handle_fatal_signal comment: crash Truncated backtrace: Thread no. 1 (15 frames) #1 handle_fatal_signal at /usr/src/debug/mariadb11.8-11.8.8-1.fc45.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 inline_mysql_cond_wait at /usr/src/debug/mariadb11.8-11.8.8-1.fc45.x86_64/include/mysql/psi/mysql_thread.h:1072 #11 start_slave_deadlock_handler_thread at /usr/src/debug/mariadb11.8-11.8.8-1.fc45.x86_64/sql/slave.cc:568 #12 init_slave at /usr/src/debug/mariadb11.8-11.8.8-1.fc45.x86_64/sql/slave.cc:672 #13 mysqld_main at /usr/src/debug/mariadb11.8-11.8.8-1.fc45.x86_64/sql/mysqld.cc:6186 #14 __libc_start_call_main at ../sysdeps/nptl/libc_start_call_main.h:59 #15 __libc_start_main_impl at ../csu/libc-start.c:366 #16 _start Potential duplicate: bug 2461899
Created attachment 2147325 [details] File: proc_pid_status
Created attachment 2147326 [details] File: maps
Created attachment 2147327 [details] File: limits
Created attachment 2147328 [details] File: environ
Created attachment 2147329 [details] File: open_fds
Created attachment 2147330 [details] File: mountinfo
Created attachment 2147331 [details] File: os_info
Created attachment 2147332 [details] File: cpuinfo
Created attachment 2147333 [details] File: core_backtrace
Created attachment 2147334 [details] File: dso_list
Created attachment 2147335 [details] File: backtrace
Hello, thank you for the report. I reported the observation to the MariaDB upstream. https://mariadb.zulipchat.com/#narrow/channel/118759-general/topic/.5BFedora.5D.20Akonadi.20.2B.20MariaDB.2011.2E8.20crash/with/608748523
So far, examination has shown that the SIGABRT was from an external process doing kill -SIGABRT {mariadbd.pid}. To help see why this is the case can we obtain the logs from akonadi - below is an assumption: journalctl --user -u akonadi_control.service and the mariadb logs: $HOME/.local/share/akonadi/db_data/mysql.err or perhaps $HOME/.local/share/akonadi/db_data/mysql.err.old if it was a previous session.