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.
200914 16:03:43 mysqld_safe mysqld from pid file /var/lib/mysql/
web2.lan.pid ended
200914 16:03:52 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
200914 16:03:52 [Note] InnoDB: Using mutexes to ref count buffer pool pages
200914 16:03:52 [Note] InnoDB: The InnoDB memory heap is disabled
200914 16:03:52 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
200914 16:03:52 [Note] InnoDB: Memory barrier is not used
200914 16:03:52 [Note] InnoDB: Compressed tables use zlib 1.2.7
200914 16:03:52 [Note] InnoDB: Using Linux native AIO
200914 16:03:52 [Note] InnoDB: Not using CPU crc32 instructions
200914 16:03:52 [Note] InnoDB: Initializing buffer pool, size = 128.0M
200914 16:03:52 [Note] InnoDB: Completed initialization of buffer pool
200914 16:03:52 [Note] InnoDB: Highest supported file format is Barracuda.
200914 16:03:52 [Note] InnoDB: Log scan progressed past the checkpoint lsn 28251634132
200914 16:03:52 [Note] InnoDB: Database was not shutdown normally!
200914 16:03:52 [Note] InnoDB: Starting crash recovery.
200914 16:03:52 [Note] InnoDB: Reading tablespace information from the .ibd files...
200914 16:03:52 [Note] InnoDB: Restoring possible half-written data pages
200914 16:03:52 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 28251634188
200914 16:03:52 [Note] InnoDB: 128 rollback segment(s) are active.
200914 16:03:52 [Note] InnoDB: Waiting for purge to start
2020-09-14 16:03:52 7ff55c7fc700 InnoDB: Assertion failure in thread 140691795592960 in file
trx0purge.cc line 703
InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no
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.htmlInnoDB: about forcing recovery.
200914 16:03:52 [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-bugsWe 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.0.17-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 = 467146 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+0x2e)[0xbc4e2e]
/usr/sbin/mysqld(handle_fatal_signal+0x390)[0x7338d0]
/lib64/libpthread.so.0(+0xf130)[0x7ff57ad92130]
/lib64/libc.so.6(gsignal+0x37)[0x7ff5794c85d7]
/lib64/libc.so.6(abort+0x148)[0x7ff5794c9cc8]
/usr/sbin/mysqld[0x98329b]
/usr/sbin/mysqld[0x983e85]
/usr/sbin/mysqld[0x98574e]
/usr/sbin/mysqld[0x977295]
/lib64/libpthread.so.0(+0x7df5)[0x7ff57ad8adf5]
/lib64/libc.so.6(clone+0x6d)[0x7ff5795891ad]
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.
200914 16:03:52 mysqld_safe mysqld from pid file /var/lib/mysql/
web2.lan.pid ended
