Thread pointer: 0x0
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 = 0x0 thread_stack 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x558cdb4aa96d]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x558cdb0c0285]
/lib64/libpthread.so.0(+0xf5e0)[0x7fe48a5715e0]
/usr/libexec/mysqld(+0x72b06d)[0x558cdb34906d]
/usr/libexec/mysqld(+0x72c516)[0x558cdb34a516]
/usr/libexec/mysqld(+0x70f99c)[0x558cdb32d99c]
/usr/libexec/mysqld(+0x711a66)[0x558cdb32fa66]
/usr/libexec/mysqld(+0x692109)[0x558cdb2b0109]
/usr/libexec/mysqld(+0x6d4593)[0x558cdb2f2593]
/usr/libexec/mysqld(+0x63b7e8)[0x558cdb2597e8]
/lib64/libpthread.so.0(+0x7e25)[0x7fe48a569e25]
/lib64/libc.so.6(clone+0x6d)[0x7fe488d6734d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
171218 08:50:48 mysqld_safe mysqld from pid file /var/run/mariadb/mariadb.pid ended
171218 09:04:21 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
171218  9:04:21 [Note] /usr/libexec/mysqld (mysqld 5.5.56-MariaDB) starting as process 2070 ...
171218  9:04:21 InnoDB: The InnoDB memory heap is disabled
171218  9:04:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins
171218  9:04:21 InnoDB: Compressed tables use zlib 1.2.7
171218  9:04:21 InnoDB: Using Linux native AIO
171218  9:04:21 InnoDB: Initializing buffer pool, size = 128.0M
171218  9:04:21 InnoDB: Completed initialization of buffer pool
171218  9:04:21 InnoDB: highest supported file format is Barracuda.
171218  9:04:21  InnoDB: Starting crash recovery from checkpoint LSN=14491245776
InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
171218  9:04:21  InnoDB: Starting final batch to recover 1552 pages from redo log
171218  9:04:21 [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 http://kb.askmonty.org/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: 5.5.56-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466711 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0x0 thread_stack 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x56252d2b596d]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x56252cecb285]
/lib64/libpthread.so.0(+0xf5e0)[0x7f927daf35e0]
/usr/libexec/mysqld(+0x72b06d)[0x56252d15406d]
/usr/libexec/mysqld(+0x72c516)[0x56252d155516]
/usr/libexec/mysqld(+0x70f99c)[0x56252d13899c]
/usr/libexec/mysqld(+0x711a66)[0x56252d13aa66]
/usr/libexec/mysqld(+0x692109)[0x56252d0bb109]
/usr/libexec/mysqld(+0x6d4593)[0x56252d0fd593]
/usr/libexec/mysqld(+0x63b7e8)[0x56252d0647e8]
/lib64/libpthread.so.0(+0x7e25)[0x7f927daebe25]
/lib64/libc.so.6(clone+0x6d)[0x7f927c2e934d]