[MDEV-15434] Mariadb crashes several times Created: 2018-02-28  Updated: 2018-03-06  Resolved: 2018-03-06

Status: Closed
Project: MariaDB Server
Component/s: Platform Debian
Affects Version/s: 10.1.27, 10.1.28, 10.1.29, 10.1.30, 10.2.12, 10.1.31, 10.2.13, 10.2
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: dave Assignee: Alice Sherepa
Resolution: Duplicate Votes: 0
Labels: crash
Environment:

Debian 8.9


Issue Links:
Duplicate
duplicates MDEV-15247 Crash when SET NAMES 'utf8' is set Closed

 Description   

We have the problem that MariaDB continuously crashes since version 10.1.27 and newer. We suspect that it is because of queries from doctrine. doctrine has the latest version.

MySQL error log:

180228 14:08:21 [ERROR] 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.
 
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.2.13-MariaDB-log
key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=22
max_threads=122
thread_count=28
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 284439 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x572c9c8
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 = 0x7f2581b3bec8 thread_stack 0x49000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0xde6e7e]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x471)[0x7df821]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f259b80c890]
/usr/local/mysql/bin/mysqld(_ZN10TABLE_LIST33is_with_table_recursive_referenceEv+0x0)[0x751a90]
/usr/local/mysql/bin/mysqld(_ZN13st_join_table7cleanupEv+0x18)[0x6264a8]
/usr/local/mysql/bin/mysqld(_ZN4JOIN7cleanupEb+0xff)[0x6268ff]
/usr/local/mysql/bin/mysqld(_ZN4JOIN9join_freeEv+0x49)[0x626e89]
/usr/local/mysql/bin/mysqld(_ZN4JOIN10exec_innerEv+0xbcf)[0x64fc4f]
/usr/local/mysql/bin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x1fc)[0x64e58c]
/usr/local/mysql/bin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x254)[0x6501a4]
/usr/local/mysql/bin/mysqld[0x5e7994]
/usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x128d)[0x5eb14d]
/usr/local/mysql/bin/mysqld(_ZN18Prepared_statement7executeEP6Stringb+0x4cc)[0x604bec]
/usr/local/mysql/bin/mysqld(_ZN18Prepared_statement12execute_loopEP6StringbPhS2_+0x9e)[0x60a7ae]
/usr/local/mysql/bin/mysqld[0x60b316]
/usr/local/mysql/bin/mysqld(_Z19mysqld_stmt_executeP3THDPcj+0x28)[0x60b478]
/usr/local/mysql/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x20ad)[0x5f76ad]
/usr/local/mysql/bin/mysqld(_Z10do_commandP3THD+0x15d)[0x5f901d]
/usr/local/mysql/bin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x235)[0x6dda45]
/usr/local/mysql/bin/mysqld(handle_one_connection+0x3f)[0x6ddc0f]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f259b805064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f259a6e962d]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x5739fa0): SELECT p0_.id AS id_0, p0_.code AS code_1, p0_.ean AS ean_2, p0_.isbn AS isbn_3, p0_.price AS price_4, p0_.recommended_price AS recommended_price_5, p0_.brand_id AS brand_id_6, p0_.updated_at AS updated_at_7, p0_.created_at AS created_at_8, p0_.status AS status_9, p0_.weight AS weight_10, p0_.category_id AS category_id_11, p0_.brand_id AS brand_id_12, p0_.supplier_id AS supplier_id_13 FROM product p0_ INNER JOIN product_i18n p1_ ON (p1_.product_id = p0_.id) WHERE (((((p0_.category_id IN (SELECT c2_.id FROM category c2_ INNER JOIN category c3_ ON (c2_.parent IN (SELECT c4_.id FROM category c4_ WHERE c4_.parent = 0 OR c4_.id = 0)))) AND p0_.status = '1') OR p0_.category_id = 0) AND p0_.status = ('1') AND p1_.name LIKE '%kinderwagen%') OR p1_.name LIKE '%kinderwagen%' OR p1_.description LIKE '%kinderwagen%' OR p1_.short_description LIKE '%kinderwagen%') AND p0_.status = ('1') AND p0_.status = ('1') AND (p0_.id IN (SELECT p5_.product_id AS sclr_14 FROM product_specifications_options p5_ WHERE p5_.specifications_id = '12' AND p5_.specifications_options_id IN ('148'))) AND (p0_.id IN (SELECT p6_.product_id AS sclr_15 FROM product_specifications_options p6_ WHERE p6_.specifications_id = '16' AND p6_.specifications_options_id IN ('19'))) AND (p0_.id IN (SELECT p7_.product_id AS sclr_16 FROM product_specifications_options p7_ WHERE p7_.specifications_id = '26' AND p7_.specifications_options_id IN ('33'))) ORDER BY p0_.created_at ASC
Connection ID (thread ID): 3076
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,orderby_uses_equalities=on,condition_pushdown_for_derived=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.
2018-02-28 14:08:22 140630631720768 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-02-28 14:08:22 140630631720768 [Note] InnoDB: Uses event mutexes
2018-02-28 14:08:22 140630631720768 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-02-28 14:08:22 140630631720768 [Note] InnoDB: Using Linux native AIO
2018-02-28 14:08:22 140630631720768 [Note] InnoDB: Number of pools: 1
2018-02-28 14:08:22 140630631720768 [Note] InnoDB: Using generic crc32 instructions
2018-02-28 14:08:22 140630631720768 [Note] InnoDB: Initializing buffer pool, total size = 384M, instances = 1, chunk size = 128M
2018-02-28 14:08:22 140630631720768 [Note] InnoDB: Completed initialization of buffer pool
2018-02-28 14:08:22 140629620905728 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-02-28 14:08:22 140630631720768 [Note] InnoDB: Highest supported file format is Barracuda.
2018-02-28 14:08:22 140630631720768 [Note] InnoDB: Starting crash recovery from checkpoint LSN=56535338305
2018-02-28 14:08:22 140630631720768 [Note] InnoDB: Starting final batch to recover 3 pages from redo log.
2018-02-28 14:08:24 140630631720768 [Note] InnoDB: 128 out of 128 rollback segments are active.
2018-02-28 14:08:24 140630631720768 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2018-02-28 14:08:24 140630631720768 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-02-28 14:08:24 140630631720768 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-02-28 14:08:24 140630631720768 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2018-02-28 14:08:24 140630631720768 [Note] InnoDB: Waiting for purge to start
2018-02-28 14:08:24 140630631720768 [Note] InnoDB: 5.7.21 started; log sequence number 56535338621
2018-02-28 14:08:24 140629325616896 [Note] InnoDB: Loading buffer pool(s) from /home/mysql/ib_buffer_pool
2018-02-28 14:08:24 140630631720768 [Note] Plugin 'FEEDBACK' is disabled.
2018-02-28 14:08:24 140630631720768 [Note] Recovering after a crash using tc.log
2018-02-28 14:08:24 140630631720768 [Note] Starting crash recovery...
2018-02-28 14:08:24 140630631720768 [Note] Crash recovery finished.
2018-02-28 14:08:24 140629325616896 [Note] InnoDB: Buffer pool(s) load completed at 180228 14:08:24
2018-02-28 14:08:24 140630631720768 [Note] Server socket created on IP: '::'.
2018-02-28 14:08:24 140630631720768 [Note] Reading of all Master_info entries succeded
2018-02-28 14:08:24 140630631720768 [Note] Added new Master_info '' to hash table
2018-02-28 14:08:24 140630631720768 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '10.2.13-MariaDB-log'  socket: '/usr/local/mysql/data/mysql.sock'  port: 3306  MariaDB Server



 Comments   
Comment by Elena Stepanova [ 2018-03-05 ]

Probably the same bug as MDEV-15247, I'll leave it to alice to double-check.

Comment by Alice Sherepa [ 2018-03-06 ]

Looks like the same problem, I close this for now. If after fixing MDEV-15247, the problem will still appear, please do not hesitate to write back and the bug report will be reopened.

Generated at Thu Feb 08 08:21:16 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.