Description:
2019-12-13T09:24:25.636845Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2 3 42019-12-13T09:24:25.700719Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-12-13T09:24:25.701937Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-12-13T09:24:25.701971Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-12-13T09:24:25.705044Z 0 [Note] InnoDB: Waiting for purge to start
5 62019-12-13T09:24:25.755298Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 5943ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
2019-12-13T09:24:25.755298Z 0 [Note] InnoDB: 5.7.26 started; log sequence number 253661009495
2019-12-13T09:24:25.755824Z 0 [Note] InnoDB: Loading buffer pool(s) from /app/mysql/mysqldata/ib_buffer_pool
2019-12-13T09:24:25.767151Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
2019-12-13T09:24:25.767205Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
2019-12-13T09:24:25.767336Z 0 [Note] IPv6 is available.
2019-12-13T09:24:25.767409Z 0 [Note] - '::' resolves to '::';
2019-12-13T09:24:25.767451Z 0 [Note] Server socket created on IP: '::'.
72019-12-13T09:24:25.770225Z 0 [Warning] Insecure configuration for --pid-file: Location '/app/mysql/mysqldata' in the path is accessible to all OS users. Consider choosing a different directory.
2019-12-13T09:24:25.785335Z 0 [Note] Event Scheduler: Loaded 3 events
2019-12-13T09:24:25.785582Z 1 [Note] Event Scheduler: scheduler thread started with id 1
2019-12-13T09:24:25.786166Z 0 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.7.26' socket: '/app/mysql/mysqldata/mysql.sock' port: 3306 MySQL Community Server (GPL)
8 9 10 11 12 13 142019-12-13 17:24:25 0x7fe27d646700 InnoDB: Assertion failure in thread 140610743068416 in file fsp0fsp.cc line 2112
InnoDB: Failing assertion: frag_n_used > 0
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
09:24:25 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
key_buffer_size=8388608
read_buffer_size=2097152
max_used_connections=0
max_threads=2000
thread_count=1
How to repeat:
Please help us to find out the problem and provide us a solution to this problem is the best, and if you have any questions please contact me by e-mail:wutb@19pay.com.cn.
