Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 2014-05-05 12:54:19 2148 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-05 12:54:19 2148 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-05 12:54:19 2148 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-05 12:54:19 2148 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-05 12:54:19 2148 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-05 12:54:19 2148 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-05 12:54:19 2148 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-05 12:54:19 2148 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-05 12:54:19 2148 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-05 12:54:19 2148 [Note] InnoDB: The first specified data file .\ibdata1 did not exist: a new database to be created!
- 2014-05-05 12:54:19 2148 [Note] InnoDB: Setting file .\ibdata1 size to 12 MB
- 2014-05-05 12:54:19 2148 [Note] InnoDB: Database physically writes the file full: wait...
- 2014-05-05 12:54:19 2148 [Note] InnoDB: Setting log file .\ib_logfile101 size to 48 MB
- 2014-05-05 12:54:21 2148 [Note] InnoDB: Setting log file .\ib_logfile1 size to 48 MB
- 2014-05-05 12:54:23 2148 [Note] InnoDB: Renaming log file .\ib_logfile101 to .\ib_logfile0
- 2014-05-05 12:54:23 2148 [Warning] InnoDB: New log files created, LSN=45781
- 2014-05-05 12:54:23 2148 [Note] InnoDB: Doublewrite buffer not found: creating new
- 2014-05-05 12:54:23 2148 [Note] InnoDB: Doublewrite buffer created
- 2014-05-05 12:54:23 2148 [Note] InnoDB: 128 rollback segment(s) are active.
- 2014-05-05 12:54:23 2148 [Warning] InnoDB: Creating foreign key constraint system tables.
- 2014-05-05 12:54:23 2148 [Note] InnoDB: Foreign key constraint system tables created
- 2014-05-05 12:54:23 2148 [Note] InnoDB: Creating tablespace and datafile system tables.
- 2014-05-05 12:54:23 2148 [Note] InnoDB: Tablespace and datafile system tables created.
- 2014-05-05 12:54:23 2148 [Note] InnoDB: Waiting for purge to start
- 2014-05-05 12:54:23 2148 [Note] InnoDB: 5.6.16 started; log sequence number 0
- 2014-05-05 12:54:23 2148 [Note] Server hostname (bind-address): '*'; port: 3306
- 2014-05-05 12:54:26 2148 [Note] IPv6 is not available.
- 2014-05-05 12:54:26 2148 [Note] - '0.0.0.0' resolves to '0.0.0.0';
- 2014-05-05 12:54:26 2148 [Note] Server socket created on IP: '0.0.0.0'.
- 2014-05-05 12:54:26 2148 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 12:54:26 2148 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
- 2014-05-05 12:54:26 2148 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 12:54:26 2148 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 12:54:26 2148 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
- 2014-05-05 12:54:26 2148 [Note] Event Scheduler: Loaded 0 events
- 2014-05-05 12:54:26 2148 [Note] mysql\bin\mysqld.exe: ready for connections.
- Version: '5.6.16' socket: '' port: 3306 MySQL Community Server (GPL)
- 2014-05-05 15:03:26 2160 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-05 15:03:26 2160 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-05 15:03:26 2160 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-05 15:03:26 2160 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-05 15:03:26 2160 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-05 15:03:26 2160 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-05 15:03:26 2160 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-05 15:03:26 2160 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-05 15:03:26 2160 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-05 15:03:27 2160 [Note] InnoDB: Highest supported file format is Barracuda.
- 2014-05-05 15:03:27 2160 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1600607 in the ib_logfiles!
- 2014-05-05 15:03:27 2160 [Note] InnoDB: Database was not shutdown normally!
- 2014-05-05 15:03:27 2160 [Note] InnoDB: Starting crash recovery.
- 2014-05-05 15:03:27 2160 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2014-05-05 15:03:27 2160 [Note] InnoDB: Restoring possible half-written data pages
- 2014-05-05 15:03:27 2160 [Note] InnoDB: from the doublewrite buffer...
- 2014-05-05 15:03:28 2160 [Note] InnoDB: 128 rollback segment(s) are active.
- 2014-05-05 15:03:29 2160 [Note] InnoDB: Waiting for purge to start
- 2014-05-05 15:03:29 2160 [Note] InnoDB: 5.6.16 started; log sequence number 1600607
- 2014-05-05 15:03:29 2160 [Note] Server hostname (bind-address): '*'; port: 3306
- 2014-05-05 15:03:31 2160 [Note] IPv6 is not available.
- 2014-05-05 15:03:31 2160 [Note] - '0.0.0.0' resolves to '0.0.0.0';
- 2014-05-05 15:03:31 2160 [Note] Server socket created on IP: '0.0.0.0'.
- 2014-05-05 15:03:32 2160 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 15:03:32 2160 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
- 2014-05-05 15:03:32 2160 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 15:03:32 2160 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 15:03:32 2160 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
- 2014-05-05 15:03:33 2160 [Note] Event Scheduler: Loaded 0 events
- 2014-05-05 15:03:33 2160 [Note] mysql\bin\mysqld.exe: ready for connections.
- Version: '5.6.16' socket: '' port: 3306 MySQL Community Server (GPL)
- 2014-05-05 15:08:23 2160 [Note] mysql\bin\mysqld.exe: Normal shutdown
- 2014-05-05 15:08:23 2160 [Note] Giving 1 client threads a chance to die gracefully
- 2014-05-05 15:08:23 2160 [Note] Event Scheduler: Purging the queue. 0 events
- 2014-05-05 15:08:23 2160 [Note] Shutting down slave threads
- 2014-05-05 15:08:23 2160 [Note] Forcefully disconnecting 0 remaining clients
- 2014-05-05 15:08:23 2160 [Note] Binlog end
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'partition'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_FT_DELETED'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_METRICS'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_CMPMEM'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_CMP_RESET'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_CMP'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_LOCKS'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'INNODB_TRX'
- 2014-05-05 15:08:23 2160 [Note] Shutting down plugin 'InnoDB'
- 2014-05-05 15:08:23 2160 [Note] InnoDB: FTS optimize thread exiting.
- 2014-05-05 15:08:23 2160 [Note] InnoDB: Starting shutdown...
- 2014-05-05 15:08:24 2160 [Note] InnoDB: Shutdown completed; log sequence number 1600617
- 2014-05-05 15:08:24 2160 [Note] Shutting down plugin 'BLACKHOLE'
- 2014-05-05 15:08:24 2160 [Note] Shutting down plugin 'ARCHIVE'
- 2014-05-05 15:08:24 2160 [Note] Shutting down plugin 'MRG_MYISAM'
- 2014-05-05 15:08:24 2160 [Note] Shutting down plugin 'MyISAM'
- 2014-05-05 15:08:24 2160 [Note] Shutting down plugin 'MEMORY'
- 2014-05-05 15:08:25 2160 [Note] Shutting down plugin 'CSV'
- 2014-05-05 15:08:25 2160 [Note] Shutting down plugin 'sha256_password'
- 2014-05-05 15:08:25 2160 [Note] Shutting down plugin 'mysql_old_password'
- 2014-05-05 15:08:25 2160 [Note] Shutting down plugin 'mysql_native_password'
- 2014-05-05 15:08:25 2160 [Note] Shutting down plugin 'binlog'
- 2014-05-05 15:08:25 2160 [Note] mysql\bin\mysqld.exe: Shutdown complete
- 2014-05-05 15:08:31 648 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-05 15:08:31 648 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-05 15:08:31 648 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-05 15:08:31 648 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-05 15:08:31 648 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-05 15:08:31 648 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-05 15:08:31 648 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-05 15:08:31 648 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-05 15:08:32 648 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-05 15:08:32 648 [Note] InnoDB: Highest supported file format is Barracuda.
- 2014-05-05 15:08:32 648 [Note] InnoDB: 128 rollback segment(s) are active.
- 2014-05-05 15:08:32 648 [Note] InnoDB: Waiting for purge to start
- 2014-05-05 15:08:32 648 [Note] InnoDB: 5.6.16 started; log sequence number 1600617
- 2014-05-05 15:08:32 648 [Note] Server hostname (bind-address): '*'; port: 3306
- 2014-05-05 15:08:34 648 [Note] IPv6 is not available.
- 2014-05-05 15:08:34 648 [Note] - '0.0.0.0' resolves to '0.0.0.0';
- 2014-05-05 15:08:34 648 [Note] Server socket created on IP: '0.0.0.0'.
- 2014-05-05 15:08:34 648 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 15:08:34 648 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
- 2014-05-05 15:08:34 648 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 15:08:34 648 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 15:08:34 648 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
- 2014-05-05 15:08:34 648 [Note] Event Scheduler: Loaded 0 events
- 2014-05-05 15:08:34 648 [Note] mysql\bin\mysqld.exe: ready for connections.
- Version: '5.6.16' socket: '' port: 3306 MySQL Community Server (GPL)
- 2014-05-05 15:12:56 648 [Note] mysql\bin\mysqld.exe: Normal shutdown
- 2014-05-05 15:12:56 648 [Note] Giving 0 client threads a chance to die gracefully
- 2014-05-05 15:12:56 648 [Note] Event Scheduler: Purging the queue. 0 events
- 2014-05-05 15:12:56 648 [Note] Shutting down slave threads
- 2014-05-05 15:12:56 648 [Note] Forcefully disconnecting 0 remaining clients
- 2014-05-05 15:12:56 648 [Note] Binlog end
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'partition'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_FT_DELETED'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_METRICS'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_CMPMEM'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_CMP_RESET'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_CMP'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_LOCKS'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'INNODB_TRX'
- 2014-05-05 15:12:56 648 [Note] Shutting down plugin 'InnoDB'
- 2014-05-05 15:12:56 648 [Note] InnoDB: FTS optimize thread exiting.
- 2014-05-05 15:12:56 648 [Note] InnoDB: Starting shutdown...
- 2014-05-05 15:12:57 648 [Note] InnoDB: Shutdown completed; log sequence number 1600627
- 2014-05-05 15:12:57 648 [Note] Shutting down plugin 'BLACKHOLE'
- 2014-05-05 15:12:57 648 [Note] Shutting down plugin 'ARCHIVE'
- 2014-05-05 15:12:57 648 [Note] Shutting down plugin 'MRG_MYISAM'
- 2014-05-05 15:12:57 648 [Note] Shutting down plugin 'MyISAM'
- 2014-05-05 15:12:57 648 [Note] Shutting down plugin 'MEMORY'
- 2014-05-05 15:12:57 648 [Note] Shutting down plugin 'CSV'
- 2014-05-05 15:12:57 648 [Note] Shutting down plugin 'sha256_password'
- 2014-05-05 15:12:57 648 [Note] Shutting down plugin 'mysql_old_password'
- 2014-05-05 15:12:57 648 [Note] Shutting down plugin 'mysql_native_password'
- 2014-05-05 15:12:57 648 [Note] Shutting down plugin 'binlog'
- 2014-05-05 15:12:57 648 [Note] mysql\bin\mysqld.exe: Shutdown complete
- 2014-05-05 15:12:59 2356 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-05 15:12:59 2356 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-05 15:12:59 2356 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-05 15:12:59 2356 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-05 15:12:59 2356 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-05 15:12:59 2356 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-05 15:12:59 2356 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-05 15:12:59 2356 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-05 15:12:59 2356 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-05 15:12:59 2356 [Note] InnoDB: Highest supported file format is Barracuda.
- 2014-05-05 15:12:59 2356 [Note] InnoDB: 128 rollback segment(s) are active.
- 2014-05-05 15:12:59 2356 [Note] InnoDB: Waiting for purge to start
- 2014-05-05 15:12:59 2356 [Note] InnoDB: 5.6.16 started; log sequence number 1600627
- 2014-05-05 15:12:59 2356 [Note] Server hostname (bind-address): '*'; port: 3306
- 2014-05-05 15:13:02 2356 [Note] IPv6 is not available.
- 2014-05-05 15:13:02 2356 [Note] - '0.0.0.0' resolves to '0.0.0.0';
- 2014-05-05 15:13:02 2356 [Note] Server socket created on IP: '0.0.0.0'.
- 2014-05-05 15:13:02 2356 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 15:13:02 2356 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
- 2014-05-05 15:13:02 2356 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 15:13:02 2356 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 15:13:02 2356 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
- 2014-05-05 15:13:02 2356 [Note] Event Scheduler: Loaded 0 events
- 2014-05-05 15:13:02 2356 [Note] mysql\bin\mysqld.exe: ready for connections.
- Version: '5.6.16' socket: '' port: 3306 MySQL Community Server (GPL)
- 2014-05-05 15:36:44 3792 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-05 15:36:44 3792 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-05 15:36:44 3792 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-05 15:36:44 3792 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-05 15:36:44 3792 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-05 15:36:44 3792 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-05 15:36:44 3792 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-05 15:36:44 3792 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-05 15:36:44 3792 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-05 15:36:44 3792 [Note] InnoDB: Highest supported file format is Barracuda.
- 2014-05-05 15:36:44 3792 [Note] InnoDB: The log sequence numbers 1600627 and 1600627 in ibdata files do not match the log sequence number 1600637 in the ib_logfiles!
- 2014-05-05 15:36:44 3792 [Note] InnoDB: Database was not shutdown normally!
- 2014-05-05 15:36:44 3792 [Note] InnoDB: Starting crash recovery.
- 2014-05-05 15:36:44 3792 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2014-05-05 15:36:45 3792 [Note] InnoDB: Restoring possible half-written data pages
- 2014-05-05 15:36:45 3792 [Note] InnoDB: from the doublewrite buffer...
- 2014-05-05 15:36:46 3792 [Note] InnoDB: 128 rollback segment(s) are active.
- 2014-05-05 15:36:47 3792 [Note] InnoDB: Waiting for purge to start
- 2014-05-05 15:36:47 3792 [Note] InnoDB: 5.6.16 started; log sequence number 1600637
- 2014-05-05 15:36:47 3792 [Note] Server hostname (bind-address): '*'; port: 3306
- 2014-05-05 15:36:49 3792 [Note] IPv6 is not available.
- 2014-05-05 15:36:49 3792 [Note] - '0.0.0.0' resolves to '0.0.0.0';
- 2014-05-05 15:36:49 3792 [Note] Server socket created on IP: '0.0.0.0'.
- 2014-05-05 15:36:50 3792 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 15:36:50 3792 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
- 2014-05-05 15:36:50 3792 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 15:36:50 3792 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 15:36:50 3792 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
- 2014-05-05 15:36:50 3792 [Note] Event Scheduler: Loaded 0 events
- 2014-05-05 15:36:50 3792 [Note] mysql\bin\mysqld.exe: ready for connections.
- Version: '5.6.16' socket: '' port: 3306 MySQL Community Server (GPL)
- 2014-05-05 18:57:30 1820 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-05 18:57:30 1820 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-05 18:57:30 1820 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-05 18:57:30 1820 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-05 18:57:30 1820 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-05 18:57:30 1820 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-05 18:57:30 1820 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-05 18:57:30 1820 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-05 18:57:30 1820 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-05 18:57:31 1820 [Note] InnoDB: Highest supported file format is Barracuda.
- 2014-05-05 18:57:31 1820 [Note] InnoDB: The log sequence numbers 1600627 and 1600627 in ibdata files do not match the log sequence number 1600647 in the ib_logfiles!
- 2014-05-05 18:57:31 1820 [Note] InnoDB: Database was not shutdown normally!
- 2014-05-05 18:57:31 1820 [Note] InnoDB: Starting crash recovery.
- 2014-05-05 18:57:31 1820 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2014-05-05 18:57:31 1820 [Note] InnoDB: Restoring possible half-written data pages
- 2014-05-05 18:57:31 1820 [Note] InnoDB: from the doublewrite buffer...
- 2014-05-05 18:57:32 1820 [Note] InnoDB: 128 rollback segment(s) are active.
- 2014-05-05 18:57:32 1820 [Note] InnoDB: Waiting for purge to start
- 2014-05-05 18:57:33 1820 [Note] InnoDB: 5.6.16 started; log sequence number 1600647
- 2014-05-05 18:57:33 1820 [Note] Server hostname (bind-address): '*'; port: 3306
- 2014-05-05 18:57:35 1820 [Note] IPv6 is not available.
- 2014-05-05 18:57:35 1820 [Note] - '0.0.0.0' resolves to '0.0.0.0';
- 2014-05-05 18:57:35 1820 [Note] Server socket created on IP: '0.0.0.0'.
- 2014-05-05 18:57:36 1820 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 18:57:36 1820 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
- 2014-05-05 18:57:36 1820 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 18:57:36 1820 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 18:57:36 1820 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
- 2014-05-05 18:57:36 1820 [Note] Event Scheduler: Loaded 0 events
- 2014-05-05 18:57:36 1820 [Note] mysql\bin\mysqld.exe: ready for connections.
- Version: '5.6.16' socket: '' port: 3306 MySQL Community Server (GPL)
- 2014-05-05 19:15:00 1820 [Note] mysql\bin\mysqld.exe: Normal shutdown
- 2014-05-05 19:15:00 1820 [Note] Giving 0 client threads a chance to die gracefully
- 2014-05-05 19:15:00 1820 [Note] Event Scheduler: Purging the queue. 0 events
- 2014-05-05 19:15:00 1820 [Note] Shutting down slave threads
- 2014-05-05 19:15:00 1820 [Note] Forcefully disconnecting 0 remaining clients
- 2014-05-05 19:15:00 1820 [Note] Binlog end
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'partition'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_FT_DELETED'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_METRICS'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_CMPMEM'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_CMP_RESET'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_CMP'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_LOCKS'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'INNODB_TRX'
- 2014-05-05 19:15:00 1820 [Note] Shutting down plugin 'InnoDB'
- 2014-05-05 19:15:00 1820 [Note] InnoDB: FTS optimize thread exiting.
- 2014-05-05 19:15:00 1820 [Note] InnoDB: Starting shutdown...
- 2014-05-05 19:15:01 1820 [Note] InnoDB: Shutdown completed; log sequence number 1600657
- 2014-05-05 19:15:01 1820 [Note] Shutting down plugin 'BLACKHOLE'
- 2014-05-05 19:15:01 1820 [Note] Shutting down plugin 'ARCHIVE'
- 2014-05-05 19:15:01 1820 [Note] Shutting down plugin 'MRG_MYISAM'
- 2014-05-05 19:15:01 1820 [Note] Shutting down plugin 'MyISAM'
- 2014-05-05 19:15:01 1820 [Note] Shutting down plugin 'MEMORY'
- 2014-05-05 19:15:01 1820 [Note] Shutting down plugin 'CSV'
- 2014-05-05 19:15:01 1820 [Note] Shutting down plugin 'sha256_password'
- 2014-05-05 19:15:01 1820 [Note] Shutting down plugin 'mysql_old_password'
- 2014-05-05 19:15:01 1820 [Note] Shutting down plugin 'mysql_native_password'
- 2014-05-05 19:15:01 1820 [Note] Shutting down plugin 'binlog'
- 2014-05-05 19:15:01 1820 [Note] mysql\bin\mysqld.exe: Shutdown complete
- 2014-05-05 19:15:03 3508 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-05 19:15:03 3508 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-05 19:15:03 3508 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-05 19:15:03 3508 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-05 19:15:03 3508 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-05 19:15:03 3508 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-05 19:15:03 3508 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-05 19:15:03 3508 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-05 19:15:03 3508 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-05 19:15:03 3508 [Note] InnoDB: Highest supported file format is Barracuda.
- 2014-05-05 19:15:03 3508 [Note] InnoDB: 128 rollback segment(s) are active.
- 2014-05-05 19:15:03 3508 [Note] InnoDB: Waiting for purge to start
- 2014-05-05 19:15:03 3508 [Note] InnoDB: 5.6.16 started; log sequence number 1600657
- 2014-05-05 19:15:03 3508 [Note] Server hostname (bind-address): '*'; port: 3306
- 2014-05-05 19:15:06 3508 [Note] IPv6 is not available.
- 2014-05-05 19:15:06 3508 [Note] - '0.0.0.0' resolves to '0.0.0.0';
- 2014-05-05 19:15:06 3508 [Note] Server socket created on IP: '0.0.0.0'.
- 2014-05-05 19:15:06 3508 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 19:15:06 3508 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
- 2014-05-05 19:15:06 3508 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 19:15:06 3508 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 19:15:06 3508 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
- 2014-05-05 19:15:06 3508 [Note] Event Scheduler: Loaded 0 events
- 2014-05-05 19:15:06 3508 [Note] mysql\bin\mysqld.exe: ready for connections.
- Version: '5.6.16' socket: '' port: 3306 MySQL Community Server (GPL)
- 2014-05-05 19:15:06 2624 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-05 19:15:06 2624 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-05 19:15:06 2624 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-05 19:15:06 2624 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-05 19:15:06 2624 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-05 19:15:06 2624 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-05 19:15:06 2624 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-05 19:15:06 2624 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-05 19:15:06 2624 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-05 19:15:06 2624 [ERROR] InnoDB: .\ibdata1 can't be opened in read-write mode
- 2014-05-05 19:15:06 2624 [ERROR] InnoDB: The system tablespace must be writable!
- 2014-05-05 19:15:06 2624 [ERROR] Plugin 'InnoDB' init function returned error.
- 2014-05-05 19:15:06 2624 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
- 2014-05-05 19:15:06 2624 [ERROR] Unknown/unsupported storage engine: InnoDB
- 2014-05-05 19:15:06 2624 [ERROR] Aborting
- 2014-05-05 19:15:06 2624 [Note] Binlog end
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'partition'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_FT_DELETED'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_METRICS'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_CMPMEM'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_CMP_RESET'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_CMP'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_LOCKS'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'INNODB_TRX'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'BLACKHOLE'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'ARCHIVE'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'MRG_MYISAM'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'MyISAM'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'MEMORY'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'CSV'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'sha256_password'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'mysql_old_password'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'mysql_native_password'
- 2014-05-05 19:15:06 2624 [Note] Shutting down plugin 'binlog'
- 2014-05-05 19:15:06 2624 [Note] mysql\bin\mysqld.exe: Shutdown complete
- 2014-05-05 19:15:13 3508 [Note] mysql\bin\mysqld.exe: Normal shutdown
- 2014-05-05 19:15:13 3508 [Note] Giving 0 client threads a chance to die gracefully
- 2014-05-05 19:15:13 3508 [Note] Event Scheduler: Purging the queue. 0 events
- 2014-05-05 19:15:13 3508 [Note] Shutting down slave threads
- 2014-05-05 19:15:13 3508 [Note] Forcefully disconnecting 0 remaining clients
- 2014-05-05 19:15:13 3508 [Note] Binlog end
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'partition'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_FT_DELETED'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_METRICS'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_CMPMEM'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_CMP_RESET'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_CMP'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_LOCKS'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'INNODB_TRX'
- 2014-05-05 19:15:13 3508 [Note] Shutting down plugin 'InnoDB'
- 2014-05-05 19:15:13 3508 [Note] InnoDB: FTS optimize thread exiting.
- 2014-05-05 19:15:13 3508 [Note] InnoDB: Starting shutdown...
- 2014-05-05 19:15:14 3508 [Note] InnoDB: Shutdown completed; log sequence number 1600667
- 2014-05-05 19:15:14 3508 [Note] Shutting down plugin 'BLACKHOLE'
- 2014-05-05 19:15:14 3508 [Note] Shutting down plugin 'ARCHIVE'
- 2014-05-05 19:15:14 3508 [Note] Shutting down plugin 'MRG_MYISAM'
- 2014-05-05 19:15:14 3508 [Note] Shutting down plugin 'MyISAM'
- 2014-05-05 19:15:14 3508 [Note] Shutting down plugin 'MEMORY'
- 2014-05-05 19:15:14 3508 [Note] Shutting down plugin 'CSV'
- 2014-05-05 19:15:14 3508 [Note] Shutting down plugin 'sha256_password'
- 2014-05-05 19:15:14 3508 [Note] Shutting down plugin 'mysql_old_password'
- 2014-05-05 19:15:14 3508 [Note] Shutting down plugin 'mysql_native_password'
- 2014-05-05 19:15:14 3508 [Note] Shutting down plugin 'binlog'
- 2014-05-05 19:15:14 3508 [Note] mysql\bin\mysqld.exe: Shutdown complete
- 2014-05-05 19:15:20 2644 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-05 19:15:20 2644 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-05 19:15:20 2644 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-05 19:15:20 2644 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-05 19:15:20 2644 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-05 19:15:20 2644 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-05 19:15:20 2644 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-05 19:15:20 2644 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-05 19:15:20 2644 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-05 19:15:20 2644 [Note] InnoDB: Highest supported file format is Barracuda.
- 2014-05-05 19:15:21 2644 [Note] InnoDB: 128 rollback segment(s) are active.
- 2014-05-05 19:15:21 2644 [Note] InnoDB: Waiting for purge to start
- 2014-05-05 19:15:21 2644 [Note] InnoDB: 5.6.16 started; log sequence number 1600667
- 2014-05-05 19:15:21 2644 [Note] Server hostname (bind-address): '*'; port: 3306
- 2014-05-05 19:15:23 2644 [Note] IPv6 is not available.
- 2014-05-05 19:15:23 2644 [Note] - '0.0.0.0' resolves to '0.0.0.0';
- 2014-05-05 19:15:23 2644 [Note] Server socket created on IP: '0.0.0.0'.
- 2014-05-05 19:15:23 2644 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 19:15:23 2644 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
- 2014-05-05 19:15:23 2644 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 19:15:23 2644 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 19:15:23 2644 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
- 2014-05-05 19:15:23 2644 [Note] Event Scheduler: Loaded 0 events
- 2014-05-05 19:15:23 2644 [Note] mysql\bin\mysqld.exe: ready for connections.
- Version: '5.6.16' socket: '' port: 3306 MySQL Community Server (GPL)
- 2014-05-05 19:33:41 2644 [Note] mysql\bin\mysqld.exe: Normal shutdown
- 2014-05-05 19:33:41 2644 [Note] Giving 0 client threads a chance to die gracefully
- 2014-05-05 19:33:41 2644 [Note] Event Scheduler: Purging the queue. 0 events
- 2014-05-05 19:33:41 2644 [Note] Shutting down slave threads
- 2014-05-05 19:33:41 2644 [Note] Forcefully disconnecting 0 remaining clients
- 2014-05-05 19:33:41 2644 [Note] Binlog end
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'partition'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_FT_DELETED'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_METRICS'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_CMPMEM'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_CMP_RESET'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_CMP'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_LOCKS'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'INNODB_TRX'
- 2014-05-05 19:33:41 2644 [Note] Shutting down plugin 'InnoDB'
- 2014-05-05 19:33:41 2644 [Note] InnoDB: FTS optimize thread exiting.
- 2014-05-05 19:33:41 2644 [Note] InnoDB: Starting shutdown...
- 2014-05-05 19:33:42 2644 [Note] InnoDB: Shutdown completed; log sequence number 1600677
- 2014-05-05 19:33:42 2644 [Note] Shutting down plugin 'BLACKHOLE'
- 2014-05-05 19:33:42 2644 [Note] Shutting down plugin 'ARCHIVE'
- 2014-05-05 19:33:42 2644 [Note] Shutting down plugin 'MRG_MYISAM'
- 2014-05-05 19:33:42 2644 [Note] Shutting down plugin 'MyISAM'
- 2014-05-05 19:33:42 2644 [Note] Shutting down plugin 'MEMORY'
- 2014-05-05 19:33:42 2644 [Note] Shutting down plugin 'CSV'
- 2014-05-05 19:33:42 2644 [Note] Shutting down plugin 'sha256_password'
- 2014-05-05 19:33:42 2644 [Note] Shutting down plugin 'mysql_old_password'
- 2014-05-05 19:33:42 2644 [Note] Shutting down plugin 'mysql_native_password'
- 2014-05-05 19:33:42 2644 [Note] Shutting down plugin 'binlog'
- 2014-05-05 19:33:42 2644 [Note] mysql\bin\mysqld.exe: Shutdown complete
- 2014-05-05 19:33:47 4012 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-05 19:33:47 4012 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-05 19:33:47 4012 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-05 19:33:47 4012 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-05 19:33:47 4012 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-05 19:33:47 4012 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-05 19:33:47 4012 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-05 19:33:47 4012 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-05 19:33:47 4012 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-05 19:33:47 4012 [Note] InnoDB: Highest supported file format is Barracuda.
- 2014-05-05 19:33:48 4012 [Note] InnoDB: 128 rollback segment(s) are active.
- 2014-05-05 19:33:48 4012 [Note] InnoDB: Waiting for purge to start
- 2014-05-05 19:33:48 4012 [Note] InnoDB: 5.6.16 started; log sequence number 1600677
- 2014-05-05 19:33:48 4012 [Note] Server hostname (bind-address): '*'; port: 3306
- 2014-05-05 19:33:50 4012 [Note] IPv6 is not available.
- 2014-05-05 19:33:50 4012 [Note] - '0.0.0.0' resolves to '0.0.0.0';
- 2014-05-05 19:33:50 4012 [Note] Server socket created on IP: '0.0.0.0'.
- 2014-05-05 19:33:50 4012 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 19:33:50 4012 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
- 2014-05-05 19:33:50 4012 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 19:33:50 4012 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
- 2014-05-05 19:33:50 4012 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
- 2014-05-05 19:33:50 4012 [Note] Event Scheduler: Loaded 0 events
- 2014-05-05 19:33:50 4012 [Note] mysql\bin\mysqld.exe: ready for connections.
- Version: '5.6.16' socket: '' port: 3306 MySQL Community Server (GPL)
- 2014-05-05 21:58:27 d5c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
- 2014-05-05 21:58:36 cd0 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
- 2014-05-05 21:58:36 cd0 InnoDB: Error: Fetch of persistent statistics requested for table "wp20"."wp_yarpp_related_cache" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
- 2014-05-05 22:04:34 d5c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
- 2014-05-05 22:04:34 d5c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
- 2014-05-05 22:04:34 d5c InnoDB: Error: Fetch of persistent statistics requested for table "wp182"."wp_yarpp_related_cache" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
- 2014-05-06 00:41:07 820 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-06 00:41:07 820 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-06 00:41:07 820 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-06 00:41:07 820 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-06 00:41:07 820 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-06 00:41:07 820 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-06 00:41:07 820 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-06 00:41:07 820 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-06 00:41:07 820 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-06 00:41:07 820 [Note] InnoDB: Highest supported file format is Barracuda.
- 2014-05-06 00:41:08 820 [Note] InnoDB: The log sequence numbers 1600677 and 1600677 in ibdata files do not match the log sequence number 1614525 in the ib_logfiles!
- 2014-05-06 00:41:08 820 [Note] InnoDB: Database was not shutdown normally!
- 2014-05-06 00:41:08 820 [Note] InnoDB: Starting crash recovery.
- 2014-05-06 00:41:08 820 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2014-05-06 00:41:08 820 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace wp182/wp_yarpp_related_cache which uses space ID: 2 at filepath: .\wp182\wp_yarpp_related_cache.ibd
- 2014-05-06 00:41:08 324 InnoDB: Operating system error number 997 in a file operation.
- InnoDB: Some operating system error numbers are described at
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
- InnoDB: Error: could not open single-table tablespace file .\wp182\wp_yarpp_related_cache.ibd
- InnoDB: We do not continue the crash recovery, because the table may become
- InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
- InnoDB: To fix the problem and start mysqld:
- InnoDB: 1) If there is a permission problem in the file and mysqld cannot
- InnoDB: open the file, you should modify the permissions.
- InnoDB: 2) If the table is not needed, or you can restore it from a backup,
- InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
- InnoDB: crash recovery and ignore that table.
- InnoDB: 3) If the file system or the disk is broken, and you cannot remove
- InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
- InnoDB: and force InnoDB to continue crash recovery here.
- 2014-05-06 01:13:25 1320 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-06 01:13:25 1320 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-06 01:13:25 1320 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-06 01:13:25 1320 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-06 01:13:25 1320 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-06 01:13:25 1320 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-06 01:13:25 1320 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-06 01:13:25 1320 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-06 01:13:25 1320 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-06 01:13:25 1320 [Note] InnoDB: Highest supported file format is Barracuda.
- 2014-05-06 01:13:25 1320 [Note] InnoDB: The log sequence numbers 1600677 and 1600677 in ibdata files do not match the log sequence number 1614525 in the ib_logfiles!
- 2014-05-06 01:13:25 1320 [Note] InnoDB: Database was not shutdown normally!
- 2014-05-06 01:13:25 1320 [Note] InnoDB: Starting crash recovery.
- 2014-05-06 01:13:25 1320 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2014-05-06 01:13:26 1320 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace wp182/wp_yarpp_related_cache which uses space ID: 2 at filepath: .\wp182\wp_yarpp_related_cache.ibd
- 2014-05-06 01:13:26 f20 InnoDB: Operating system error number 997 in a file operation.
- InnoDB: Some operating system error numbers are described at
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
- InnoDB: Error: could not open single-table tablespace file .\wp182\wp_yarpp_related_cache.ibd
- InnoDB: We do not continue the crash recovery, because the table may become
- InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
- InnoDB: To fix the problem and start mysqld:
- InnoDB: 1) If there is a permission problem in the file and mysqld cannot
- InnoDB: open the file, you should modify the permissions.
- InnoDB: 2) If the table is not needed, or you can restore it from a backup,
- InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
- InnoDB: crash recovery and ignore that table.
- InnoDB: 3) If the file system or the disk is broken, and you cannot remove
- InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
- InnoDB: and force InnoDB to continue crash recovery here.
- 2014-05-06 01:13:28 2844 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-06 01:13:28 2844 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-06 01:13:28 2844 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-06 01:13:28 2844 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-06 01:13:28 2844 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-06 01:13:28 2844 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-06 01:13:28 2844 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-06 01:13:28 2844 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-06 01:13:28 2844 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-06 01:13:28 2844 [Note] InnoDB: Highest supported file format is Barracuda.
- 2014-05-06 01:13:28 2844 [Note] InnoDB: The log sequence numbers 1600677 and 1600677 in ibdata files do not match the log sequence number 1614525 in the ib_logfiles!
- 2014-05-06 01:13:28 2844 [Note] InnoDB: Database was not shutdown normally!
- 2014-05-06 01:13:28 2844 [Note] InnoDB: Starting crash recovery.
- 2014-05-06 01:13:28 2844 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2014-05-06 01:13:29 2844 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace wp182/wp_yarpp_related_cache which uses space ID: 2 at filepath: .\wp182\wp_yarpp_related_cache.ibd
- 2014-05-06 01:13:29 b20 InnoDB: Operating system error number 997 in a file operation.
- InnoDB: Some operating system error numbers are described at
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
- InnoDB: Error: could not open single-table tablespace file .\wp182\wp_yarpp_related_cache.ibd
- InnoDB: We do not continue the crash recovery, because the table may become
- InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
- InnoDB: To fix the problem and start mysqld:
- InnoDB: 1) If there is a permission problem in the file and mysqld cannot
- InnoDB: open the file, you should modify the permissions.
- InnoDB: 2) If the table is not needed, or you can restore it from a backup,
- InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
- InnoDB: crash recovery and ignore that table.
- InnoDB: 3) If the file system or the disk is broken, and you cannot remove
- InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
- InnoDB: and force InnoDB to continue crash recovery here.
- 2014-05-06 09:35:33 640 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-06 09:35:33 640 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-06 09:35:33 640 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-06 09:35:33 640 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-06 09:35:33 640 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-06 09:35:33 640 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-06 09:35:33 640 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-06 09:35:33 640 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-06 09:35:33 640 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-06 09:35:34 640 [Note] InnoDB: Highest supported file format is Barracuda.
- 2014-05-06 09:35:34 640 [Note] InnoDB: The log sequence numbers 1600677 and 1600677 in ibdata files do not match the log sequence number 1614525 in the ib_logfiles!
- 2014-05-06 09:35:34 640 [Note] InnoDB: Database was not shutdown normally!
- 2014-05-06 09:35:34 640 [Note] InnoDB: Starting crash recovery.
- 2014-05-06 09:35:34 640 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2014-05-06 09:35:35 640 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace wp182/wp_yarpp_related_cache which uses space ID: 2 at filepath: .\wp182\wp_yarpp_related_cache.ibd
- 2014-05-06 09:35:35 338 InnoDB: Operating system error number 997 in a file operation.
- InnoDB: Some operating system error numbers are described at
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
- InnoDB: Error: could not open single-table tablespace file .\wp182\wp_yarpp_related_cache.ibd
- InnoDB: We do not continue the crash recovery, because the table may become
- InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
- InnoDB: To fix the problem and start mysqld:
- InnoDB: 1) If there is a permission problem in the file and mysqld cannot
- InnoDB: open the file, you should modify the permissions.
- InnoDB: 2) If the table is not needed, or you can restore it from a backup,
- InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
- InnoDB: crash recovery and ignore that table.
- InnoDB: 3) If the file system or the disk is broken, and you cannot remove
- InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
- InnoDB: and force InnoDB to continue crash recovery here.
- 2014-05-06 09:35:40 2248 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-06 09:35:40 2248 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-06 09:35:40 2248 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-06 09:35:40 2248 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-06 09:35:40 2248 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-06 09:35:40 2248 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-06 09:35:40 2248 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-06 09:35:40 2248 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-06 09:35:40 2248 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-06 09:35:40 2248 [Note] InnoDB: Highest supported file format is Barracuda.
- 2014-05-06 09:35:42 2248 [Note] InnoDB: The log sequence numbers 1600677 and 1600677 in ibdata files do not match the log sequence number 1614525 in the ib_logfiles!
- 2014-05-06 09:35:42 2248 [Note] InnoDB: Database was not shutdown normally!
- 2014-05-06 09:35:42 2248 [Note] InnoDB: Starting crash recovery.
- 2014-05-06 09:35:42 2248 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2014-05-06 09:35:43 2248 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace wp182/wp_yarpp_related_cache which uses space ID: 2 at filepath: .\wp182\wp_yarpp_related_cache.ibd
- 2014-05-06 09:35:43 8cc InnoDB: Operating system error number 997 in a file operation.
- InnoDB: Some operating system error numbers are described at
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
- InnoDB: Error: could not open single-table tablespace file .\wp182\wp_yarpp_related_cache.ibd
- InnoDB: We do not continue the crash recovery, because the table may become
- InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
- InnoDB: To fix the problem and start mysqld:
- InnoDB: 1) If there is a permission problem in the file and mysqld cannot
- InnoDB: open the file, you should modify the permissions.
- InnoDB: 2) If the table is not needed, or you can restore it from a backup,
- InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
- InnoDB: crash recovery and ignore that table.
- InnoDB: 3) If the file system or the disk is broken, and you cannot remove
- InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
- InnoDB: and force InnoDB to continue crash recovery here.
- 2014-05-06 09:36:53 4048 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-06 09:36:53 4048 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-06 09:36:53 4048 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-06 09:36:53 4048 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-06 09:36:53 4048 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-06 09:36:53 4048 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-06 09:36:53 4048 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-06 09:36:53 4048 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-06 09:36:53 4048 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-06 09:36:53 4048 [Note] InnoDB: Highest supported file format is Barracuda.
- 2014-05-06 09:36:53 4048 [Note] InnoDB: The log sequence numbers 1600677 and 1600677 in ibdata files do not match the log sequence number 1614525 in the ib_logfiles!
- 2014-05-06 09:36:53 4048 [Note] InnoDB: Database was not shutdown normally!
- 2014-05-06 09:36:53 4048 [Note] InnoDB: Starting crash recovery.
- 2014-05-06 09:36:53 4048 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2014-05-06 09:36:53 4048 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace wp182/wp_yarpp_related_cache which uses space ID: 2 at filepath: .\wp182\wp_yarpp_related_cache.ibd
- 2014-05-06 09:36:53 fd4 InnoDB: Operating system error number 997 in a file operation.
- InnoDB: Some operating system error numbers are described at
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
- InnoDB: Error: could not open single-table tablespace file .\wp182\wp_yarpp_related_cache.ibd
- InnoDB: We do not continue the crash recovery, because the table may become
- InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
- InnoDB: To fix the problem and start mysqld:
- InnoDB: 1) If there is a permission problem in the file and mysqld cannot
- InnoDB: open the file, you should modify the permissions.
- InnoDB: 2) If the table is not needed, or you can restore it from a backup,
- InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
- InnoDB: crash recovery and ignore that table.
- InnoDB: 3) If the file system or the disk is broken, and you cannot remove
- InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
- InnoDB: and force InnoDB to continue crash recovery here.
- 2014-05-06 09:38:41 180 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-06 09:38:41 180 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-06 09:38:41 180 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-06 09:38:41 180 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-06 09:38:41 180 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-06 09:38:41 180 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-06 09:38:41 180 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-06 09:38:41 180 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-06 09:38:41 180 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-06 09:38:41 180 [Note] InnoDB: Highest supported file format is Barracuda.
- 2014-05-06 09:38:41 180 [Note] InnoDB: The log sequence numbers 1600677 and 1600677 in ibdata files do not match the log sequence number 1614525 in the ib_logfiles!
- 2014-05-06 09:38:41 180 [Note] InnoDB: Database was not shutdown normally!
- 2014-05-06 09:38:41 180 [Note] InnoDB: Starting crash recovery.
- 2014-05-06 09:38:41 180 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2014-05-06 09:38:41 180 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace wp182/wp_yarpp_related_cache which uses space ID: 2 at filepath: .\wp182\wp_yarpp_related_cache.ibd
- 2014-05-06 09:38:41 670 InnoDB: Operating system error number 997 in a file operation.
- InnoDB: Some operating system error numbers are described at
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
- InnoDB: Error: could not open single-table tablespace file .\wp182\wp_yarpp_related_cache.ibd
- InnoDB: We do not continue the crash recovery, because the table may become
- InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
- InnoDB: To fix the problem and start mysqld:
- InnoDB: 1) If there is a permission problem in the file and mysqld cannot
- InnoDB: open the file, you should modify the permissions.
- InnoDB: 2) If the table is not needed, or you can restore it from a backup,
- InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
- InnoDB: crash recovery and ignore that table.
- InnoDB: 3) If the file system or the disk is broken, and you cannot remove
- InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
- InnoDB: and force InnoDB to continue crash recovery here.
- 2014-05-06 09:38:44 160 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-06 09:38:44 160 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-06 09:38:44 160 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-06 09:38:44 160 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-06 09:38:44 160 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-06 09:38:44 160 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-06 09:38:44 160 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-06 09:38:44 160 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-06 09:38:44 160 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-06 09:38:44 160 [Note] InnoDB: Highest supported file format is Barracuda.
- 2014-05-06 09:38:44 160 [Note] InnoDB: The log sequence numbers 1600677 and 1600677 in ibdata files do not match the log sequence number 1614525 in the ib_logfiles!
- 2014-05-06 09:38:44 160 [Note] InnoDB: Database was not shutdown normally!
- 2014-05-06 09:38:44 160 [Note] InnoDB: Starting crash recovery.
- 2014-05-06 09:38:44 160 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2014-05-06 09:38:44 160 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace wp182/wp_yarpp_related_cache which uses space ID: 2 at filepath: .\wp182\wp_yarpp_related_cache.ibd
- 2014-05-06 09:38:44 ac InnoDB: Operating system error number 997 in a file operation.
- InnoDB: Some operating system error numbers are described at
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
- InnoDB: Error: could not open single-table tablespace file .\wp182\wp_yarpp_related_cache.ibd
- InnoDB: We do not continue the crash recovery, because the table may become
- InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
- InnoDB: To fix the problem and start mysqld:
- InnoDB: 1) If there is a permission problem in the file and mysqld cannot
- InnoDB: open the file, you should modify the permissions.
- InnoDB: 2) If the table is not needed, or you can restore it from a backup,
- InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
- InnoDB: crash recovery and ignore that table.
- InnoDB: 3) If the file system or the disk is broken, and you cannot remove
- InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
- InnoDB: and force InnoDB to continue crash recovery here.
- 2014-05-06 09:48:39 1060 [Warning] You need to use --log-bin to make --binlog-format work.
- 2014-05-06 09:48:39 1060 [Note] Plugin 'FEDERATED' is disabled.
- 2014-05-06 09:48:39 1060 [Note] InnoDB: Using atomics to ref count buffer pool pages
- 2014-05-06 09:48:39 1060 [Note] InnoDB: The InnoDB memory heap is disabled
- 2014-05-06 09:48:39 1060 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
- 2014-05-06 09:48:39 1060 [Note] InnoDB: Compressed tables use zlib 1.2.3
- 2014-05-06 09:48:39 1060 [Note] InnoDB: Not using CPU crc32 instructions
- 2014-05-06 09:48:39 1060 [Note] InnoDB: Initializing buffer pool, size = 128.0M
- 2014-05-06 09:48:39 1060 [Note] InnoDB: Completed initialization of buffer pool
- 2014-05-06 09:48:39 1060 [Note] InnoDB: Highest supported file format is Barracuda.
- 2014-05-06 09:48:39 1060 [Note] InnoDB: The log sequence numbers 1600677 and 1600677 in ibdata files do not match the log sequence number 1614525 in the ib_logfiles!
- 2014-05-06 09:48:39 1060 [Note] InnoDB: Database was not shutdown normally!
- 2014-05-06 09:48:39 1060 [Note] InnoDB: Starting crash recovery.
- 2014-05-06 09:48:39 1060 [Note] InnoDB: Reading tablespace information from the .ibd files...
- 2014-05-06 09:48:39 1060 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace wp182/wp_yarpp_related_cache which uses space ID: 2 at filepath: .\wp182\wp_yarpp_related_cache.ibd
- 2014-05-06 09:48:39 c78 InnoDB: Operating system error number 997 in a file operation.
- InnoDB: Some operating system error numbers are described at
- InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
- InnoDB: Error: could not open single-table tablespace file .\wp182\wp_yarpp_related_cache.ibd
- InnoDB: We do not continue the crash recovery, because the table may become
- InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
- InnoDB: To fix the problem and start mysqld:
- InnoDB: 1) If there is a permission problem in the file and mysqld cannot
- InnoDB: open the file, you should modify the permissions.
- InnoDB: 2) If the table is not needed, or you can restore it from a backup,
- InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
- InnoDB: crash recovery and ignore that table.
- InnoDB: 3) If the file system or the disk is broken, and you cannot remove
- InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
- InnoDB: and force InnoDB to continue crash recovery here.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement