Mar 30 18:30:51 db04 mysqld: 160330 18:30:51 [ERROR] mysqld got signal 11 ;
Mar 30 18:30:51 db04 mysqld: This could be because you hit a bug. It is also possible that this binary
Mar 30 18:30:51 db04 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Mar 30 18:30:51 db04 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Mar 30 18:30:51 db04 mysqld: 
Mar 30 18:30:51 db04 mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs
Mar 30 18:30:51 db04 mysqld: 
Mar 30 18:30:51 db04 mysqld: We will try our best to scrape up some info that will hopefully help
Mar 30 18:30:51 db04 mysqld: diagnose the problem, but since we have already crashed, 
Mar 30 18:30:51 db04 mysqld: something is definitely wrong and this may fail.
Mar 30 18:30:51 db04 mysqld: 
Mar 30 18:30:51 db04 mysqld: Server version: 10.1.12-MariaDB-1~trusty
Mar 30 18:30:51 db04 mysqld: key_buffer_size=134217728
Mar 30 18:30:51 db04 mysqld: read_buffer_size=2097152
Mar 30 18:30:51 db04 mysqld: max_used_connections=57
Mar 30 18:30:51 db04 mysqld: max_threads=102
Mar 30 18:30:51 db04 mysqld: thread_count=49
Mar 30 18:30:51 db04 mysqld: It is possible that mysqld could use up to 
Mar 30 18:30:51 db04 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759828 K  bytes of memory
Mar 30 18:30:51 db04 mysqld: Hope that's ok; if not, decrease some variables in the equation.
Mar 30 18:30:51 db04 mysqld: 
Mar 30 18:30:51 db04 mysqld: Thread pointer: 0x0x7f0a55849008
Mar 30 18:30:51 db04 mysqld: Attempting backtrace. You can use the following information to find out
Mar 30 18:30:51 db04 mysqld: where mysqld died. If you see no messages after this, something went
Mar 30 18:30:51 db04 mysqld: terribly wrong...
Mar 30 18:30:51 db04 mysqld: stack_bottom = 0x7f0a732e6210 thread_stack 0x48400
Mar 30 18:30:51 db04 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f0a72cf705e]
Mar 30 18:30:51 db04 mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x38d)[0x7f0a728241bd]
Mar 30 18:30:51 db04 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f0a70d7a340]
Mar 30 18:30:51 db04 mysqld: /usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG13mark_xid_doneEmb+0xc7)[0x7f0a728e5397]
Mar 30 18:30:51 db04 mysqld: /usr/sbin/mysqld(binlog_background_thread+0x2b5)[0x7f0a728e5955]
Mar 30 18:30:51 db04 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f0a70d72182]
Mar 30 18:30:51 db04 mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f0a7049547d]
Mar 30 18:30:51 db04 mysqld: 
Mar 30 18:30:51 db04 mysqld: Trying to get some variables.
Mar 30 18:30:51 db04 mysqld: Some pointers may be invalid and cause the dump to abort.
Mar 30 18:30:51 db04 mysqld: Query (0x0): is an invalid pointer
Mar 30 18:30:51 db04 mysqld: Connection ID (thread ID): 3
Mar 30 18:30:51 db04 mysqld: Status: NOT_KILLED
Mar 30 18:30:51 db04 mysqld: 
Mar 30 18:30:51 db04 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 30 18:30:51 db04 mysqld: 
Mar 30 18:30:51 db04 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Mar 30 18:30:51 db04 mysqld: information that should help you find out what is causing the crash.
Mar 30 18:30:52 db04 mysqld_safe: Number of processes running now: 0
Mar 30 18:30:52 db04 mysqld_safe: WSREP: not restarting wsrep node automatically