190616 8:16:39 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190616 8:16:39 [Note] Plugin 'FEDERATED' is disabled.
190616 8:16:39 InnoDB: The InnoDB memory heap is disabled
190616 8:16:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190616 8:16:39 InnoDB: Compressed tables use zlib 1.2.8
190616 8:16:39 InnoDB: Using Linux native AIO
190616 8:16:39 InnoDB: Initializing buffer pool, size = 32.0M
190616 8:16:39 InnoDB: Completed initialization of buffer pool
190616 8:16:39 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
190616 8:16:39 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
190616 8:16:40 InnoDB: Waiting for the background threads to start
190616 8:16:41 InnoDB: 5.5.60 started; log sequence number 1595916
190616 8:16:41 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
190616 8:16:41 [Note] - '0.0.0.0' resolves to '0.0.0.0';
190616 8:16:41 [Note] Server socket created on IP: '0.0.0.0'.
190616 8:16:41 [ERROR] /usr/sbin/mysqld: Table './mysql/user' is marked as crashed and should be repaired
190616 8:16:41 [Warning] Checking table: './mysql/user'
190616 8:16:41 [ERROR] 1 client is using or hasn't closed the table properly
190616 8:16:41 [Note] Event Scheduler: Loaded 0 events
190616 8:16:41 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.60-0+deb8u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
190617 8:01:18 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 8:01:18 [Note] Plugin 'FEDERATED' is disabled.
190617 8:01:18 InnoDB: The InnoDB memory heap is disabled
190617 8:01:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 8:01:18 InnoDB: Compressed tables use zlib 1.2.8
190617 8:01:18 InnoDB: Using Linux native AIO
190617 8:01:18 InnoDB: Initializing buffer pool, size = 32.0M
190617 8:01:18 InnoDB: Completed initialization of buffer pool
190617 8:01:18 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
190617 8:01:18 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
190617 8:01:18 InnoDB: Waiting for the background threads to start
190617 8:01:19 InnoDB: 5.5.60 started; log sequence number 11718829
190617 8:01:19 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
190617 8:01:19 [Note] - '0.0.0.0' resolves to '0.0.0.0';
190617 8:01:19 [Note] Server socket created on IP: '0.0.0.0'.
190617 8:01:19 [ERROR] /usr/sbin/mysqld: Table './mysql/user' is marked as crashed and should be repaired
190617 8:01:19 [Warning] Checking table: './mysql/user'
190617 8:01:19 [ERROR] 1 client is using or hasn't closed the table properly
190617 8:01:19 [Note] Event Scheduler: Loaded 0 events
190617 8:01:19 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.60-0+deb8u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
190617 15:13:31 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 15:13:31 [Note] Plugin 'FEDERATED' is disabled.
190617 15:13:31 InnoDB: The InnoDB memory heap is disabled
190617 15:13:31 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 15:13:31 InnoDB: Compressed tables use zlib 1.2.8
190617 15:13:31 InnoDB: Using Linux native AIO
190617 15:13:31 InnoDB: Initializing buffer pool, size = 32.0M
190617 15:13:31 InnoDB: Completed initialization of buffer pool
190617 15:13:31 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
190617 15:13:31 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Warning: database page corruption or a failed
InnoDB: file read of space 0 page 582.
InnoDB: Trying to recover it from the doublewrite buffer.
InnoDB: Recovered the page from the doublewrite buffer.
InnoDB: Warning: database page corruption or a failed
InnoDB: file read of space 0 page 246.
InnoDB: Trying to recover it from the doublewrite buffer.
InnoDB: Recovered the page from the doublewrite buffer.
190617 15:13:31 InnoDB: Error: page 5 log sequence number 25668035
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 50 log sequence number 25665293
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 744 log sequence number 25623015
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 58 log sequence number 25677284
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 193 log sequence number 25623477
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 782 log sequence number 25623477
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 664 log sequence number 25667815
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 206 log sequence number 25668025
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 219 log sequence number 25623725
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 222 log sequence number 25669039
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 750 log sequence number 25669039
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 233 log sequence number 25623928
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 234 log sequence number 25633391
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 799 log sequence number 25633391
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 235 log sequence number 25642086
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 712 log sequence number 25642724
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 244 log sequence number 25643034
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 655 log sequence number 25643034
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 798 log sequence number 25660600
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 789 log sequence number 25671991
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 787 log sequence number 25660849
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 725 log sequence number 25673611
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 652 log sequence number 25663371
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 773 log sequence number 25663591
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 572 log sequence number 25676133
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Error: page 0 log sequence number 25624712
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:31 InnoDB: Waiting for the background threads to start
190617 15:13:32 InnoDB: 5.5.60 started; log sequence number 25620509
190617 15:13:32 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
190617 15:13:32 [Note] - '0.0.0.0' resolves to '0.0.0.0';
190617 15:13:32 [Note] Server socket created on IP: '0.0.0.0'.
190617 15:13:32 InnoDB: Error: page 580 log sequence number 25665197
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:32 InnoDB: Error: page 753 log sequence number 25677386
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:32 [Note] Event Scheduler: Loaded 0 events
190617 15:13:32 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.60-0+deb8u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
190617 15:13:38 InnoDB: Error: page 603 log sequence number 25672493
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:38 InnoDB: Error: page 601 log sequence number 25676244
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:13:38 InnoDB: Error: page 608 log sequence number 25677188
InnoDB: is in the future! Current system log sequence number 25620509.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
190617 15:14:05 InnoDB: Assertion failure in thread 140352420644608 in file fut0lst.ic line 83
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:14:05 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.
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.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=4
max_threads=151
thread_count=3
connection_count=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346701 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x55650e5eadc0
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 = 7fa6582cfed0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0x55650d321f33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x55650d20dbc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7fa65ade7890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fa6597dd067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fa6597de448]
/usr/sbin/mysqld(+0x5feb5d)[0x55650d437b5d]
/usr/sbin/mysqld(+0x5812a1)[0x55650d3ba2a1]
/usr/sbin/mysqld(+0x596a7a)[0x55650d3cfa7a]
/usr/sbin/mysqld(+0x58e9e4)[0x55650d3c79e4]
/usr/sbin/mysqld(+0x58fc90)[0x55650d3c8c90]
/usr/sbin/mysqld(+0x590f99)[0x55650d3c9f99]
/usr/sbin/mysqld(+0x544fb0)[0x55650d37dfb0]
/usr/sbin/mysqld(_Z19ha_commit_one_phaseP3THDb+0x91)[0x55650d2103f1]
/usr/sbin/mysqld(_Z15ha_commit_transP3THDb+0x280)[0x55650d210a80]
/usr/sbin/mysqld(_Z17trans_commit_stmtP3THD+0x1a)[0x55650d1c9d0a]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x454)[0x55650d124224]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x160)[0x55650d12adc0]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1b4f)[0x55650d12d0af]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x195)[0x55650d1bd615]
/usr/sbin/mysqld(handle_one_connection+0x41)[0x55650d1bd671]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7fa65ade0064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fa65989062d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fa634004b60): is an invalid pointer
Connection ID (thread ID): 10
Status: NOT_KILLED

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.
190617 15:14:05 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 15:14:05 [Note] Plugin 'FEDERATED' is disabled.
190617 15:14:05 InnoDB: The InnoDB memory heap is disabled
190617 15:14:05 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 15:14:05 InnoDB: Compressed tables use zlib 1.2.8
190617 15:14:05 InnoDB: Using Linux native AIO
190617 15:14:05 InnoDB: Initializing buffer pool, size = 32.0M
190617 15:14:05 InnoDB: Completed initialization of buffer pool
190617 15:14:05 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 15:14:05 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 15:14:06 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 190617 15:14:06 InnoDB: Assertion failure in thread 139976853595904 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:14:06 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.
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.

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 = 346701 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+0x33)[0x55641d7b9f33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x55641d6a5bc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f4ef3ddc890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f4ef27d2067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f4ef27d3448]
/usr/sbin/mysqld(+0x6455f6)[0x55641d9165f6]
94 95 96 97 98 99 /usr/sbin/mysqld(+0x635abe)[0x55641d906abe]
/usr/sbin/mysqld(+0x620c58)[0x55641d8f1c58]
/usr/sbin/mysqld(+0x62221d)[0x55641d8f321d]
/usr/sbin/mysqld(+0x5bfcc8)[0x55641d890cc8]
/usr/sbin/mysqld(+0x5ef889)[0x55641d8c0889]
/usr/sbin/mysqld(+0x577c88)[0x55641d848c88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f4ef3dd5064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f4ef288562d]
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.
190617 15:16:14 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 15:16:14 [Note] Plugin 'FEDERATED' is disabled.
190617 15:16:14 InnoDB: The InnoDB memory heap is disabled
190617 15:16:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 15:16:14 InnoDB: Compressed tables use zlib 1.2.8
190617 15:16:14 InnoDB: Using Linux native AIO
190617 15:16:14 InnoDB: Initializing buffer pool, size = 32.0M
190617 15:16:14 InnoDB: Completed initialization of buffer pool
190617 15:16:14 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 15:16:14 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 15:16:14 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 190617 15:16:15 InnoDB: Assertion failure in thread 140030063019776 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:16: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.
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.

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 = 346701 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+0x33)[0x556c5085ef33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x556c5074abc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f5b572de890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f5b55cd4067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f5b55cd5448]
/usr/sbin/mysqld(+0x6455f6)[0x556c509bb5f6]
/usr/sbin/mysqld(+0x635abe)[0x556c509ababe]
/usr/sbin/mysqld(+0x620c58)[0x556c50996c58]
/usr/sbin/mysqld(+0x62221d)[0x556c5099821d]
/usr/sbin/mysqld(+0x5bfcc8)[0x556c50935cc8]
/usr/sbin/mysqld(+0x5ef889)[0x556c50965889]
/usr/sbin/mysqld(+0x577c88)[0x556c508edc88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f5b572d7064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f5b55d8762d]
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.
190617 15:24:04 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 15:24:04 [Note] Plugin 'FEDERATED' is disabled.
190617 15:24:04 InnoDB: The InnoDB memory heap is disabled
190617 15:24:04 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 15:24:04 InnoDB: Compressed tables use zlib 1.2.8
190617 15:24:04 InnoDB: Using Linux native AIO
190617 15:24:04 InnoDB: Initializing buffer pool, size = 32.0M
190617 15:24:04 InnoDB: Completed initialization of buffer pool
190617 15:24:04 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 15:24:04 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 15:24:05 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 190617 15:24:05 InnoDB: Assertion failure in thread 139887075636992 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:24:05 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.
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.

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 = 346701 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...
94 95 96 97 stack_bottom = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0x558a74566f33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x558a74452bc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f3a0c78a890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f3a0b180067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f3a0b181448]
/usr/sbin/mysqld(+0x6455f6)[0x558a746c35f6]
/usr/sbin/mysqld(+0x635abe)[0x558a746b3abe]
/usr/sbin/mysqld(+0x620c58)[0x558a7469ec58]
98 99 /usr/sbin/mysqld(+0x62221d)[0x558a746a021d]
/usr/sbin/mysqld(+0x5bfcc8)[0x558a7463dcc8]
/usr/sbin/mysqld(+0x5ef889)[0x558a7466d889]
/usr/sbin/mysqld(+0x577c88)[0x558a745f5c88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f3a0c783064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f3a0b23362d]
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.
190617 15:57:22 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 15:57:22 [Note] Plugin 'FEDERATED' is disabled.
190617 15:57:22 InnoDB: The InnoDB memory heap is disabled
190617 15:57:22 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 15:57:22 InnoDB: Compressed tables use zlib 1.2.8
190617 15:57:22 InnoDB: Using Linux native AIO
190617 15:57:22 InnoDB: Initializing buffer pool, size = 32.0M
190617 15:57:22 InnoDB: Completed initialization of buffer pool
190617 15:57:22 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 15:57:22 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 15:57:22 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 190617 15:57:22 InnoDB: Assertion failure in thread 139771986994944 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:57:22 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.
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.

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 = 346701 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+0x33)[0x561580436f33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x561580322bc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f1f40e70890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f1f3f866067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f1f3f867448]
/usr/sbin/mysqld(+0x6455f6)[0x5615805935f6]
94 95 96 97 98 99 /usr/sbin/mysqld(+0x635abe)[0x561580583abe]
/usr/sbin/mysqld(+0x620c58)[0x56158056ec58]
/usr/sbin/mysqld(+0x62221d)[0x56158057021d]
/usr/sbin/mysqld(+0x5bfcc8)[0x56158050dcc8]
/usr/sbin/mysqld(+0x5ef889)[0x56158053d889]
/usr/sbin/mysqld(+0x577c88)[0x5615804c5c88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f1f40e69064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f1f3f91962d]
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.
190617 15:59:16 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 15:59:16 [Note] Plugin 'FEDERATED' is disabled.
190617 15:59:16 InnoDB: The InnoDB memory heap is disabled
190617 15:59:16 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 15:59:16 InnoDB: Compressed tables use zlib 1.2.8
190617 15:59:16 InnoDB: Using Linux native AIO
190617 15:59:16 InnoDB: Initializing buffer pool, size = 32.0M
190617 15:59:16 InnoDB: Completed initialization of buffer pool
190617 15:59:16 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 15:59:16 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 15:59:16 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 190617 15:59:16 InnoDB: Assertion failure in thread 140429178001152 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:59: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.
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.

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 = 346701 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+0x33)[0x55d65f991f33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x55d65f87dbc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7fb84454c890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fb842f42067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fb842f43448]
/usr/sbin/mysqld(+0x6455f6)[0x55d65faee5f6]
/usr/sbin/mysqld(+0x635abe)[0x55d65fadeabe]
94 95 96 97 98 99 /usr/sbin/mysqld(+0x620c58)[0x55d65fac9c58]
/usr/sbin/mysqld(+0x62221d)[0x55d65facb21d]
/usr/sbin/mysqld(+0x5bfcc8)[0x55d65fa68cc8]
/usr/sbin/mysqld(+0x5ef889)[0x55d65fa98889]
/usr/sbin/mysqld(+0x577c88)[0x55d65fa20c88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7fb844545064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fb842ff562d]
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.
190617 16:05:12 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 16:05:12 [Note] Plugin 'FEDERATED' is disabled.
190617 16:05:12 InnoDB: The InnoDB memory heap is disabled
190617 16:05:12 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 16:05:12 InnoDB: Compressed tables use zlib 1.2.8
190617 16:05:12 InnoDB: Using Linux native AIO
190617 16:05:12 InnoDB: Initializing buffer pool, size = 32.0M
190617 16:05:12 InnoDB: Completed initialization of buffer pool
190617 16:05:12 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 16:05:12 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 16:05:12 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 190617 16:05:12 InnoDB: Assertion failure in thread 139807434196736 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:05:12 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.
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.

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 = 346701 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+0x33)[0x55ede3007f33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x55ede2ef3bc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f2781b7a890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f2780570067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f2780571448]
/usr/sbin/mysqld(+0x6455f6)[0x55ede31645f6]
/usr/sbin/mysqld(+0x635abe)[0x55ede3154abe]
/usr/sbin/mysqld(+0x620c58)[0x55ede313fc58]
/usr/sbin/mysqld(+0x62221d)[0x55ede314121d]
/usr/sbin/mysqld(+0x5bfcc8)[0x55ede30decc8]
/usr/sbin/mysqld(+0x5ef889)[0x55ede310e889]
/usr/sbin/mysqld(+0x577c88)[0x55ede3096c88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f2781b73064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f278062362d]
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.
190617 16:12:28 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 16:12:28 [Note] Plugin 'FEDERATED' is disabled.
190617 16:12:28 InnoDB: The InnoDB memory heap is disabled
190617 16:12:28 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 16:12:28 InnoDB: Compressed tables use zlib 1.2.8
190617 16:12:28 InnoDB: Using Linux native AIO
190617 16:12:28 InnoDB: Initializing buffer pool, size = 32.0M
190617 16:12:28 InnoDB: Completed initialization of buffer pool
190617 16:12:28 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 16:12:28 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 16:12:28 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 190617 16:12:28 InnoDB: Assertion failure in thread 140390607165184 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:12:28 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.
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.

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 = 346701 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...
94 95 96 97 98 99 stack_bottom = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0x5563bba9ef33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x5563bb98abc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7faf494a5890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7faf47e9b067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7faf47e9c448]
/usr/sbin/mysqld(+0x6455f6)[0x5563bbbfb5f6]
/usr/sbin/mysqld(+0x635abe)[0x5563bbbebabe]
/usr/sbin/mysqld(+0x620c58)[0x5563bbbd6c58]
/usr/sbin/mysqld(+0x62221d)[0x5563bbbd821d]
/usr/sbin/mysqld(+0x5bfcc8)[0x5563bbb75cc8]
/usr/sbin/mysqld(+0x5ef889)[0x5563bbba5889]
/usr/sbin/mysqld(+0x577c88)[0x5563bbb2dc88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7faf4949e064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7faf47f4e62d]
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.
190617 16:18:13 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 16:18:13 [Note] Plugin 'FEDERATED' is disabled.
190617 16:18:13 InnoDB: The InnoDB memory heap is disabled
190617 16:18:13 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 16:18:13 InnoDB: Compressed tables use zlib 1.2.8
190617 16:18:13 InnoDB: Using Linux native AIO
190617 16:18:13 InnoDB: Initializing buffer pool, size = 32.0M
190617 16:18:13 InnoDB: Completed initialization of buffer pool
190617 16:18:13 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 16:18:13 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 16:18:13 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 190617 16:18:13 InnoDB: Assertion failure in thread 140099847362304 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:18: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.
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.

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 = 346701 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...
94 95 96 97 98 stack_bottom = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0x55bc74ab5f33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x55bc749a1bc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f6b96fd0890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f6b959c6067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f6b959c7448]
/usr/sbin/mysqld(+0x6455f6)[0x55bc74c125f6]
/usr/sbin/mysqld(+0x635abe)[0x55bc74c02abe]
99 /usr/sbin/mysqld(+0x620c58)[0x55bc74bedc58]
/usr/sbin/mysqld(+0x62221d)[0x55bc74bef21d]
/usr/sbin/mysqld(+0x5bfcc8)[0x55bc74b8ccc8]
/usr/sbin/mysqld(+0x5ef889)[0x55bc74bbc889]
/usr/sbin/mysqld(+0x577c88)[0x55bc74b44c88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f6b96fc9064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f6b95a7962d]
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.
190617 16:19:26 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 16:19:26 [Note] Plugin 'FEDERATED' is disabled.
190617 16:19:26 InnoDB: The InnoDB memory heap is disabled
190617 16:19:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 16:19:26 InnoDB: Compressed tables use zlib 1.2.8
190617 16:19:26 InnoDB: Using Linux native AIO
190617 16:19:26 InnoDB: Initializing buffer pool, size = 32.0M
190617 16:19:26 InnoDB: Completed initialization of buffer pool
190617 16:19:26 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 16:19:26 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 16:19:27 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 190617 16:19:27 InnoDB: Assertion failure in thread 140648009344768 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:19:27 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.
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.

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 = 346701 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+0x33)[0x55771bc34f33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x55771bb20bc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7feb37de2890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7feb367d8067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7feb367d9448]
/usr/sbin/mysqld(+0x6455f6)[0x55771bd915f6]
/usr/sbin/mysqld(+0x635abe)[0x55771bd81abe]
/usr/sbin/mysqld(+0x620c58)[0x55771bd6cc58]
/usr/sbin/mysqld(+0x62221d)[0x55771bd6e21d]
/usr/sbin/mysqld(+0x5bfcc8)[0x55771bd0bcc8]
/usr/sbin/mysqld(+0x5ef889)[0x55771bd3b889]
/usr/sbin/mysqld(+0x577c88)[0x55771bcc3c88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7feb37ddb064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7feb3688b62d]
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.
190617 16:33:04 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 16:33:04 [Note] Plugin 'FEDERATED' is disabled.
190617 16:33:04 InnoDB: The InnoDB memory heap is disabled
190617 16:33:04 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 16:33:04 InnoDB: Compressed tables use zlib 1.2.8
190617 16:33:04 InnoDB: Using Linux native AIO
190617 16:33:04 InnoDB: Initializing buffer pool, size = 32.0M
190617 16:33:04 InnoDB: Completed initialization of buffer pool
190617 16:33:04 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 16:33:04 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 16:33:04 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 190617 16:33:04 InnoDB: Assertion failure in thread 139629122885376 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:33:04 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.
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.

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 = 346701 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+0x33)[0x5572db4cdf33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x5572db3b9bc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7efdfd4b2890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7efdfbea8067]
94 95 96 97 98 99 /lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7efdfbea9448]
/usr/sbin/mysqld(+0x6455f6)[0x5572db62a5f6]
/usr/sbin/mysqld(+0x635abe)[0x5572db61aabe]
/usr/sbin/mysqld(+0x620c58)[0x5572db605c58]
/usr/sbin/mysqld(+0x62221d)[0x5572db60721d]
/usr/sbin/mysqld(+0x5bfcc8)[0x5572db5a4cc8]
/usr/sbin/mysqld(+0x5ef889)[0x5572db5d4889]
/usr/sbin/mysqld(+0x577c88)[0x5572db55cc88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7efdfd4ab064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7efdfbf5b62d]
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.
190617 16:34:26 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 16:34:26 [Note] Plugin 'FEDERATED' is disabled.
190617 16:34:26 InnoDB: The InnoDB memory heap is disabled
190617 16:34:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 16:34:26 InnoDB: Compressed tables use zlib 1.2.8
190617 16:34:26 InnoDB: Using Linux native AIO
190617 16:34:26 InnoDB: Initializing buffer pool, size = 32.0M
190617 16:34:26 InnoDB: Completed initialization of buffer pool
190617 16:34:26 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 16:34:26 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 16:34:26 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 190617 16:34:26 InnoDB: Assertion failure in thread 139884025255680 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:34:26 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.
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.

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 = 346701 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+0x33)[0x55ddaed25f33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x55ddaec11bc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f3956c3e890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f3955634067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f3955635448]
/usr/sbin/mysqld(+0x6455f6)[0x55ddaee825f6]
/usr/sbin/mysqld(+0x635abe)[0x55ddaee72abe]
/usr/sbin/mysqld(+0x620c58)[0x55ddaee5dc58]
/usr/sbin/mysqld(+0x62221d)[0x55ddaee5f21d]
/usr/sbin/mysqld(+0x5bfcc8)[0x55ddaedfccc8]
/usr/sbin/mysqld(+0x5ef889)[0x55ddaee2c889]
94 95 96 97 98 99 /usr/sbin/mysqld(+0x577c88)[0x55ddaedb4c88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f3956c37064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f39556e762d]
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.
190617 16:40:03 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 16:40:03 [Note] Plugin 'FEDERATED' is disabled.
190617 16:40:03 InnoDB: The InnoDB memory heap is disabled
190617 16:40:03 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 16:40:03 InnoDB: Compressed tables use zlib 1.2.8
190617 16:40:03 InnoDB: Using Linux native AIO
190617 16:40:03 InnoDB: Initializing buffer pool, size = 32.0M
190617 16:40:03 InnoDB: Completed initialization of buffer pool
190617 16:40:03 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 16:40:03 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 16:40:03 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 190617 16:40:03 InnoDB: Assertion failure in thread 140669433833216 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:40:03 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.
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.

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 = 346701 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+0x33)[0x55bf56d0ef33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x55bf56bfabc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7ff0351a9890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7ff033b9f067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7ff033ba0448]
/usr/sbin/mysqld(+0x6455f6)[0x55bf56e6b5f6]
/usr/sbin/mysqld(+0x635abe)[0x55bf56e5babe]
/usr/sbin/mysqld(+0x620c58)[0x55bf56e46c58]
/usr/sbin/mysqld(+0x62221d)[0x55bf56e4821d]
/usr/sbin/mysqld(+0x5bfcc8)[0x55bf56de5cc8]
/usr/sbin/mysqld(+0x5ef889)[0x55bf56e15889]
/usr/sbin/mysqld(+0x577c88)[0x55bf56d9dc88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7ff0351a2064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7ff033c5262d]
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.
190617 16:47:00 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 16:47:00 [Note] Plugin 'FEDERATED' is disabled.
190617 16:47:00 InnoDB: The InnoDB memory heap is disabled
190617 16:47:00 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 16:47:00 InnoDB: Compressed tables use zlib 1.2.8
190617 16:47:00 InnoDB: Using Linux native AIO
190617 16:47:00 InnoDB: Initializing buffer pool, size = 32.0M
190617 16:47:00 InnoDB: Completed initialization of buffer pool
190617 16:47:00 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 16:47:00 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 16:47:00 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 190617 16:47:00 InnoDB: Assertion failure in thread 140027076179712 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:47:00 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.
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.

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 = 346701 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+0x33)[0x5611cf858f33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x5611cf744bc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f5aa52f7890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f5aa3ced067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f5aa3cee448]
/usr/sbin/mysqld(+0x6455f6)[0x5611cf9b55f6]
/usr/sbin/mysqld(+0x635abe)[0x5611cf9a5abe]
94 95 96 97 98 99 /usr/sbin/mysqld(+0x620c58)[0x5611cf990c58]
/usr/sbin/mysqld(+0x62221d)[0x5611cf99221d]
/usr/sbin/mysqld(+0x5bfcc8)[0x5611cf92fcc8]
/usr/sbin/mysqld(+0x5ef889)[0x5611cf95f889]
/usr/sbin/mysqld(+0x577c88)[0x5611cf8e7c88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f5aa52f0064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f5aa3da062d]
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.
190617 16:50:01 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 16:50:01 [Note] Plugin 'FEDERATED' is disabled.
190617 16:50:01 InnoDB: The InnoDB memory heap is disabled
190617 16:50:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 16:50:01 InnoDB: Compressed tables use zlib 1.2.8
190617 16:50:01 InnoDB: Using Linux native AIO
190617 16:50:01 InnoDB: Initializing buffer pool, size = 32.0M
190617 16:50:01 InnoDB: Completed initialization of buffer pool
190617 16:50:01 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 16:50:01 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 16:50:01 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 190617 16:50:01 InnoDB: Assertion failure in thread 140169774798592 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:50:01 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.
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.

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 = 346701 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+0x33)[0x557d134bdf33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x557d133a9bc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f7bded56890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f7bdd74c067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f7bdd74d448]
/usr/sbin/mysqld(+0x6455f6)[0x557d1361a5f6]
/usr/sbin/mysqld(+0x635abe)[0x557d1360aabe]
/usr/sbin/mysqld(+0x620c58)[0x557d135f5c58]
94 95 96 97 98 99 /usr/sbin/mysqld(+0x62221d)[0x557d135f721d]
/usr/sbin/mysqld(+0x5bfcc8)[0x557d13594cc8]
/usr/sbin/mysqld(+0x5ef889)[0x557d135c4889]
/usr/sbin/mysqld(+0x577c88)[0x557d1354cc88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f7bded4f064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f7bdd7ff62d]
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.
190617 16:52:12 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 16:52:12 [Note] Plugin 'FEDERATED' is disabled.
190617 16:52:12 InnoDB: The InnoDB memory heap is disabled
190617 16:52:12 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 16:52:12 InnoDB: Compressed tables use zlib 1.2.8
190617 16:52:12 InnoDB: Using Linux native AIO
190617 16:52:12 InnoDB: Initializing buffer pool, size = 32.0M
190617 16:52:12 InnoDB: Completed initialization of buffer pool
190617 16:52:12 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 16:52:12 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 16:52:12 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 190617 16:52:12 InnoDB: Assertion failure in thread 139720446830336 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:52:12 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.
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.

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 = 346701 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+0x33)[0x5642100aaf33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x56420ff96bc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f13409ed890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f133f3e3067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f133f3e4448]
/usr/sbin/mysqld(+0x6455f6)[0x5642102075f6]
/usr/sbin/mysqld(+0x635abe)[0x5642101f7abe]
94 95 96 97 98 99 /usr/sbin/mysqld(+0x620c58)[0x5642101e2c58]
/usr/sbin/mysqld(+0x62221d)[0x5642101e421d]
/usr/sbin/mysqld(+0x5bfcc8)[0x564210181cc8]
/usr/sbin/mysqld(+0x5ef889)[0x5642101b1889]
/usr/sbin/mysqld(+0x577c88)[0x564210139c88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f13409e6064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f133f49662d]
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.
190617 16:55:29 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 16:55:29 [Note] Plugin 'FEDERATED' is disabled.
190617 16:55:29 InnoDB: The InnoDB memory heap is disabled
190617 16:55:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 16:55:29 InnoDB: Compressed tables use zlib 1.2.8
190617 16:55:29 InnoDB: Using Linux native AIO
190617 16:55:29 InnoDB: Initializing buffer pool, size = 32.0M
190617 16:55:29 InnoDB: Completed initialization of buffer pool
190617 16:55:29 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 16:55:29 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 16:55:29 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 190617 16:55:29 InnoDB: Assertion failure in thread 139821191513856 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:55:29 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.
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.

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 = 346701 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...
83 84 85 86 87 stack_bottom = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0x561eab4e7f33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x561eab3d3bc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f2ab5ba7890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f2ab459d067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f2ab459e448]
/usr/sbin/mysqld(+0x6455f6)[0x561eab6445f6]
/usr/sbin/mysqld(+0x635abe)[0x561eab634abe]
88 89 90 91 92 93 94 95 96 97 98 99 /usr/sbin/mysqld(+0x620c58)[0x561eab61fc58]
/usr/sbin/mysqld(+0x62221d)[0x561eab62121d]
/usr/sbin/mysqld(+0x5bfcc8)[0x561eab5becc8]
/usr/sbin/mysqld(+0x5ef889)[0x561eab5ee889]
/usr/sbin/mysqld(+0x577c88)[0x561eab576c88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f2ab5ba0064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f2ab465062d]
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.
190617 17:06:21 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 17:06:21 [Note] Plugin 'FEDERATED' is disabled.
190617 17:06:21 InnoDB: The InnoDB memory heap is disabled
190617 17:06:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 17:06:21 InnoDB: Compressed tables use zlib 1.2.8
190617 17:06:21 InnoDB: Using Linux native AIO
190617 17:06:21 InnoDB: Initializing buffer pool, size = 32.0M
190617 17:06:21 InnoDB: Completed initialization of buffer pool
190617 17:06:21 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 17:06:21 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 17:06:21 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 190617 17:06:21 InnoDB: Assertion failure in thread 139829801293568 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
17:06:21 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.
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.

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 = 346701 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+0x33)[0x55d39afadf33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x55d39ae99bc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f2cb7009890]
94 95 96 97 98 99 /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f2cb59ff067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f2cb5a00448]
/usr/sbin/mysqld(+0x6455f6)[0x55d39b10a5f6]
/usr/sbin/mysqld(+0x635abe)[0x55d39b0faabe]
/usr/sbin/mysqld(+0x620c58)[0x55d39b0e5c58]
/usr/sbin/mysqld(+0x62221d)[0x55d39b0e721d]
/usr/sbin/mysqld(+0x5bfcc8)[0x55d39b084cc8]
/usr/sbin/mysqld(+0x5ef889)[0x55d39b0b4889]
/usr/sbin/mysqld(+0x577c88)[0x55d39b03cc88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f2cb7002064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f2cb5ab262d]
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.
190617 17:07:46 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 17:07:46 [Note] Plugin 'FEDERATED' is disabled.
190617 17:07:46 InnoDB: The InnoDB memory heap is disabled
190617 17:07:46 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 17:07:46 InnoDB: Compressed tables use zlib 1.2.8
190617 17:07:46 InnoDB: Using Linux native AIO
190617 17:07:46 InnoDB: Initializing buffer pool, size = 32.0M
190617 17:07:46 InnoDB: Completed initialization of buffer pool
190617 17:07:46 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 17:07:46 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 17:07:46 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 190617 17:07:46 InnoDB: Assertion failure in thread 140457369822976 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
17:07:46 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.
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.

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 = 346701 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+0x33)[0x55b6ff9aef33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x55b6ff89abc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7fbed4b56890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7fbed354c067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fbed354d448]
/usr/sbin/mysqld(+0x6455f6)[0x55b6ffb0b5f6]
/usr/sbin/mysqld(+0x635abe)[0x55b6ffafbabe]
/usr/sbin/mysqld(+0x620c58)[0x55b6ffae6c58]
/usr/sbin/mysqld(+0x62221d)[0x55b6ffae821d]
/usr/sbin/mysqld(+0x5bfcc8)[0x55b6ffa85cc8]
/usr/sbin/mysqld(+0x5ef889)[0x55b6ffab5889]
94 95 96 97 98 99 /usr/sbin/mysqld(+0x577c88)[0x55b6ffa3dc88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7fbed4b4f064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fbed35ff62d]
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.
190617 17:08:22 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 17:08:22 [Note] Plugin 'FEDERATED' is disabled.
190617 17:08:22 InnoDB: The InnoDB memory heap is disabled
190617 17:08:22 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 17:08:22 InnoDB: Compressed tables use zlib 1.2.8
190617 17:08:22 InnoDB: Using Linux native AIO
190617 17:08:22 InnoDB: Initializing buffer pool, size = 32.0M
190617 17:08:22 InnoDB: Completed initialization of buffer pool
190617 17:08:22 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 17:08:22 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 17:08:22 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 190617 17:08:22 InnoDB: Assertion failure in thread 140071385855744 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
17:08:22 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.
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.

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 = 346701 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+0x33)[0x56456df81f33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x56456de6dbc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f64f63c0890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f64f4db6067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f64f4db7448]
/usr/sbin/mysqld(+0x6455f6)[0x56456e0de5f6]
/usr/sbin/mysqld(+0x635abe)[0x56456e0ceabe]
/usr/sbin/mysqld(+0x620c58)[0x56456e0b9c58]
/usr/sbin/mysqld(+0x62221d)[0x56456e0bb21d]
94 95 96 97 98 99 /usr/sbin/mysqld(+0x5bfcc8)[0x56456e058cc8]
/usr/sbin/mysqld(+0x5ef889)[0x56456e088889]
/usr/sbin/mysqld(+0x577c88)[0x56456e010c88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f64f63b9064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f64f4e6962d]
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.
190617 17:12:11 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 17:12:11 [Note] Plugin 'FEDERATED' is disabled.
190617 17:12:11 InnoDB: The InnoDB memory heap is disabled
190617 17:12:11 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 17:12:11 InnoDB: Compressed tables use zlib 1.2.8
190617 17:12:11 InnoDB: Using Linux native AIO
190617 17:12:11 InnoDB: Initializing buffer pool, size = 32.0M
190617 17:12:11 InnoDB: Completed initialization of buffer pool
190617 17:12:11 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 25620756
190617 17:12:11 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 25702726
190617 17:12:11 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 190617 17:12:11 InnoDB: Assertion failure in thread 139862634309376 in file rem0rec.c line 569
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
17:12:11 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.
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.

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 = 346701 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+0x33)[0x55dbd1ee7f33]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x55dbd1dd3bc4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f345c0b2890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f345aaa8067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f345aaa9448]
/usr/sbin/mysqld(+0x6455f6)[0x55dbd20445f6]
/usr/sbin/mysqld(+0x635abe)[0x55dbd2034abe]
/usr/sbin/mysqld(+0x620c58)[0x55dbd201fc58]
/usr/sbin/mysqld(+0x62221d)[0x55dbd202121d]
/usr/sbin/mysqld(+0x5bfcc8)[0x55dbd1fbecc8]
/usr/sbin/mysqld(+0x5ef889)[0x55dbd1fee889]
/usr/sbin/mysqld(+0x577c88)[0x55dbd1f76c88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f345c0ab064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f345ab5b62d]
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.
190617 18:23:11 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
190617 18:23:11 [Note] Plugin 'FEDERATED' is disabled.
190617 18:23:11 InnoDB: The InnoDB memory heap is disabled
190617 18:23:11 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190617 18:23:11 InnoDB: Compressed tables use zlib 1.2.8
190617 18:23:11 InnoDB: Using Linux native AIO
190617 18:23:11 InnoDB: Initializing buffer pool, size = 32.0M
190617 18:23:11 InnoDB: Completed initialization of buffer pool
190617 18:23:11 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
190617 18:23:11 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
190617 18:23:11 InnoDB: Waiting for the background threads to start
190617 18:23:12 InnoDB: 5.5.60 started; log sequence number 2398089
190617 18:23:12 InnoDB: !!! innodb_force_recovery is set to 1 !!!
190617 18:23:12 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
190617 18:23:12 [Note] - '0.0.0.0' resolves to '0.0.0.0';
190617 18:23:12 [Note] Server socket created on IP: '0.0.0.0'.
190617 18:23:12 [Note] Event Scheduler: Loaded 0 events
190617 18:23:12 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.60-0+deb8u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)