MySQL Forums
Forum List  »  InnoDB

BUG IN VERSIONE 5.7.3-M13
Posted by: massimo mico
Date: December 06, 2013 06:33AM

I've installed a version 5.7.3-m13 of mysql server, and use a same configuration of my previous installation version 5.7.2, but i see on server log Always the same error on database start.

server log:
013-12-06T12:06:26.140880Z 0 [Note] Giving 0 client threads a chance to die gracefully
2013-12-06T12:06:26.141857Z 0 [Note] Shutting down slave threads
2013-12-06T12:06:26.143810Z 0 [Note] Forcefully disconnecting 0 remaining clients
2013-12-06T12:06:26.144786Z 0 [Note] Event Scheduler: Purging the queue. 0 events
2013-12-06T12:06:26.147716Z 0 [Note] Binlog end
2013-12-06T12:07:12.195550Z 0 [Note] Plugin 'FEDERATED' is disabled.
2013-12-06T12:07:12.199456Z 0 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-06T12:07:12.199456Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-06T12:07:12.202385Z 0 [Note] InnoDB: Uses system mutexes
2013-12-06T12:07:12.203362Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-06T12:07:12.209221Z 0 [Note] InnoDB: Number of pools: 1
2013-12-06T12:07:12.213127Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-06T12:07:12.216056Z 0 [Note] InnoDB: Initializing buffer pool, total size = 1.0G, instances = 3
2013-12-06T12:07:12.405497Z 0 [Note] InnoDB: Completed initialization of buffer pool
2013-12-06T12:07:12.442604Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-06T12:07:12.460181Z 0 [Note] InnoDB: The log sequence numbers 87594636 and 87594636 in ibdata files do not match the log sequence number 88411279 in the ib_logfiles!
2013-12-06T12:07:12.463111Z 0 [Note] InnoDB: Database was not shutdown normally!
2013-12-06T12:07:12.464087Z 0 [Note] InnoDB: Starting crash recovery.
2013-12-06T12:07:12.465064Z 0 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-06T12:07:13.279465Z 0 [Note] InnoDB: Restoring possible half-written data pages
2013-12-06T12:07:13.280441Z 0 [Note] InnoDB: from the doublewrite buffer...
2013-12-06T12:07:14.174915Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2013-12-06T12:07:14.177845Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2013-12-06T12:07:14.178821Z 0 [Note] InnoDB: Setting file ".\ibtmp1" size to 24 MB
2013-12-06T12:07:14.179798Z 0 [Note] InnoDB: Database physically writes the file full: wait ...
2013-12-06T12:07:14.558680Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2013-12-06T12:07:14.560633Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2013-12-06T12:07:14.693437Z 0 [Note] InnoDB: Waiting for purge to start
2013-12-06T12:07:14.777416Z 0 [Note] InnoDB: 5.7.3 started; log sequence number 88411279
2013-12-06T12:07:14.785228Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
2013-12-06T12:07:14.787181Z 0 [Note] IPv6 is available.
2013-12-06T12:07:14.789134Z 0 [Note] - '::' resolves to '::';
2013-12-06T12:07:14.790110Z 0 [Note] Server socket created on IP: '::'.
2013-12-06T12:07:14.802805Z 0 [Note] Event Scheduler: Loaded 0 events
2013-12-06T12:07:14.804758Z 0 [Note] C:\MySQL\bin\mysqld: ready for connections.
Version: '5.7.3-m13' socket: '' port: 3306 MySQL Community Server (GPL)

Options: ReplyQuote


Subject
Views
Written By
Posted
BUG IN VERSIONE 5.7.3-M13
1650
December 06, 2013 06:33AM
699
December 07, 2013 01:27PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.