Server version: 10.0.19-MariaDB-log
key_buffer_size=67108864
read_buffer_size=8388608
max_used_connections=0
max_threads=1302
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 32089213 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
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/sbin/mysqld(my_print_stacktrace+0x2b)[0xb7bc1b]
/usr/sbin/mysqld(handle_fatal_signal+0x398)[0x72b318]
/lib64/libpthread.so.0(+0xf710)[0x7f228c5cb710]
/lib64/libc.so.6(gsignal+0x35)[0x7f228ac27625]
/lib64/libc.so.6(abort+0x175)[0x7f228ac28e05]
/usr/sbin/mysqld[0x9e90b1]
/usr/sbin/mysqld[0x9e9165]
/usr/sbin/mysqld[0x9efcbb]
/usr/sbin/mysqld[0x9ba04d]
/usr/sbin/mysqld[0x9babb3]
/usr/sbin/mysqld[0x99f281]
/usr/sbin/mysqld[0x982508]
/usr/sbin/mysqld[0x929745]
/usr/sbin/mysqld[0x9264a0]
/usr/sbin/mysqld[0x92806f]
/usr/sbin/mysqld[0x8f37eb]
/usr/sbin/mysqld[0x94eeb7]
/usr/sbin/mysqld[0x9403c9]
/lib64/libpthread.so.0(+0x79d1)[0x7f228c5c39d1]
/lib64/libc.so.6(clone+0x6d)[0x7f228acdd8fd]
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.
180112 05:05:14 mysqld_safe mysqld from pid file /var/lib/mysql/test-data.mydb.com.pid ended
180112 05:20:08 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
180112  5:20:09 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
180112  5:20:09 [Note] /usr/sbin/mysqld (mysqld 10.0.19-MariaDB-log) starting as process 14811 ...
180112  5:20:09 [Warning] option 'innodb-purge-threads': unsigned value 0 adjusted to 1
2018-01-12 05:20:09 7f01f4a0a820 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
180112  5:20:09 [Note] InnoDB: Using mutexes to ref count buffer pool pages
180112  5:20:09 [Note] InnoDB: The InnoDB memory heap is disabled
180112  5:20:09 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
180112  5:20:09 [Note] InnoDB: Memory barrier is not used
180112  5:20:09 [Note] InnoDB: Compressed tables use zlib 1.2.3
180112  5:20:09 [Note] InnoDB: Using Linux native AIO
180112  5:20:09 [Note] InnoDB: Using CPU crc32 instructions
180112  5:20:09 [Note] InnoDB: Initializing buffer pool, size = 10.0G
180112  5:20:11 [Note] InnoDB: Completed initialization of buffer pool
180112  5:20:12 [Note] InnoDB: Highest supported file format is Barracuda.
180112  5:20:13 [Note] InnoDB: 128 rollback segment(s) are active.
180112  5:20:13 [Note] InnoDB: Waiting for purge to start
InnoDB: Error: tablespace id is 2330 in the data dictionary
InnoDB: but in file ./mysql/innodb_index_stats.ibd it is 2!
2018-01-12 05:20:13 7efef8bfb700  InnoDB: Assertion failure in thread 139633560106752 in file fil0fil.cc line 635
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
180112  5:20:13 [ERROR] mysqld got signal 6 ;
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.