阿里云ECS 1核 1G記憶體，一鍵安裝包部署的web環境，
---------- mysql-5.5.40 ok ----------
---------- nginx-1.4.4 ok ----------
---------- php-5.5.7 ok ----------
---------- php extension ok ----------
---------- vsftpd-2.2.2 ok ----------
---------- phpwind-8.7 ok ----------
---------- phpmyadmin-4.1.8 ok
搭建的wordpress博客，mysql日志報錯如下（部分）：
Version: '5.5.40-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
InnoDB: Last MySQL binlog file position 0 62207, file name ./mysql-bin.000013
180418 19:51:34 InnoDB: Waiting for the background threads to start
180418 19:51:35 InnoDB: 5.5.40 started; log sequence number 6947378
180418 19:51:35 [Note] Recovering after a crash using mysql-bin
180418 19:51:35 [Note] Starting crash recovery...
180418 19:51:35 [Note] Crash recovery finished.
180418 19:51:35 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180418 19:51:35 [Note] - '0.0.0.0' resolves to '0.0.0.0';
180418 19:51:35 [Note] Server socket created on IP: '0.0.0.0'.
180418 19:51:35 [Note] Event Scheduler: Loaded 0 events
180418 19:51:35 [Note] /alidata/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.40-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
180418 20:22:20 mysqld_safe Number of processes running now: 0
180418 20:22:20 mysqld_safe mysqld restarted
180418 20:22:20 [Note] Plugin 'FEDERATED' is disabled.
180418 20:22:20 InnoDB: The InnoDB memory heap is disabled
180418 20:22:20 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180418 20:22:20 InnoDB: Compressed tables use zlib 1.2.3
180418 20:22:20 InnoDB: Using Linux native AIO
180418 20:22:20 InnoDB: Initializing buffer pool, size = 128.0M
180418 20:22:20 InnoDB: Completed initialization of buffer pool
180418 20:22:21 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!
180418 20:22: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: Last MySQL binlog file position 0 12181, file name ./mysql-bin.000014
180418 20:22:23 InnoDB: Waiting for the background threads to start
180418 20:22:24 InnoDB: 5.5.40 started; log sequence number 6962417
180418 20:22:24 [Note] Recovering after a crash using mysql-bin
180418 20:22:24 [Note] Starting crash recovery...
180418 20:22:24 [Note] Crash recovery finished.
180418 20:22:24 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180418 20:22:24 [Note] - '0.0.0.0' resolves to '0.0.0.0';
180418 20:22:24 [Note] Server socket created on IP: '0.0.0.0'.
180418 20:22:24 [Note] Event Scheduler: Loaded 0 events
180418 20:22:24 [Note] /alidata/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.40-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
180418 20:49:50 mysqld_safe Number of processes running now: 0
180418 20:49:50 mysqld_safe mysqld restarted
180418 20:49:50 [Note] Plugin 'FEDERATED' is disabled.
180418 20:49:50 InnoDB: The InnoDB memory heap is disabled
180418 20:49:50 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180418 20:49:50 InnoDB: Compressed tables use zlib 1.2.3
180418 20:49:50 InnoDB: Using Linux native AIO
180418 20:49:51 InnoDB: Initializing buffer pool, size = 128.0M
180418 20:49:51 InnoDB: Completed initialization of buffer pool
180418 20:49:51 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 6971888
180418 20:49:52 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 6972296
180418 20:49:54 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 6526, file name ./mysql-bin.000015
180418 20:49:54 InnoDB: Waiting for the background threads to start
180418 20:49:55 InnoDB: 5.5.40 started; log sequence number 6972296
180418 20:49:55 [Note] Recovering after a crash using mysql-bin
180418 20:49:55 [Note] Starting crash recovery...
180418 20:49:55 [Note] Crash recovery finished.
180418 20:49:55 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180418 20:49:55 [Note] - '0.0.0.0' resolves to '0.0.0.0';
180418 20:49:55 [Note] Server socket created on IP: '0.0.0.0'.
180418 20:49:56 [Note] Event Scheduler: Loaded 0 events
180418 20:49:56 [Note] /alidata/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.40-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
180419 1:19:42 [Warning] IP address '106.15.52.246' could not be resolved: Name or service not known
180419 1:57:11 [Warning] IP address '120.78.231.236' could not be resolved: Name or service not known
180419 3:19:37 [Warning] IP address '106.14.104.214' could not be resolved: Name or service not known
180419 7:18:25 [Warning] IP address '47.97.63.119' could not be resolved: Name or service not known
180419 20:40:50 [Warning] IP address '122.114.240.248' could not be resolved: Name or service not known
180420 0:32:46 [Warning] IP address '39.107.14.208' could not be resolved: Name or service not known
180421 1:54:31 [Warning] IP address '47.100.130.114' could not be resolved: Name or service not known
180421 4:42:30 [Warning] IP address '145.249.106.141' could not be resolved: Name or service not known
180422 0:22:39 [Warning] IP address '118.31.244.58' could not be resolved: Name or service not known
180422 5:28:17 [Warning] IP address '106.15.76.92' could not be resolved: Name or service not known
180423 2:14:54 [Warning] IP address '47.100.64.86' could not be resolved: Name or service not known
180424 0:12:06 [Warning] IP address '47.94.52.138' could not be resolved: Name or service not known
180424 10:27:12 [Warning] IP address '61.153.237.123' could not be resolved: Name or service not known
180424 10:56:31 mysqld_safe Number of processes running now: 0
180424 10:56:31 mysqld_safe mysqld restarted
180424 10:56:32 [Note] Plugin 'FEDERATED' is disabled.
180424 10:56:32 InnoDB: The InnoDB memory heap is disabled
180424 10:56:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180424 10:56:32 InnoDB: Compressed tables use zlib 1.2.3
180424 10:56:32 InnoDB: Using Linux native AIO
180424 10:56:32 InnoDB: Initializing buffer pool, size = 128.0M
180424 10:56:32 InnoDB: Completed initialization of buffer pool
180424 10:56:33 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!
180424 10:56:34 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: Last MySQL binlog file position 0 1149774, file name ./mysql-bin.000016
180424 10:56:35 InnoDB: Waiting for the background threads to start
180424 10:56:36 InnoDB: 5.5.40 started; log sequence number 8842589
180424 10:56:36 [Note] Recovering after a crash using mysql-bin
180424 10:56:36 [Note] Starting crash recovery...
180424 10:56:36 [Note] Crash recovery finished.
180424 10:56:36 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
180424 10:56:36 [Note] - '0.0.0.0' resolves to '0.0.0.0';
180424 10:56:36 [Note] Server socket created on IP: '0.0.0.0'.
180424 10:56:36 [Note] Event Scheduler: Loaded 0 events
180424 10:56:36 [Note] /alidata/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.40-log' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
uj5u.com熱心網友回復：
應該是OOM被系統強殺了轉載請註明出處，本文鏈接：https://www.uj5u.com/shujuku/90939.html
標籤：MySQL