191106 4:08:47 [ERROR] mysqld got signal 6 ;

2019-11-06 4:08:47 0 [Note] InnoDB: Using Linux native AIO
2019-11-06 4:08:47 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-11-06 4:08:47 0 [Note] InnoDB: Uses event mutexes
2019-11-06 4:08:47 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2019-11-06 4:08:47 0 [Note] InnoDB: Number of pools: 1
2019-11-06 4:08:47 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-11-06 4:08:47 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-11-06 4:08:47 0 [Note] InnoDB: Completed initialization of buffer pool
2019-11-06 4:08:47 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-11-06 4:08:47 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 50331648 bytes
2019-11-06 4:08:47 0 [Note] InnoDB: Setting log file ./ib_logfile1 size to 50331648 bytes
2019-11-06 4:08:47 0 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2019-11-06 4:08:47 0 [Note] InnoDB: New log files created, LSN=702623252
2019-11-06 04:08:47 0x7fea31d578c0 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.3.19/storage/innobase/dict/dict0dict.cc line 1443
InnoDB: Failing assertion: table->can_be_evicted
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
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: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
191106 4:08:47 [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.19-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 = 467422 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 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55e1a4f5658e]
/usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x55e1a49f354f]
sigaction.c:0(__restore_rt)[0x7fea319445f0]
:0(__GI_raise)[0x7fea2fc15337]
:0(__GI_abort)[0x7fea2fc16a28]
/usr/sbin/mysqld(+0x4d3560)[0x55e1a4733560]
/usr/sbin/mysqld(+0xaebf97)[0x55e1a4d4bf97]
/usr/sbin/mysqld(+0xb02603)[0x55e1a4d62603]
/usr/sbin/mysqld(+0xb02a1d)[0x55e1a4d62a1d]
/usr/sbin/mysqld(+0xb03976)[0x55e1a4d63976]
/usr/sbin/mysqld(+0xaf0d50)[0x55e1a4d50d50]
/usr/sbin/mysqld(+0xb4cd08)[0x55e1a4dacd08]
/usr/sbin/mysqld(+0xb578f2)[0x55e1a4db78f2]
/usr/sbin/mysqld(+0x984cf3)[0x55e1a4be4cf3]
/usr/sbin/mysqld(+0xa3b0e8)[0x55e1a4c9b0e8]
/usr/sbin/mysqld(+0x92a001)[0x55e1a4b8a001]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x55e1a49f5dd4]
/usr/sbin/mysqld(+0x5c59f0)[0x55e1a48259f0]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x9ba)[0x55e1a4826b7a]
/usr/sbin/mysqld(+0x4f8bf1)[0x55e1a4758bf1]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x4ae)[0x55e1a475edde]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fea2fc01505]
/usr/sbin/mysqld(+0x4f280d)[0x55e1a475280d]
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...
Working directory at /var/lib/mysql
Core pattern: core

InnoDB Corrupted on this server ! The Mysql is getting started in the Mode = 3

Not getting Started in Mode 1 or 2

Please help me to solve this issue !