Home > database >  Ali cloud MysQl often crash recovery link database errors from time to time
Ali cloud MysQl often crash recovery link database errors from time to time

Time:09-28

Ali cloud ECS nuclear 1 gb of memory, a key installation package deployed web environment,
-- -- -- -- -- -- -- -- -- -- mysql - 5.5.40 ok -- -- -- -- -- -- -- -- -- --
-- -- -- -- -- -- -- -- -- -- nginx 1.4.4 ok -- -- -- -- -- -- -- -- -- --
-- -- -- -- -- -- -- -- -- -- - PHP 5.5.7 ok -- -- -- -- -- -- -- -- -- --
-- -- -- -- -- -- -- -- -- -- the PHP extension ok -- -- -- -- -- -- -- -- -- --
-- -- -- -- -- -- -- -- -- -- VSFTPD - 2.2.2 ok -- -- -- -- -- -- -- -- -- --
-- -- -- -- -- -- -- -- -- -- phpwind - 8.7 ok -- -- -- -- -- -- -- -- -- --
-- -- -- -- -- -- -- -- -- -- phpmyadmin 4.1.8 ok

Structures, wordpress blog, the mysql error log (part) as follows:

Version: '5.5.40 - log' socket: '/TMP/mysql. The sock' port: 3306 mysql Community Server (GPL)

InnoDB: Last MySQL binlog file position 0, 62207, the file name. 000013
/MySQL - bin.180418 19:51:34 InnoDB: Waiting for the background threads to start
180418 19:51:35 InnoDB: 5.5.40 started; The 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: the Loaded 0 events
180418 19:51:35 [Note]/alidata/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.40 - log' socket: '/TMP/mysql. The sock' port: 3306 mysql Community Server (GPL)
180418 20:22:20 mysqld_safe Number of the processes running now: 0
180418 20:22:20 mysqld_safe mysqld restarted
180418 20:22:20 [Note] the Plugin 'FEDERATED is disabled.
180418 20:22:20 InnoDB: The InnoDB heap memory 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.0 M
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 The
InnoDB: the log sequence number in the ib_logfiles!
180418 20:22:21 InnoDB: the Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading in 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, the file name. 000014
/MySQL - bin.180418 20:22:23 InnoDB: Waiting for the background threads to start
180418 20:22:24 InnoDB: 5.5.40 started; The 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: the Loaded 0 events
180418 20:22:24 [Note]/alidata/server/mysql/bin/mysqld: ready for connections.
Version: '5.5.40 - log' socket: '/TMP/mysql. The sock' port: 3306 mysql Community Server (GPL)
180418 20:49:50 mysqld_safe Number of the processes running now: 0
180418 20:49:50 mysqld_safe mysqld restarted
180418 20:49:50 [Note] the Plugin 'FEDERATED is disabled.
180418 20:49:50 InnoDB: The InnoDB heap memory 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.0 M
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: the Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading in tablespace information from the. Ibd files...
InnoDB: Restoring possible half - written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned one 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, the file name. 000015
/MySQL - bin.180418 20:49:54 InnoDB: Waiting for the background threads to start
180418 20:49:55 InnoDB: 5.5.40 started; The 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
nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull
  • Related