Home > database >  MYSQL automatically restart, looking for solutions
MYSQL automatically restart, looking for solutions

Time:10-04

170922 09:40:01 mysqld_safe mysqld restarted
The 2017-09-22 09:40:01 0 [Note]/usr/local/mysql/bin/mysqld (mysqld 5.6.29 - log) starting as the process of 2258...
The 2258 09:40:01 2017-09-22 [Note] the Plugin 'FEDERATED is disabled.
The 2017-09-22 09:40:01 2258 [Note] InnoDB: Using atomics to ref count buffer pool pages
The 2017-09-22 09:40:01 2258 InnoDB [Note] : The InnoDB heap memory is disabled
The 2017-09-22 09:40:01 2258 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-09-22 09:40:01 2258 InnoDB [Note] : the Memory barrier is not 2
The 2017-09-22 09:40:01 2258 [Note] InnoDB: Compressed tables use zlib 1.2.3
The 2017-09-22 09:40:01 2258 [Note] InnoDB: Using CPU crc32 instructions
The 2017-09-22 09:40:01 2258 [Note] InnoDB: Initializing buffer pool, size=1.0 G
The 2017-09-22 09:40:02 InnoDB [Note] : 2258 Completed initialization of buffer pool
The 2017-09-22 09:40:02 2258 [Note] InnoDB: Highest supported file format is Barracuda.
The 2258 09:40:02 2017-09-22 [Note] InnoDB: The log sequence Numbers 962097288 and 962097288 in ibdata files do not match The log sequence number 962097308 in The ib_logfiles!
The 2258 09:40:02 2017-09-22 [Note] InnoDB: the Database was not shutdown normally!
The 2017-09-22 09:40:02 2258 [Note] InnoDB: Starting crash recovery.
The 2017-09-22 09:40:02 2258 [Note] InnoDB: Reading in tablespace information from the. Ibd files...
The 2017-09-22 09:40:02 2258 [Note] InnoDB: Restoring possible half - written data pages
The 2017-09-22 09:40:02 2258 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0, 1122, the file name MySQL - bin. 001029
09:40:02 InnoDB [Note] : 2258 2017-09-22 128 the rollback segment (s) are active.
The 2017-09-22 09:40:02 2258 [Note] InnoDB: Waiting for purge to start
The 2017-09-22 09:40:02 2258 [Note] InnoDB: 5.6.29 started; The log sequence number 962097308
The 2258 09:40:02 2017-09-22 [Note] Recovering after a crash using mysql - bin
The 2258 09:40:02 2017-09-22 [Note] Starting crash recovery...
The 2258 09:40:02 2017-09-22 [Note] Crash recovery finished.
The 2258 09:40:02 2017-09-22 [Note] Server hostname (bind - address) : '0.0.0.0'; Port: 3306
The 2017-09-22 09:40:02 2258 [Note] - '0.0.0.0 resolves to' 0.0.0.0 ';
The 2258 09:40:02 2017-09-22 [Note] Server socket created on IP: '0.0.0.0.
The 2258 09:40:02 2017-09-22 [Note] Event Scheduler: the Loaded 0 events
The 2258 09:40:02 2017-09-22 [Note]/usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.6.29 - log' socket: '/TMP/mysql. The sock' port: 3306 Source distribution
170922 09:57:02 mysqld_safe Number of the processes running now: 0
170922 09:57:02 mysqld_safe mysqld restarted
The 2017-09-22 09:57:02 0 [Note]/usr/local/mysql/bin/mysqld (mysqld 5.6.29 - log) starting as the process of 2648...
The 2648 09:57:02 2017-09-22 [Note] the Plugin 'FEDERATED is disabled.
The 2017-09-22 09:57:02 2648 [Note] InnoDB: Using atomics to ref count buffer pool pages
The 2017-09-22 09:57:02 2648 InnoDB [Note] : The InnoDB heap memory is disabled
The 2017-09-22 09:57:02 2648 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-09-22 09:57:02 2648 InnoDB [Note] : the Memory barrier is not 2
The 2017-09-22 09:57:02 2648 [Note] InnoDB: Compressed tables use zlib 1.2.3
The 2017-09-22 09:57:02 2648 [Note] InnoDB: Using CPU crc32 instructions
The 2017-09-22 09:57:02 2648 [Note] InnoDB: Initializing buffer pool, size=1.0 G
The 2017-09-22 09:57:02 InnoDB [Note] : 2648 Completed initialization of buffer pool
The 2017-09-22 09:57:02 2648 [Note] InnoDB: Highest supported file format is Barracuda.
The 2648 09:57:02 2017-09-22 [Note] InnoDB: The log sequence Numbers 962097288 and 962097288 in ibdata files do not match The log sequence number 962097318 in The ib_logfiles!
The 2648 09:57:02 2017-09-22 [Note] InnoDB: the Database was not shutdown normally!
The 2017-09-22 09:57:02 2648 [Note] InnoDB: Starting crash recovery.
The 2017-09-22 09:57:02 2648 [Note] InnoDB: Reading in tablespace information from the. Ibd files...
The 2017-09-22 09:57:02 2648 [Note] InnoDB: Restoring possible half - written data pages
The 2017-09-22 09:57:02 2648 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0, 1122, the file name MySQL - bin. 001029
09:57:02 InnoDB [Note] : 2648 2017-09-22 128 the rollback segment (s) are active.
The 2017-09-22 09:57:02 2648 [Note] InnoDB: Waiting for purge to start
The 2017-09-22 09:57:02 2648 [Note] InnoDB: 5.6.29 started; The log sequence number 962097318
The 2648 09:57:02 2017-09-22 [Note] Recovering after a crash using mysql - bin
The 2648 09:57:02 2017-09-22 [Note] Starting crash recovery...
The 2648 09:57:02 2017-09-22 [Note] Crash recovery finished.
The 2648 09:57:02 2017-09-22 [Note] Server hostname (bind - address) : '0.0.0.0'; Port: 3306
The 2017-09-22 09:57:02 2648 [Note] - '0.0.0.0 resolves to' 0.0.0.0 ';
The 2648 09:57:02 2017-09-22 [Note] Server socket created on IP: '0.0.0.0.
nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull
  • Related