mysql crash

Bug #1366757 reported by Ilya
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
New
Undecided
Unassigned

Bug Description

Mysql server version: 5.5.37-35.1-log Percona Server (GPL), Release 35.1, Revision 666
Os: Ubuntu 14.04 LTS

Mysql crashed and I found this in log.

10:14:58 UTC - mysqld got signal 11 ;
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.
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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=2097152000
read_buffer_size=131072
max_used_connections=166
max_threads=232
thread_count=7
connection_count=7
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2555703 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 = 0 thread_stack 0x30000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x35)[0x7fa6d5]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x3f4)[0x6aea44]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f297a4ff340]
/usr/local/mysql/bin/mysqld[0x8f1a0b]
/usr/local/mysql/bin/mysqld[0x8f1b1f]
/usr/local/mysql/bin/mysqld[0x89327f]
/usr/local/mysql/bin/mysqld[0x877b48]
/usr/local/mysql/bin/mysqld[0x879d1a]
/usr/local/mysql/bin/mysqld[0x880cd8]
/usr/local/mysql/bin/mysqld[0x8820a1]
/usr/local/mysql/bin/mysqld[0x88c870]
/usr/local/mysql/bin/mysqld[0x9481d0]
/usr/local/mysql/bin/mysqld[0x948e26]
/usr/local/mysql/bin/mysqld[0x93d53c]
/usr/local/mysql/bin/mysqld[0x859924]
/usr/local/mysql/bin/mysqld[0x84c9ae]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f297a4f7182]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f2978d9b30d]
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.

Hope this can make mysql better. Any information will be sent if needed.

Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :

Please, check if you can reproduce the crash with a recent version, 5.5.39. if you do, please, send your my.cnf file content and try to note crashing statement.

In any case we need a resolved stack trace. You can try to resolve it as explained in the manual, http://dev.mysql.com/doc/refman/5.5/en/resolve-stack-dump.html:

cat <<EOT >/tmp/mysqld.stack
<numeric addresses from your stack trace here>
EOT

nm -n `which mysqld` > /tmp/mysqld.symbols

resolve_stack_dump -s /tmp/mysqld.symbols -n /tmp/mysqld.stack | c++filt

Changed in percona-server:
status: New → Confirmed
status: Confirmed → Incomplete
Revision history for this message
Ilya (ilantipov) wrote :

Thanks for quick reply.

I am not sure I cane ever reproduce this error because it happened only once.

If I understood you correctly - that's what you asked for

0x7fa6d5 my_print_stacktrace + 53
0x6aea44 handle_fatal_signal + 1012
0x7f297a4ff340 _end + 2034673944
0x8f1a0b ha_delete_hash_node + 171
0x8f1b1f ha_remove_all_nodes_to_page + 95
0x89327f btr_search_drop_page_hash_index + 1983
0x877b48 btr_page_reorganize_low + 648
0x879d1a btr_can_merge_with_page + 586
0x880cd8 btr_compress + 728
0x8820a1 btr_cur_compress_if_useful + 273
0x88c870 btr_cur_pessimistic_delete + 640
0x9481d0 row_purge_remove_sec_if_poss_tree + 512
0x948e26 row_purge_step + 3094
0x93d53c que_run_threads + 1500
0x859924 trx_purge + 868
0x84c9ae srv_purge_thread + 766
0x7f297a4f7182 _end + 2034640730
0x7f2978d9b30d _end + 2010147045

Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :

So, it seems it was probably something related to purge thread.

Please, send your my.cnf file content also.

Revision history for this message
Ilya (ilantipov) wrote :

Here is my.cnf

Changed in percona-server:
status: Incomplete → New
Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :

I see this:

!includedir /etc/mysql/conf.d/

at the end of my.cnf. Do you have any files in that directory? I am mostly interested in innodb-* settings there, if any.

Can you, please, upload also the entire error log of that MySQL instance.

Changed in percona-server:
status: New → Incomplete
Revision history for this message
Ilya (ilantipov) wrote :

That dir is empty.

Sorry I have cleaned up my log file.

Changed in percona-server:
status: Incomplete → New
Revision history for this message
Ilya (ilantipov) wrote :

I've got it again.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3179

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.