Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: 180917 12:14:02 [ERROR] mysqld got signal 11 ; Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: This could be because you hit a bug. It is also possible that this binary Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: or one of the libraries it was linked against is corrupt, improperly built, Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: We will try our best to scrape up some info that will hopefully help Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: diagnose the problem, but since we have already crashed, Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: something is definitely wrong and this may fail. Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: Server version: 10.3.9-MariaDB-1:10.3.9+maria~trusty-log Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: key_buffer_size=134217728 Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: read_buffer_size=2097152 Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: max_used_connections=3 Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: max_threads=102 Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: thread_count=10 Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: It is possible that mysqld could use up to Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 760016 K bytes of memory Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: Hope that's ok; if not, decrease some variables in the equation. Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: Thread pointer: 0x7fd524000ae8 Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: Attempting backtrace. You can use the following information to find out Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: where mysqld died. If you see no messages after this, something went Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: terribly wrong... Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: stack_bottom = 0x7fd55c196e70 thread_stack 0x49000 Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7fd566fc636e] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x357)[0x7fd566a5cde7] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7fd564c09330] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(_ZN6st_key18actual_rec_per_keyEj+0x1d)[0x7fd56693f60d] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(_ZN13st_join_table21choose_best_splittingEdy+0x19d)[0x7fd5669cb80d] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(_Z16best_access_pathP4JOINP13st_join_tableyjbdP11st_positionS4_+0xf2)[0x7fd5668bc142] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(+0x5e059a)[0x7fd5668be59a] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(+0x5e0901)[0x7fd5668be901] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(+0x5e0b71)[0x7fd5668beb71] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(_Z11choose_planP4JOINy+0xdd)[0x7fd5668bf01d] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(_ZN4JOIN14optimize_innerEv+0x228e)[0x7fd5668df2de] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(_ZN4JOIN8optimizeEv+0x37)[0x7fd5668df837] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x94)[0x7fd5668e0e04] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x1bc)[0x7fd5668e198c] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(+0x4b968a)[0x7fd56679768a] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x6d58)[0x7fd56688cff8] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x36c)[0x7fd56688fccc] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x2355)[0x7fd566893185] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(_Z10do_commandP3THD+0x13e)[0x7fd56689422e] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x1aa)[0x7fd5669649fa] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /usr/sbin/mysqld(handle_one_connection+0x3d)[0x7fd566964b1d] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8184)[0x7fd564c01184] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fd56432403d] Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: Trying to get some variables. Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: Some pointers may be invalid and cause the dump to abort. Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: Query (0x7fd5240117b0): SELECT lId, sdate Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: FROM Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: ( Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: SELECT l.lId, sgh.psd AS sdate, t.sgId Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: FROM l Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: INNER JOIN t ON (l.a=t.tId) Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: INNER JOIN sgh ON sgh.sgId=t.sgId Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: GROUP BY l.lId, sdate, t.sgId Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: ) us Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: INNER JOIN sgh ON sgh.sgId=us.sgId AND sgh.psd=sdate Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: GROUP BY lId, sdate Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: LIMIT 0, 1000 Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: Connection ID (thread ID): 11 Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: Status: NOT_KILLED Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: Sep 17 11:14:02 vagrant-ubuntu-trusty-64 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,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains Sep 17 11:14:02 vagrant-ubuntu-trusty-64 mysqld: information that should help you find out what is causing the crash.