Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Incomplete
-
10.1.14
-
None
-
centOS7 on Google Compute Engine
Description
Server crashes frequently now (once or twice per day) for no apparent reason. A previous report looked like it was linked to CONNECT engine or unixODBC issues, but this one I can't tell.
Jun 25 10:19:04 si-mariadb-3 mysqld: 160625 10:19:04 [ERROR] mysqld got signal 11 ; |
Jun 25 10:19:04 si-mariadb-3 mysqld: This could be because you hit a bug. It is also possible that this binary |
Jun 25 10:19:04 si-mariadb-3 mysqld: or one of the libraries it was linked against is corrupt, improperly built, |
Jun 25 10:19:04 si-mariadb-3 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. |
Jun 25 10:19:04 si-mariadb-3 mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs |
Jun 25 10:19:04 si-mariadb-3 mysqld: We will try our best to scrape up some info that will hopefully help |
Jun 25 10:19:04 si-mariadb-3 mysqld: diagnose the problem, but since we have already crashed, |
Jun 25 10:19:04 si-mariadb-3 mysqld: something is definitely wrong and this may fail. |
Jun 25 10:19:04 si-mariadb-3 mysqld: Server version: 10.1.14-MariaDB |
Jun 25 10:19:04 si-mariadb-3 mysqld: key_buffer_size=134217728 |
Jun 25 10:19:04 si-mariadb-3 mysqld: read_buffer_size=131072 |
Jun 25 10:19:04 si-mariadb-3 mysqld: max_used_connections=1 |
Jun 25 10:19:04 si-mariadb-3 mysqld: max_threads=153 |
Jun 25 10:19:04 si-mariadb-3 mysqld: thread_count=2 |
Jun 25 10:19:04 si-mariadb-3 mysqld: It is possible that mysqld could use up to |
Jun 25 10:19:04 si-mariadb-3 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467113 K bytes of memory |
Jun 25 10:19:04 si-mariadb-3 mysqld: Hope that's ok; if not, decrease some variables in the equation. |
Jun 25 10:19:04 si-mariadb-3 mysqld: Thread pointer: 0x0x7f137ee70008 |
Jun 25 10:19:04 si-mariadb-3 mysqld: Attempting backtrace. You can use the following information to find out |
Jun 25 10:19:04 si-mariadb-3 mysqld: where mysqld died. If you see no messages after this, something went |
Jun 25 10:19:04 si-mariadb-3 mysqld: terribly wrong... |
Jun 25 10:19:04 si-mariadb-3 mysqld: stack_bottom = 0x7f13ae025130 thread_stack 0x48400 |
Jun 25 10:19:04 si-mariadb-3 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f13aebc71be] |
Jun 25 10:19:04 si-mariadb-3 mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x38d)[0x7f13ae6f2f0d] |
Jun 25 10:19:04 si-mariadb-3 mysqld: /lib64/libpthread.so.0(+0xf100)[0x7f13add11100] |
Jun 25 10:19:04 si-mariadb-3 mysqld: /usr/sbin/mysqld(+0x82dcb3)[0x7f13ae96fcb3] |
Jun 25 10:19:04 si-mariadb-3 mysqld: /usr/sbin/mysqld(+0x83220d)[0x7f13ae97420d] |
Jun 25 10:19:04 si-mariadb-3 mysqld: /usr/sbin/mysqld(+0x83254b)[0x7f13ae97454b] |
Jun 25 10:19:04 si-mariadb-3 mysqld: /usr/sbin/mysqld(+0x71708b)[0x7f13ae85908b] |
Jun 25 10:19:04 si-mariadb-3 mysqld: /usr/sbin/mysqld(+0x5b1ad1)[0x7f13ae6f3ad1] |
Jun 25 10:19:04 si-mariadb-3 mysqld: /usr/sbin/mysqld(_Z24plugin_foreach_with_maskP3THDPFcS0_P13st_plugin_intPvEijS3_+0x206)[0x7f13ae582906] |
Jun 25 10:19:04 si-mariadb-3 mysqld: /usr/sbin/mysqld(_ZN3THDD1Ev+0x20e)[0x7f13ae547bae] |
Jun 25 10:19:04 si-mariadb-3 mysqld: /usr/sbin/mysqld(_ZN3THDD0Ev+0x11)[0x7f13ae548181] |
Jun 25 10:19:04 si-mariadb-3 mysqld: /usr/sbin/mysqld(_Z10unlink_thdP3THD+0x172)[0x7f13ae4dc7c2] |
Jun 25 10:19:04 si-mariadb-3 mysqld: /usr/sbin/mysqld(_Z29one_thread_per_connection_endP3THDb+0x20)[0x7f13ae4dc820] |
Jun 25 10:19:04 si-mariadb-3 mysqld: /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x113)[0x7f13ae6415b3] |
Jun 25 10:19:04 si-mariadb-3 mysqld: /usr/sbin/mysqld(handle_one_connection+0x40)[0x7f13ae641800] |
Jun 25 10:19:04 si-mariadb-3 mysqld: /lib64/libpthread.so.0(+0x7dc5)[0x7f13add09dc5] |
Jun 25 10:19:04 si-mariadb-3 mysqld: /lib64/libc.so.6(clone+0x6d)[0x7f13ac12bced] |
Jun 25 10:19:04 si-mariadb-3 mysqld: Trying to get some variables. |
Jun 25 10:19:04 si-mariadb-3 mysqld: Some pointers may be invalid and cause the dump to abort. |
Jun 25 10:19:04 si-mariadb-3 mysqld: Query (0x0): |
Jun 25 10:19:04 si-mariadb-3 mysqld: Connection ID (thread ID): 164 |
Jun 25 10:19:04 si-mariadb-3 mysqld: Status: KILL_CONNECTION |
Jun 25 10:19:04 si-mariadb-3 mysqld: 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,optimi
|
ze_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on
|
Jun 25 10:19:04 si-mariadb-3 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains |
Jun 25 10:19:04 si-mariadb-3 mysqld: information that should help you find out what is causing the crash. |