Created attachment 1249656 [details]
File: backtrace

Created attachment 1249657 [details]
File: cgroup

Created attachment 1249658 [details]
File: core_backtrace

Created attachment 1249659 [details]
File: dso_list

Created attachment 1249660 [details]
File: environ

Created attachment 1249661 [details]
File: limits

Created attachment 1249662 [details]
File: maps

Created attachment 1249663 [details]
File: mountinfo

Created attachment 1249664 [details]
File: namespaces

Created attachment 1249665 [details]
File: open_fds

Created attachment 1249666 [details]
File: proc_pid_status

Created attachment 1249667 [details]
File: var_log_messages

Similar problem has been detected:

I restarted my computer and after entering my password in the login box, KDE loaded and the first thing that happned was that mariadb and korganizer died. Happens every time. Bloody annoying.

reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/libexec/mysqld --defaults-file=/home/ante/.local/share/akonadi/mysql.conf --datadir=/home/ante/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-ante.biLm8T/mysql.socket
crash_function: fil_load_single_table_tablespace
executable:     /usr/libexec/mysqld
global_pid:     1794
kernel:         4.10.10-200.fc25.x86_64
package:        mariadb-server-10.1.21-3.fc25
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
reason:         mysqld killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

I started my computer and logged into plasma, the first thing that happened was that abrt said mariadb had crashed.

This is what's in the mariadb error log:

2017-06-04 10:13:22 7fd2702368c0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2017-06-04 10:13:22 140541801228480 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-06-04 10:13:22 140541801228480 [Note] InnoDB: The InnoDB memory heap is disabled
2017-06-04 10:13:22 140541801228480 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-06-04 10:13:22 140541801228480 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-06-04 10:13:22 140541801228480 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-06-04 10:13:22 140541801228480 [Note] InnoDB: Using Linux native AIO
2017-06-04 10:13:22 140541801228480 [Note] InnoDB: Using SSE crc32 instructions
2017-06-04 10:13:22 140541801228480 [Note] InnoDB: Initializing buffer pool, size = 80.0M
2017-06-04 10:13:22 140541801228480 [Note] InnoDB: Completed initialization of buffer pool
2017-06-04 10:13:22 140541801228480 [Note] InnoDB: Highest supported file format is Barracuda.
2017-06-04 10:13:22 140541801228480 [Note] InnoDB: The log sequence numbers 29550130 and 29550130 in ibdata files do not match the log sequence number 31062713 in the ib_logfiles!
2017-06-04 10:13:22 140541801228480 [Note] InnoDB: Database was not shutdown normally!
2017-06-04 10:13:22 140541801228480 [Note] InnoDB: Starting crash recovery.
2017-06-04 10:13:22 140541801228480 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-06-04 10:13:22 140541801228480 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace akonadi/pimitemflagrelation uses space ID: 18 at filepath: ./akonadi/pimitemflagrelation.ibd. Cannot open tablespace akonadi/relationtable which uses space ID: 18 at filepath: ./akonadi/relationtable.ibd
2017-06-04 10:13:22 7fd2702368c0  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: Error: could not open single-table tablespace file ./akonadi/relationtable.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
170604 10:13:22 [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.1.21-MariaDB
key_buffer_size=16384
read_buffer_size=131072
max_used_connections=0
max_threads=258
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 566702 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 0x48400
/usr/libexec/mysqld(my_print_stacktrace+0x2e)[0x561a6ee1b1ee]
/usr/libexec/mysqld(handle_fatal_signal+0x3bd)[0x561a6e96423d]
/lib64/libpthread.so.0(+0x115c0)[0x7fd26fece5c0]
/lib64/libc.so.6(gsignal+0x9f)[0x7fd26e30391f]
/lib64/libc.so.6(abort+0x16a)[0x7fd26e30551a]
/usr/libexec/mysqld(+0x9c5078)[0x561a6ed92078]
/usr/libexec/mysqld(+0x86d053)[0x561a6ec3a053]
/usr/libexec/mysqld(+0x8fbcb2)[0x561a6ecc8cb2]
/usr/libexec/mysqld(+0x81fab6)[0x561a6ebecab6]
/usr/libexec/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x66)[0x561a6e966346]
/usr/libexec/mysqld(+0x41db98)[0x561a6e7eab98]
/usr/libexec/mysqld(_Z11plugin_initPiPPci+0x7fa)[0x561a6e7ec1aa]
/usr/libexec/mysqld(+0x377b33)[0x561a6e744b33]
/usr/libexec/mysqld(_Z11mysqld_mainiPPc+0xa5a)[0x561a6e748d6a]
/lib64/libc.so.6(__libc_start_main+0xf1)[0x7fd26e2ee401]
/usr/libexec/mysqld(_start+0x2a)[0x561a6e73c7aa]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
addr2line: Dwarf Error: Offset (2197951744) greater than or equal to .debug_str size (2417909).
addr2line: Dwarf Error: Offset (2063734016) greater than or equal to .debug_str size (2417909).
addr2line: Dwarf Error: Offset (318433542) greater than or equal to .debug_str size (2417909).
addr2line: Dwarf Error: Offset (585210629) greater than or equal to .debug_str size (2417909).
addr2line: Dwarf Error: Offset (598470147) greater than or equal to .debug_str size (2417909).
addr2line: Dwarf Error: Offset (598470147) greater than or equal to .debug_str size (2417909).
addr2line: Dwarf Error: Offset (598470147) greater than or equal to .debug_str size (2417909).
addr2line: Dwarf Error: Offset (598470147) greater than or equal to .debug_str size (2417909).
addr2line: Dwarf Error: Offset (3338797761) greater than or equal to .debug_str size (2417909).
addr2line: Dwarf Error: Offset (405547521) greater than or equal to .debug_str size (2417909).
addr2line: Dwarf Error: Offset (135201055) greater than or equal to .debug_str size (2417909).

reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/libexec/mysqld --defaults-file=/home/ante/.local/share/akonadi/mysql.conf --datadir=/home/ante/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-ante.uhbIXv/mysql.socket
crash_function: fil_load_single_table_tablespace
executable:     /usr/libexec/mysqld
global_pid:     1871
kernel:         4.11.3-200.fc25.x86_64
package:        mariadb-server-10.1.21-3.fc25
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
reason:         mysqld killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

I've got some problems delivering new MariaDB versions, however finally an update is on the way:
https://bodhi.fedoraproject.org/updates/?packages=mariadb

I'd like to know, if the issue persists with the new version.

Similar problem has been detected:

I logged in to plasma, and boom mariadb crashed. Happens every time.

reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/libexec/mysqld --defaults-file=/home/ante/.local/share/akonadi/mysql.conf --datadir=/home/ante/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-ante.rUOrhg/mysql.socket
crash_function: fil_load_single_table_tablespace
executable:     /usr/libexec/mysqld
global_pid:     1786
kernel:         4.11.3-202.fc25.x86_64
package:        mariadb-server-10.1.21-3.fc25
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
reason:         mysqld killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

Solving with MariaDB upstream: https://jira.mariadb.org/browse/MDEV-13284

Is this still a problem, with 10.1.24 or 10.1.25 (in Bodhi) version?

*** Bug 1478267 has been marked as a duplicate of this bug. ***

Now the crash upon boot problems seems to have gone away.

$ rpm -q mariadb
mariadb-10.1.25-1.fc25.x86_64

New version of mariadb in place.

Thanks!

*** Bug 1488730 has been marked as a duplicate of this bug. ***

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.

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)