Bug 1468255

Summary: [abrt] mariadb-server: fil_load_single_table_tablespace(): mysqld killed by SIGABRT
Product: [Fedora] Fedora Reporter: Pupkur
Component: mariadbAssignee: Michal Schorm <mschorm>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: dciabrin, hhorak, jstanek, mbayer, mkocka, mmuzila, mschorm, praiskup, Pupkur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d27f3125bd28431c7972ddd55ab31f8e88c24783
Whiteboard: abrt_hash:9ed744db13f68ecfd0f67716ca21133054e13da2;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-06 14:36:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Pupkur 2017-07-06 13:24:28 UTC
Version-Release number of selected component:
mariadb-server-10.1.24-3.fc25

Additional info:
reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/libexec/mysqld --defaults-file=/home/pupkur/.local/share/akonadi/mysql.conf --datadir=/home/pupkur/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-pupkur.UohNya/mysql.socket
crash_function: fil_load_single_table_tablespace
executable:     /usr/libexec/mysqld
global_pid:     2642
kernel:         4.11.8-200.fc25.x86_64
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #5 fil_load_single_table_tablespace at /usr/src/debug/mariadb-10.1.24/storage/xtradb/fil/fil0fil.cc:5169
 #6 fil_load_single_table_tablespaces at /usr/src/debug/mariadb-10.1.24/storage/xtradb/fil/fil0fil.cc:5518
 #7 recv_init_crash_recovery at /usr/src/debug/mariadb-10.1.24/storage/xtradb/log/log0recv.cc:2999
 #8 recv_recovery_from_checkpoint_start_func at /usr/src/debug/mariadb-10.1.24/storage/xtradb/log/log0recv.cc:3312
 #9 innobase_start_or_create_for_mysql at /usr/src/debug/mariadb-10.1.24/storage/xtradb/srv/srv0start.cc:2575
 #10 innobase_init at /usr/src/debug/mariadb-10.1.24/storage/xtradb/handler/ha_innodb.cc:4440
 #11 ha_initialize_handlerton at /usr/src/debug/mariadb-10.1.24/sql/handler.cc:513
 #12 plugin_initialize at /usr/src/debug/mariadb-10.1.24/sql/sql_plugin.cc:1400
 #13 plugin_init at /usr/src/debug/mariadb-10.1.24/sql/sql_plugin.cc:1677
 #14 init_server_components at /usr/src/debug/mariadb-10.1.24/sql/mysqld.cc:5147

Comment 1 Pupkur 2017-07-06 13:24:36 UTC
Created attachment 1294945 [details]
File: backtrace

Comment 2 Pupkur 2017-07-06 13:24:38 UTC
Created attachment 1294946 [details]
File: cgroup

Comment 3 Pupkur 2017-07-06 13:24:40 UTC
Created attachment 1294947 [details]
File: core_backtrace

Comment 4 Pupkur 2017-07-06 13:24:41 UTC
Created attachment 1294948 [details]
File: dso_list

Comment 5 Pupkur 2017-07-06 13:24:43 UTC
Created attachment 1294949 [details]
File: environ

Comment 6 Pupkur 2017-07-06 13:24:44 UTC
Created attachment 1294950 [details]
File: limits

Comment 7 Pupkur 2017-07-06 13:24:46 UTC
Created attachment 1294951 [details]
File: maps

Comment 8 Pupkur 2017-07-06 13:24:48 UTC
Created attachment 1294952 [details]
File: mountinfo

Comment 9 Pupkur 2017-07-06 13:24:49 UTC
Created attachment 1294953 [details]
File: namespaces

Comment 10 Pupkur 2017-07-06 13:24:51 UTC
Created attachment 1294954 [details]
File: open_fds

Comment 11 Pupkur 2017-07-06 13:24:52 UTC
Created attachment 1294955 [details]
File: proc_pid_status

Comment 12 Pupkur 2017-07-06 13:24:54 UTC
Created attachment 1294956 [details]
File: var_log_messages

Comment 13 Michal Schorm 2017-07-10 13:03:45 UTC
Inspecting the issue with upstream:
https://jira.mariadb.org/browse/MDEV-13284

Comment 14 Michal Schorm 2017-07-10 13:29:38 UTC
Hello,

Can you please remember any operation before this crash, which could be usefull for me?

Most notably some MariaDB update from old version or something.

Comment 15 Pupkur 2017-09-25 14:22:16 UTC
Hello. No I had this crash on system boot and I also install too many updates to remember its.

Comment 16 Fedora End Of Life 2017-11-16 14:58:27 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 17 Michal Schorm 2018-02-06 14:36:34 UTC
Workaround is to use innodb-force-recovery=1

Fixed in MariaDB 10.2 and later. (F27)

Can't be fixed in 10.1 and earlier. (F26)