2019-10-29 15:29:11 139800646204800 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2019-10-29 15:29:12 139800646204800 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-10-29 15:29:12 139800646204800 [Note] InnoDB: The InnoDB memory heap is disabled
2019-10-29 15:29:12 139800646204800 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-10-29 15:29:12 139800646204800 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-10-29 15:29:12 139800646204800 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-10-29 15:29:12 139800646204800 [Note] InnoDB: Using Linux native AIO
2019-10-29 15:29:12 139800646204800 [Note] InnoDB: Using generic crc32 instructions
2019-10-29 15:29:13 139800646204800 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-10-29 15:29:13 139800646204800 [Note] InnoDB: Completed initialization of buffer pool
2019-10-29 15:29:15 139800646204800 [Note] InnoDB: Highest supported file format is Barracuda.
2019-10-29 15:29:15 139800646204800 [Note] InnoDB: The log sequence number 70583645 in ibdata file do not match the log sequence number 1402269061 in the ib_logfiles!
2019-10-29 15:29:16 139800646204800 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2019-10-29 15:29:22 139800646204800 [Note] InnoDB: 128 rollback segment(s) are active.
2019-10-29 15:29:22 139800646204800 [Note] InnoDB: Waiting for purge to start
2019-10-29 15:29:22 139800646204800 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.42-84.2 started; log sequence number 1402269061
2019-10-29 15:29:24 139799985911552 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-10-29 15:29:24 139800646204800 [Note] Plugin 'FEEDBACK' is disabled.
2019-10-29 15:29:24 139800646204800 [Note] Recovering after a crash using tc.log
2019-10-29 15:29:24 139800646204800 [Note] Starting crash recovery...
2019-10-29 15:29:24 139800646204800 [Note] Crash recovery finished.
2019-10-29 15:29:25 139800646204800 [Note] Server socket created on IP: '127.0.0.1'.
2019-10-29 15:29:25 139800646204800 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.1.38-MariaDB-0+deb9u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Debian 9.8
2019-10-29 15:41:08 139873595026816 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2019-10-29 15:41:08 139873595026816 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-10-29 15:41:08 139873595026816 [Note] InnoDB: The InnoDB memory heap is disabled
2019-10-29 15:41:08 139873595026816 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-10-29 15:41:08 139873595026816 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-10-29 15:41:08 139873595026816 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-10-29 15:41:08 139873595026816 [Note] InnoDB: Using Linux native AIO
2019-10-29 15:41:08 139873595026816 [Note] InnoDB: Using generic crc32 instructions
2019-10-29 15:41:08 139873595026816 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-10-29 15:41:08 139873595026816 [Note] InnoDB: Completed initialization of buffer pool
2019-10-29 15:41:08 139873595026816 [Note] InnoDB: Highest supported file format is Barracuda.
2019-10-29 15:41:08 139873595026816 [Note] InnoDB: The log sequence number 70583645 in ibdata file do not match the log sequence number 1402269071 in the ib_logfiles!
2019-10-29 15:41:09 139873595026816 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2019-10-29 15:41:10 139873595026816 [Note] InnoDB: 128 rollback segment(s) are active.
2019-10-29 15:41:10 139873595026816 [Note] InnoDB: Waiting for purge to start
2019-10-29 15:41:10 139873595026816 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.42-84.2 started; log sequence number 1402269071
2019-10-29 15:41:10 139872933246720 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-10-29 15:41:10 139873595026816 [Note] Plugin 'FEEDBACK' is disabled.
2019-10-29 15:41:10 139873595026816 [Note] Recovering after a crash using tc.log
2019-10-29 15:41:10 139873595026816 [Note] Starting crash recovery...
2019-10-29 15:41:10 139873595026816 [Note] Crash recovery finished.
2019-10-29 15:41:10 139873595026816 [Note] Server socket created on IP: '127.0.0.1'.
2019-10-29 15:41:11 139873595026816 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.1.38-MariaDB-0+deb9u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Debian 9.8
2019-10-29 15:42:57 139873023465216 [ERROR] mysqld: Out of memory (Needed 2984 bytes)
2019-10-29 15:43:08 7f36bbbf57002019-10-29 15:43:08 7f36b6ffa7002019-10-29 15:43:08 7f36c2dbd700  InnoDB: Assertion failure in thread 139873054840576 in file ut0mem.cc line 105
InnoDB: Failing assertion: ret || !assert_on_error
2019-10-29 15:43:11 7f36bb9cf700InnoDB: 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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2019-10-29 15:43:11 139873022031616 [ERROR] mysqld: Out of memory (Needed 1888 bytes)
2019-10-29 15:43:11 139873022236416 [ERROR] mysqld: Out of memory (Needed 1888 bytes)
191029 15:43:31 [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.

  InnoDB: Assertion failure in thread 139873174148864 in file ha_innodb.cc line 22034
InnoDB: Failing assertion: ret != -1
  InnoDB: Assertion failure in thread 139873052587776 in file ha_innodb.cc line 22034
InnoDB: Failing assertion: ret != -1
  InnoDB: Assertion failure in thread 139872975169280 in file ha_innodb.cc line 22034
InnoDB: Failing assertion: ret != -1
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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
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: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2019-10-29 16:02:46 140069457571200 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2019-10-29 16:02:46 140069457571200 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-10-29 16:02:46 140069457571200 [Note] InnoDB: The InnoDB memory heap is disabled
2019-10-29 16:02:46 140069457571200 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-10-29 16:02:46 140069457571200 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-10-29 16:02:46 140069457571200 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-10-29 16:02:46 140069457571200 [Note] InnoDB: Using Linux native AIO
2019-10-29 16:02:46 140069457571200 [Note] InnoDB: Using generic crc32 instructions
2019-10-29 16:02:46 140069457571200 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-10-29 16:02:46 140069457571200 [Note] InnoDB: Completed initialization of buffer pool
2019-10-29 16:02:46 140069457571200 [Note] InnoDB: Highest supported file format is Barracuda.
2019-10-29 16:02:46 140069457571200 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1402310699
2019-10-29 16:02:46 140069457571200 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2019-10-29 16:02:47 140069457571200 [Note] InnoDB: Starting final batch to recover 1 pages from redo log
2019-10-29 16:02:48 140069457571200 [Note] InnoDB: 128 rollback segment(s) are active.
2019-10-29 16:02:48 140069457571200 [Note] InnoDB: Waiting for purge to start
2019-10-29 16:02:48 140069457571200 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.42-84.2 started; log sequence number 1402312814
2019-10-29 16:02:49 140068794660608 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-10-29 16:02:49 140069457571200 [Note] Plugin 'FEEDBACK' is disabled.
2019-10-29 16:02:49 140069457571200 [Note] Recovering after a crash using tc.log
2019-10-29 16:02:49 140069457571200 [Note] Starting crash recovery...
2019-10-29 16:02:49 140069457571200 [Note] Crash recovery finished.
2019-10-29 16:02:49 140069457571200 [Note] Server socket created on IP: '127.0.0.1'.
2019-10-29 16:02:49 140069457571200 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.1.38-MariaDB-0+deb9u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Debian 9.8