2020-07-17 11:57:35 0 [Note] CONNECT: Version 1.07.0001 November 12, 2019
2020-07-17 11:57:35 0 [Warning] The parameter innodb_file_format is deprecated and has no effect. It may be removed in future releases. See https://mariadb.com/kb/en/library/xtradbinnodb-file-format/
2020-07-17 11:57:35 0 [Note] InnoDB: Using Linux native AIO
2020-07-17 11:57:35 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-07-17 11:57:35 0 [Note] InnoDB: Uses event mutexes
2020-07-17 11:57:35 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-07-17 11:57:35 0 [Note] InnoDB: Number of pools: 1
2020-07-17 11:57:35 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-07-17 11:57:35 0 [Note] InnoDB: Initializing buffer pool, total size = 6G, instances = 8, chunk size = 128M
2020-07-17 11:57:36 0 [Note] InnoDB: Completed initialization of buffer pool
2020-07-17 11:57:36 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-07-17 11:57:36 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 805306368 bytes
2020-07-17 11:57:36 0 [Note] InnoDB: Setting log file ./ib_logfile1 size to 805306368 bytes
2020-07-17 11:57:36 0 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2020-07-17 11:57:36 0 [Note] InnoDB: New log files created, LSN=72130754174213
2020-07-17 11:57:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=7] log sequence number 72165594673077 is in the future! Current system log sequence number 72130754174485.
2020-07-17 11:57:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information abou
2020-07-17 11:57:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=2] log sequence number 72165586722829 is in the future! Current system log sequence number 72130754174485.

.................


200717 11:57:41 [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 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.3.22-MariaDB-1ubuntu1-log
key_buffer_size=16777216
read_buffer_size=2097152
max_used_connections=0
max_threads=3002
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 12380168 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 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x32)[0x564f9af32202]
/usr/sbin/mysqld(handle_fatal_signal+0x55d)[0x564f9aa0437d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0)[0x7fb8a662e3c0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7fb8a613d18b]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7fb8a611c859]
/usr/sbin/mysqld(+0x4d3ce9)[0x564f9a731ce9]
/usr/sbin/mysqld(+0xb05483)[0x564f9ad63483]
/usr/sbin/mysqld(+0xb12eab)[0x564f9ad70eab]
/usr/sbin/mysqld(+0xacb489)[0x564f9ad29489]
/usr/sbin/mysqld(+0xacb8af)[0x564f9ad298af]
/usr/sbin/mysqld(+0xab0793)[0x564f9ad0e793]
/usr/sbin/mysqld(+0xa6f77e)[0x564f9accd77e]
/usr/sbin/mysqld(+0xa5f5e2)[0x564f9acbd5e2]
/usr/sbin/mysqld(+0xa6a17a)[0x564f9acc817a]
/usr/sbin/mysqld(+0x4cdd67)[0x564f9a72bd67]
/usr/sbin/mysqld(+0x9355c8)[0x564f9ab935c8]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x70)[0x564f9aa06ad0]
/usr/sbin/mysqld(+0x5cfd25)[0x564f9a82dd25]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x88e)[0x564f9a82ee3e]
/usr/sbin/mysqld(+0x506391)[0x564f9a764391]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x401)[0x564f9a76b0d1]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x7fb8a611e0b3]
/usr/sbin/mysqld(_start+0x2e)[0x564f9a75e0ce]
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.
Writing a core file...