2017-06-08 13:06:54 140715399149600 [Note] /usr/sbin/mysqld: ready for connections.

Version: '10.1.19-MariaDB-enterprise'  socket: '/var/lib/mysql/mysql.sock'  port: 6603  MariaDB Enterprise Certified Binary

170608 13:11:53 [ERROR] mysqld got signal 11 ;

This could be because you hit a bug. It is also possible that this binary

or one of the libraries it was linked against is corrupt, improperly built,

or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help

diagnose the problem, but since we have already crashed,

something is definitely wrong and this may fail.

Server version: 10.1.19-MariaDB-enterprise

key_buffer_size=67108864

read_buffer_size=131072

max_used_connections=2

max_threads=1002

thread_count=2

It is possible that mysqld could use up to

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2266447 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7ffa1173c008

Attempting backtrace. You can use the following information to find out

where mysqld died. If you see no messages after this, something went

terribly wrong...

stack_bottom = 0x7ffadb4ec140 thread_stack 0x48400

/usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7ffadc0a653b]

/usr/sbin/mysqld(handle_fatal_signal+0x475)[0x7ffadbc00605]

/lib64/libpthread.so.0(+0x369de0f7e0)[0x7ffadb2017e0]

/usr/sbin/mysqld(+0x72abcd)[0x7ffadbd5cbcd]

/usr/sbin/mysqld(+0x72b4f9)[0x7ffadbd5d4f9]

/usr/sbin/mysqld(+0x4bdc2f)[0x7ffadbaefc2f]

/usr/sbin/mysqld(+0x4b5917)[0x7ffadbae7917]

/usr/sbin/mysqld(_Z14get_all_tablesP3THDP10TABLE_LISTP4Item+0x81e)[0x7ffadbafc45e]

/usr/sbin/mysqld(_Z24get_schema_tables_resultP4JOIN23enum_schema_table_state+0x28e)[0x7ffadbaf9fae]

170608 13:11:53 mysqld_safe Number of processes running now: 0

170608 13:11:53 mysqld_safe mysqld restarted