2019-01-22T06:54:13.934027Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-01-22T06:54:13.934984Z 0 [Note] mysqld (mysqld 5.7.24-0ubuntu0.18.04.1) starting as process 5997 ...
2019-01-22T06:54:13.937591Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-01-22T06:54:13.937600Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-01-22T06:54:13.937603Z 0 [Note] InnoDB: Uses event mutexes
2019-01-22T06:54:13.937606Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-01-22T06:54:13.937608Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-01-22T06:54:13.937610Z 0 [Note] InnoDB: Using Linux native AIO
2019-01-22T06:54:13.937738Z 0 [Note] InnoDB: Number of pools: 1
2019-01-22T06:54:13.937791Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-01-22T06:54:13.938661Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-01-22T06:54:13.943198Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-01-22T06:54:13.944675Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-01-22T06:54:13.995617Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000!
2019-01-22 12:24:13 0x7fc2b32b6740  InnoDB: Assertion failure in thread 140474206349120 in file ut0ut.cc line 942
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
06:54:13 UTC - 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76387 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 = 0 thread_stack 0x30000
mysqld(my_print_stacktrace+0x3b)[0xebde1b]
mysqld(handle_fatal_signal+0x48b)[0x790bbb]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7fc2b1e14890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fc2b1110e97]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fc2b1112801]
mysqld[0x7675ca]
mysqld(_ZN2ib5fatalD1Ev+0x66)[0x1094aa6]
mysqld[0x11426ec]
mysqld[0x1142c6d]
mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x322)[0x114d6d2]
mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xdd)[0x11007fd]
mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4e5)[0x10d2555]
mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x14f)[0x1072dbf]
mysqld[0x103a218]
mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2de6)[0x103e546]
mysqld[0xf05cc8]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x7de31f]
mysqld[0xc99ce5]
mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x1e5)[0xc9d1f5]
mysqld[0x788e70]
mysqld(_Z11mysqld_mainiPPc+0x785)[0x78a585]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fc2b10f3b97]
mysqld(_start+0x2a)[0x780c1a]
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.
2019-01-22T06:54:14.366625Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-01-22T06:54:14.367546Z 0 [Note] mysqld (mysqld 5.7.24-0ubuntu0.18.04.1) starting as process 6016 ...
2019-01-22T06:54:14.370199Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-01-22T06:54:14.370214Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-01-22T06:54:14.370217Z 0 [Note] InnoDB: Uses event mutexes
2019-01-22T06:54:14.370219Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-01-22T06:54:14.370222Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-01-22T06:54:14.370224Z 0 [Note] InnoDB: Using Linux native AIO
2019-01-22T06:54:14.370356Z 0 [Note] InnoDB: Number of pools: 1
2019-01-22T06:54:14.370411Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-01-22T06:54:14.371210Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-01-22T06:54:14.375761Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-01-22T06:54:14.377105Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-01-22T06:54:14.388045Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000!
2019-01-22 12:24:14 0x7f110748b740  InnoDB: Assertion failure in thread 139711113377600 in file ut0ut.cc line 942
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
06:54:14 UTC - 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76387 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 = 0 thread_stack 0x30000
mysqld(my_print_stacktrace+0x3b)[0xebde1b]
mysqld(handle_fatal_signal+0x48b)[0x790bbb]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f1105fe9890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f11052e5e97]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f11052e7801]
mysqld[0x7675ca]
mysqld(_ZN2ib5fatalD1Ev+0x66)[0x1094aa6]
mysqld[0x11426ec]
mysqld[0x1142c6d]
mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x322)[0x114d6d2]
mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xdd)[0x11007fd]
mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4e5)[0x10d2555]
mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x14f)[0x1072dbf]
mysqld[0x103a218]
mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2de6)[0x103e546]
mysqld[0xf05cc8]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x7de31f]
mysqld[0xc99ce5]
mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x1e5)[0xc9d1f5]
mysqld[0x788e70]
mysqld(_Z11mysqld_mainiPPc+0x785)[0x78a585]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f11052c8b97]
mysqld(_start+0x2a)[0x780c1a]
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.
2019-01-22T06:54:15.346302Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-01-22T06:54:15.347218Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.24-0ubuntu0.18.04.1) starting as process 6108 ...
2019-01-22T06:54:15.349581Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-01-22T06:54:15.349595Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-01-22T06:54:15.349598Z 0 [Note] InnoDB: Uses event mutexes
2019-01-22T06:54:15.349600Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-01-22T06:54:15.349603Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-01-22T06:54:15.349605Z 0 [Note] InnoDB: Using Linux native AIO
2019-01-22T06:54:15.349737Z 0 [Note] InnoDB: Number of pools: 1
2019-01-22T06:54:15.349791Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-01-22T06:54:15.350600Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-01-22T06:54:15.355170Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-01-22T06:54:15.356409Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-01-22T06:54:15.367947Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000!
2019-01-22 12:24:15 0x7fab75e4d740  InnoDB: Assertion failure in thread 140374394066752 in file ut0ut.cc line 942
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
06:54:15 UTC - 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76387 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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xebde1b]
/usr/sbin/mysqld(handle_fatal_signal+0x48b)[0x790bbb]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7fab749ab890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fab73ca7e97]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fab73ca9801]
/usr/sbin/mysqld[0x7675ca]
/usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0x66)[0x1094aa6]
/usr/sbin/mysqld[0x11426ec]
/usr/sbin/mysqld[0x1142c6d]
/usr/sbin/mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x322)[0x114d6d2]
/usr/sbin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xdd)[0x11007fd]
/usr/sbin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4e5)[0x10d2555]
/usr/sbin/mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x14f)[0x1072dbf]
/usr/sbin/mysqld[0x103a218]
/usr/sbin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2de6)[0x103e546]
/usr/sbin/mysqld[0xf05cc8]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x7de31f]
/usr/sbin/mysqld[0xc99ce5]
/usr/sbin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x1e5)[0xc9d1f5]
/usr/sbin/mysqld[0x788e70]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x785)[0x78a585]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fab73c8ab97]
/usr/sbin/mysqld(_start+0x2a)[0x780c1a]
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.
2019-01-22T06:54:15.842884Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-01-22T06:54:15.844617Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.24-0ubuntu0.18.04.1) starting as process 6134 ...
2019-01-22T06:54:15.847129Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-01-22T06:54:15.847142Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-01-22T06:54:15.847145Z 0 [Note] InnoDB: Uses event mutexes
2019-01-22T06:54:15.847147Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-01-22T06:54:15.847150Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-01-22T06:54:15.847152Z 0 [Note] InnoDB: Using Linux native AIO
2019-01-22T06:54:15.847282Z 0 [Note] InnoDB: Number of pools: 1
2019-01-22T06:54:15.847335Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-01-22T06:54:15.848143Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-01-22T06:54:15.852885Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-01-22T06:54:15.854179Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-01-22T06:54:15.866371Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000!
2019-01-22 12:24:15 0x7fd3c9644740  InnoDB: Assertion failure in thread 140547593619264 in file ut0ut.cc line 942
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
06:54:15 UTC - 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76387 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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xebde1b]
/usr/sbin/mysqld(handle_fatal_signal+0x48b)[0x790bbb]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7fd3c81a2890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fd3c749ee97]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fd3c74a0801]
/usr/sbin/mysqld[0x7675ca]
/usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0x66)[0x1094aa6]
/usr/sbin/mysqld[0x11426ec]
/usr/sbin/mysqld[0x1142c6d]
/usr/sbin/mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x322)[0x114d6d2]
/usr/sbin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xdd)[0x11007fd]
/usr/sbin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4e5)[0x10d2555]
/usr/sbin/mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x14f)[0x1072dbf]
/usr/sbin/mysqld[0x103a218]
/usr/sbin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2de6)[0x103e546]
/usr/sbin/mysqld[0xf05cc8]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x7de31f]
/usr/sbin/mysqld[0xc99ce5]
/usr/sbin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x1e5)[0xc9d1f5]
/usr/sbin/mysqld[0x788e70]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x785)[0x78a585]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fd3c7481b97]
/usr/sbin/mysqld(_start+0x2a)[0x780c1a]
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.
2019-01-22T06:54:16.374216Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-01-22T06:54:16.375135Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.24-0ubuntu0.18.04.1) starting as process 6158 ...
2019-01-22T06:54:16.377506Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-01-22T06:54:16.377519Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-01-22T06:54:16.377522Z 0 [Note] InnoDB: Uses event mutexes
2019-01-22T06:54:16.377524Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-01-22T06:54:16.377526Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-01-22T06:54:16.377528Z 0 [Note] InnoDB: Using Linux native AIO
2019-01-22T06:54:16.377656Z 0 [Note] InnoDB: Number of pools: 1
2019-01-22T06:54:16.377709Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-01-22T06:54:16.378494Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-01-22T06:54:16.383118Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-01-22T06:54:16.384455Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-01-22T06:54:16.395462Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000!
2019-01-22 12:24:16 0x7ff1a8932740  InnoDB: Assertion failure in thread 140675892062016 in file ut0ut.cc line 942
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
06:54:16 UTC - 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76387 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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xebde1b]
/usr/sbin/mysqld(handle_fatal_signal+0x48b)[0x790bbb]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7ff1a7490890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7ff1a678ce97]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7ff1a678e801]
/usr/sbin/mysqld[0x7675ca]
/usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0x66)[0x1094aa6]
/usr/sbin/mysqld[0x11426ec]
/usr/sbin/mysqld[0x1142c6d]
/usr/sbin/mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x322)[0x114d6d2]
/usr/sbin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xdd)[0x11007fd]
/usr/sbin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4e5)[0x10d2555]
/usr/sbin/mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x14f)[0x1072dbf]
/usr/sbin/mysqld[0x103a218]
/usr/sbin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2de6)[0x103e546]
/usr/sbin/mysqld[0xf05cc8]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x7de31f]
/usr/sbin/mysqld[0xc99ce5]
/usr/sbin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x1e5)[0xc9d1f5]
/usr/sbin/mysqld[0x788e70]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x785)[0x78a585]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7ff1a676fb97]
/usr/sbin/mysqld(_start+0x2a)[0x780c1a]
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.
2019-01-22T06:54:16.834492Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-01-22T06:54:16.835413Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.24-0ubuntu0.18.04.1) starting as process 6182 ...
2019-01-22T06:54:16.837796Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-01-22T06:54:16.837810Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-01-22T06:54:16.837813Z 0 [Note] InnoDB: Uses event mutexes
2019-01-22T06:54:16.837815Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-01-22T06:54:16.837817Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-01-22T06:54:16.837820Z 0 [Note] InnoDB: Using Linux native AIO
2019-01-22T06:54:16.837949Z 0 [Note] InnoDB: Number of pools: 1
2019-01-22T06:54:16.838003Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-01-22T06:54:16.838808Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-01-22T06:54:16.843441Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-01-22T06:54:16.844712Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-01-22T06:54:16.855594Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000!
2019-01-22 12:24:16 0x7fd2d9b99740  InnoDB: Assertion failure in thread 140543572678464 in file ut0ut.cc line 942
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
06:54:16 UTC - 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76387 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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xebde1b]
/usr/sbin/mysqld(handle_fatal_signal+0x48b)[0x790bbb]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7fd2d86f7890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fd2d79f3e97]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fd2d79f5801]
/usr/sbin/mysqld[0x7675ca]
/usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0x66)[0x1094aa6]
/usr/sbin/mysqld[0x11426ec]
/usr/sbin/mysqld[0x1142c6d]
/usr/sbin/mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x322)[0x114d6d2]
/usr/sbin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xdd)[0x11007fd]
/usr/sbin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4e5)[0x10d2555]
/usr/sbin/mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x14f)[0x1072dbf]
/usr/sbin/mysqld[0x103a218]
/usr/sbin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2de6)[0x103e546]
/usr/sbin/mysqld[0xf05cc8]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x7de31f]
/usr/sbin/mysqld[0xc99ce5]
/usr/sbin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x1e5)[0xc9d1f5]
/usr/sbin/mysqld[0x788e70]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x785)[0x78a585]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fd2d79d6b97]
/usr/sbin/mysqld(_start+0x2a)[0x780c1a]
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.
2019-01-22T06:54:17.374313Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-01-22T06:54:17.375232Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.24-0ubuntu0.18.04.1) starting as process 6206 ...
2019-01-22T06:54:17.377616Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-01-22T06:54:17.377628Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-01-22T06:54:17.377631Z 0 [Note] InnoDB: Uses event mutexes
2019-01-22T06:54:17.377634Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-01-22T06:54:17.377636Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-01-22T06:54:17.377638Z 0 [Note] InnoDB: Using Linux native AIO
2019-01-22T06:54:17.377770Z 0 [Note] InnoDB: Number of pools: 1
2019-01-22T06:54:17.377824Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-01-22T06:54:17.378611Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-01-22T06:54:17.383078Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-01-22T06:54:17.384390Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-01-22T06:54:17.395378Z 0 [ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4000!
2019-01-22 12:24:17 0x7ff02a461740  InnoDB: Assertion failure in thread 140669478115136 in file ut0ut.cc line 942
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
06:54:17 UTC - 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 76387 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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xebde1b]
/usr/sbin/mysqld(handle_fatal_signal+0x48b)[0x790bbb]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7ff028fbf890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7ff0282bbe97]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7ff0282bd801]
/usr/sbin/mysqld[0x7675ca]
/usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0x66)[0x1094aa6]
/usr/sbin/mysqld[0x11426ec]
/usr/sbin/mysqld[0x1142c6d]
/usr/sbin/mysqld(_Z6fil_ioRK9IORequestbRK9page_id_tRK11page_size_tmmPvS8_+0x322)[0x114d6d2]
/usr/sbin/mysqld(_Z13buf_read_pageRK9page_id_tRK11page_size_t+0xdd)[0x11007fd]
/usr/sbin/mysqld(_Z16buf_page_get_genRK9page_id_tRK11page_size_tmP11buf_block_tmPKcmP5mtr_tb+0x4e5)[0x10d2555]
/usr/sbin/mysqld(_Z31trx_rseg_get_n_undo_tablespacesPm+0x14f)[0x1072dbf]
/usr/sbin/mysqld[0x103a218]
/usr/sbin/mysqld(_Z34innobase_start_or_create_for_mysqlv+0x2de6)[0x103e546]
/usr/sbin/mysqld[0xf05cc8]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4f)[0x7de31f]
/usr/sbin/mysqld[0xc99ce5]
/usr/sbin/mysqld(_Z40plugin_register_builtin_and_init_core_sePiPPc+0x1e5)[0xc9d1f5]
/usr/sbin/mysqld[0x788e70]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x785)[0x78a585]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7ff02829eb97]
/usr/sbin/mysqld(_start+0x2a)[0x780c1a]
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.