Mar 11 09:18:40 db3 mysqld: 160311  9:18:40 [ERROR] mysqld got signal 11 ;
Mar 11 09:18:40 db3 mysqld: This could be because you hit a bug. It is also possible that this binary
Mar 11 09:18:40 db3 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Mar 11 09:18:40 db3 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Mar 11 09:18:40 db3 mysqld: 
Mar 11 09:18:40 db3 mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs
Mar 11 09:18:40 db3 mysqld: 
Mar 11 09:18:40 db3 mysqld: We will try our best to scrape up some info that will hopefully help
Mar 11 09:18:40 db3 mysqld: diagnose the problem, but since we have already crashed, 
Mar 11 09:18:40 db3 mysqld: something is definitely wrong and this may fail.
Mar 11 09:18:40 db3 mysqld: 
Mar 11 09:18:40 db3 mysqld: Server version: 10.1.12-MariaDB-1~trusty
Mar 11 09:18:40 db3 mysqld: key_buffer_size=33554432
Mar 11 09:18:40 db3 mysqld: read_buffer_size=131072
Mar 11 09:18:40 db3 mysqld: max_used_connections=80
Mar 11 09:18:40 db3 mysqld: max_threads=502
Mar 11 09:18:40 db3 mysqld: thread_count=11
Mar 11 09:18:40 db3 mysqld: It is possible that mysqld could use up to 
Mar 11 09:18:40 db3 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2163478 K  bytes of memory
Mar 11 09:18:40 db3 mysqld: Hope that's ok; if not, decrease some variables in the equation.
Mar 11 09:18:40 db3 mysqld: 
Mar 11 09:18:40 db3 mysqld: Thread pointer: 0x0x7f30c2423008
Mar 11 09:18:40 db3 mysqld: Attempting backtrace. You can use the following information to find out
Mar 11 09:18:40 db3 mysqld: where mysqld died. If you see no messages after this, something went
Mar 11 09:18:40 db3 mysqld: terribly wrong...
Mar 11 09:18:40 db3 mysqld: stack_bottom = 0x7f30e3153210 thread_stack 0x48400
Mar 11 09:18:41 db3 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f30e2b6405e]
Mar 11 09:18:41 db3 mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x38d)[0x7f30e26911bd]
Mar 11 09:18:41 db3 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f30e0be8340]
Mar 11 09:18:41 db3 mysqld: /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG13mark_xid_doneEmb+0xc7)[0x7f30e2752397]
Mar 11 09:18:41 db3 mysqld: /usr/sbin/mysqld(binlog_background_thread+0x2b5)[0x7f30e2752955]
Mar 11 09:18:41 db3 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f30e0be0182]
Mar 11 09:18:41 db3 mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f30e030347d]
Mar 11 09:18:41 db3 mysqld: 
Mar 11 09:18:41 db3 mysqld: Trying to get some variables.
Mar 11 09:18:41 db3 mysqld: Some pointers may be invalid and cause the dump to abort.
Mar 11 09:18:41 db3 mysqld: Query (0x0): is an invalid pointer
Mar 11 09:18:41 db3 mysqld: Connection ID (thread ID): 3
Mar 11 09:18:41 db3 mysqld: Status: NOT_KILLED
Mar 11 09:18:41 db3 mysqld: 
Mar 11 09:18:41 db3 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
Mar 11 09:18:41 db3 mysqld: 
Mar 11 09:18:41 db3 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Mar 11 09:18:41 db3 mysqld: information that should help you find out what is causing the crash.