Description of problem: I recently imported some hundred thousand mails from evolutuin into kontact. Everything worked fine, but now mariadb crashes. Version-Release number of selected component: mariadb-server-5.5.36-1.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/libexec/mysqld --defaults-file=/home/chris/.local/share/akonadi/mysql.conf --datadir=/home/chris/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-chris.arpDWC/mysql.socket crash_function: buf_LRU_get_free_block executable: /usr/libexec/mysqld kernel: 3.13.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 buf_LRU_get_free_block #3 buf_page_init_for_read #4 buf_read_page #5 buf_page_get_gen #6 ibuf_merge_or_delete_for_page #7 buf_page_io_complete #8 buf_read_page #9 buf_page_get_gen #10 btr_cur_search_to_nth_level #11 row_search_on_row_ref
Created attachment 884122 [details] File: backtrace
Created attachment 884123 [details] File: cgroup
Created attachment 884124 [details] File: core_backtrace
Created attachment 884125 [details] File: dso_list
Created attachment 884126 [details] File: limits
Created attachment 884127 [details] File: maps
Created attachment 884128 [details] File: open_fds
Created attachment 884129 [details] File: proc_pid_status
Created attachment 884130 [details] File: var_log_messages
(In reply to Christoph Wickert from comment #0) > Description of problem: > I recently imported some hundred thousand mails from evolutuin into kontact. > Everything worked fine, but now mariadb crashes. Thanks for reporting. MariaDB crashes means that it crashes every-time or it did once? Also it is important if the daemon crashes during start or after some query is proceeded.
It was a one time crash after importing hundreds of thousands of mails into Kontact/akonadi. As I only switch my email program every 5 years or so, I cannot tell you if this crash is reproducible. The crash occurred on starting akonadi. I ended up deleting the imported mail as Kontact became too unresponsive and akonadi just consumed too much resources.
OK, thanks for the reply. I'll keep this bug open for a case we try yet to debug it.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.