Mar  7 20:34:17 appanalytics1 mysqld: This could be because you hit a bug. It is also possible that this binary

Mar  7 20:34:17 appanalytics1 mysqld: or one of the libraries it was linked against is corrupt, improperly built,

Mar  7 20:34:17 appanalytics1 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.

Mar  7 20:34:17 appanalytics1 mysqld: 

Mar  7 20:34:17 appanalytics1 mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs

Mar  7 20:34:17 appanalytics1 mysqld: 

Mar  7 20:34:17 appanalytics1 mysqld: We will try our best to scrape up some info that will hopefully help

Mar  7 20:34:17 appanalytics1 mysqld: diagnose the problem, but since we have already crashed, 

Mar  7 20:34:17 appanalytics1 mysqld: something is definitely wrong and this may fail.

Mar  7 20:34:17 appanalytics1 mysqld: 

Mar  7 20:34:17 appanalytics1 mysqld: Server version: 10.1.21-MariaDB-1~trusty

Mar  7 20:34:17 appanalytics1 mysqld: key_buffer_size=134217728

Mar  7 20:34:17 appanalytics1 mysqld: read_buffer_size=2097152

Mar  7 20:34:17 appanalytics1 mysqld: max_used_connections=153

Mar  7 20:34:17 appanalytics1 mysqld: max_threads=252

Mar  7 20:34:17 appanalytics1 mysqld: thread_count=3

Mar  7 20:34:17 appanalytics1 mysqld: It is possible that mysqld could use up to 

Mar  7 20:34:17 appanalytics1 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1684515 K  bytes of memory

Mar  7 20:34:17 appanalytics1 mysqld: Hope that's ok; if not, decrease some variables in the equation.

Mar  7 20:34:17 appanalytics1 mysqld: 

Mar  7 20:34:17 appanalytics1 mysqld: Thread pointer: 0x7feb3a412008

Mar  7 20:34:17 appanalytics1 mysqld: Attempting backtrace. You can use the following information to find out

Mar  7 20:34:17 appanalytics1 mysqld: terribly wrong...

Mar  7 20:34:17 appanalytics1 mysqld: stack_bottom = 0x7feec255d210 thread_stack 0x48400

Mar  7 20:34:17 appanalytics1 mysqld: *** buffer overflow detected ***: /usr/sbin/mysqld terminated