[MDEV-8161] MariaDB Random Crash Created: 2015-05-14  Updated: 2015-07-13  Resolved: 2015-07-13

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.0.19
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: AS Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: need_feedback
Environment:

Ver 15.1 Distrib 10.0.19-MariaDB, for Linux (x86_64) using readline 5.1
cPanel based server
CentOS 6


 Description   

Hi,

My sincerest apologies if I have done anything wrong, this is the first time I have used the MariaDB bug reporting system. Never the less, I run a cPanel environment with MariaDB. For some reason over the last few days we've had reports of MariaDB randomly restarting.

So I've checked the /var/lib/mysql/server.err log to see this:

Server version: 10.0.19-MariaDB
 
key_buffer_size=67108864
 
read_buffer_size=131072
 
max_used_connections=30
 
max_threads=102
 
thread_count=12
 
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 289485 K  bytes of memory
 
Hope that's ok; if not, decrease some variables in the equation.
 
 
 
Thread pointer: 0x0x7f7db3fcd008
 
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 = 0x7f7ded4fed30 thread_stack 0x48000
 
/usr/sbin/mysqld(my_print_stacktrace+0x2b)[0xb7bc1b]
 
/usr/sbin/mysqld(handle_fatal_signal+0x398)[0x72b318]
 
/lib64/libpthread.so.0[0x312820f710]
 
/usr/sbin/mysqld(_ZN10Item_fieldC1EP5Field+0xe)[0x743dee]
 
/usr/sbin/mysqld(_ZN14Item_subselect18get_tmp_table_itemEP3THD+0x6e)[0x7a698e]
 
/usr/sbin/mysqld(_ZN20Item_direct_view_ref18get_tmp_table_itemEP3THD+0x165)[0x752c75]
 
/usr/sbin/mysqld(_ZN4JOIN10exec_innerEv+0x1965)[0x625fb5]
 
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x11)[0x626ee1]
 
/usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x1dd)[0x623acd]
 
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x28d)[0x62723d]
 
/usr/sbin/mysqld[0x5cd756]
 
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x4e91)[0x5d8bc1]
 
/usr/sbin/mysqld[0x5da5e7]
 
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1c7c)[0x5dc9cc]
 
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x453)[0x699b53]
 
/usr/sbin/mysqld(handle_one_connection+0x42)[0x699c22]
 
/lib64/libpthread.so.0[0x31282079d1]
 
/lib64/libc.so.6(clone+0x6d)[0x3127ee88dd]
 
 
 
Trying to get some variables.
 
Some pointers may be invalid and cause the dump to abort.
 
Query (0x7f7d956a8020): is an invalid pointer
 
Connection ID (thread ID): 13147
 
Status: NOT_KILLED
 
 
 
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on
 
 
 
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.

Here's a copy of my.cnf

[mysqld]
 
max_allowed_packet=268435456
 
open_files_limit=50000
 
max_connections=100
 
innodb_buffer_pool_size=5G
 
query_cache_size=32M
 
join_buffer_size=1024K
 
tmp_table_size=48M
 
max_heap_table_size=48M
 
key_buffer_size=64M
 
low_priority_updates=1
 
local-infile=0
 
sql_mode=""
 
default-storage-engine=MyISAM
 
innodb_file_per_table=1
 
 
 
general_log = 1
 
general_log_file = /var/log/mysqld.log
 
log-error = /var/log/mysqld.error.log

Any advice on what I should do to further diagnose this issue would be greatly appreciated.

 Comments   
Comment by Elena Stepanova [ 2015-05-15 ]

Hi,

How high is the load on your server? Would it be possible for you to enable general logging for one session, till the next crash? It would help us understand which query it crashes on.

If you can do that, please run set global general_log_file='<path/filename>', general_log=1;

When/if the crash happens again, backup both error and general log files. If it's possible, please upload both of them to our ftp (ftp.askmonty.org/private). If the log is confidential, here is how you find the guilty query:

In the error log, you can see the line
Connection ID (thread ID): NNNNN
(In your current log it's 13147, but will be different next time).
In the general log, from the end of it backwards, search for this NNNNN in the form of Query NNNNN. That is, it should be the last query in the log which belongs to this thread. That would be the guilty one.
Then please paste the query and SHOW CREATE TABLE .. or SHOW CREATE VIEW... for all tables/views involved in the query, and also definitions of the procedures/functions that participate in the query.
If any part of this information is private, please instead of pasting it here, upload it to ftp.askmonty.org/private and comment to let us know it's done.

Then we can proceed and request further information if needed.
Thanks!

Comment by Elena Stepanova [ 2015-06-14 ]

x1hash,

Do you keep experiencing the problem?
Would you be able to provide information as described above?

Comment by Elena Stepanova [ 2015-07-13 ]

Unfortunately, there is not enough to work with, so I have to close it as incomplete for now. Please by all means comment on the issue if you have more information, and the report will be re-opened, we are very interested in investigating it.

Generated at Thu Feb 08 07:25:05 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.