Bug 1085445

Summary: [abrt] mariadb-server: buf_LRU_get_free_block(): mysqld killed by SIGABRT
Product: [Fedora] Fedora Reporter: Christoph Wickert <christoph.wickert>
Component: mariadbAssignee: Honza Horak <hhorak>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: christoph.wickert, hhorak, jdornak
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2819da35d88dd11941af659afe809214500f1a3b
Whiteboard: abrt_hash:274bdd8e66fd3cb2c91706d8dbf337d4455029d1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 19:58:53 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Christoph Wickert 2014-04-08 15:45:12 UTC 
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
Comment 1 Christoph Wickert 2014-04-08 15:45:24 UTC 
Created attachment 884122 [details]
File: backtrace
Comment 2 Christoph Wickert 2014-04-08 15:45:27 UTC 
Created attachment 884123 [details]
File: cgroup
Comment 3 Christoph Wickert 2014-04-08 15:45:31 UTC 
Created attachment 884124 [details]
File: core_backtrace
Comment 4 Christoph Wickert 2014-04-08 15:45:34 UTC 
Created attachment 884125 [details]
File: dso_list
Comment 5 Christoph Wickert 2014-04-08 15:45:37 UTC 
Created attachment 884126 [details]
File: limits
Comment 6 Christoph Wickert 2014-04-08 15:45:40 UTC 
Created attachment 884127 [details]
File: maps
Comment 7 Christoph Wickert 2014-04-08 15:45:45 UTC 
Created attachment 884128 [details]
File: open_fds
Comment 8 Christoph Wickert 2014-04-08 15:45:48 UTC 
Created attachment 884129 [details]
File: proc_pid_status
Comment 9 Christoph Wickert 2014-04-08 15:45:51 UTC 
Created attachment 884130 [details]
File: var_log_messages
Comment 10 Honza Horak 2014-04-09 14:52:36 UTC 
(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.
Comment 11 Christoph Wickert 2014-06-11 09:20:36 UTC 
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.
Comment 12 Honza Horak 2014-06-11 11:14:33 UTC 
OK, thanks for the reply. I'll keep this bug open for a case we try yet to debug it.
Comment 13 Fedora End Of Life 2015-05-29 11:30:35 UTC 
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.
Comment 14 Fedora End Of Life 2015-06-29 19:58:53 UTC 
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.