MySQL Bugs: #66305: Cannot start MySQL 5.6.6 after upgrading from 5.6.5

Bug #66305	Cannot start MySQL 5.6.6 after upgrading from 5.6.5
Submitted:	10 Aug 2012 11:38	Modified:	4 Oct 2012 7:06
Reporter:	Peter Laursen (Basic Quality Contributor)	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S2 (Serious)
Version:	5.6.6	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	qc

Description:
Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle rettigheder forbeholdes.

C:\Users\Peter>net stop mysql56
Tjenesten mysql56 stopper.
Tjenesten mysql56 er stoppet.

< Here I launched the (mysql-5.6.6-m9-winx64.msi) intaller. It completed the upgrade with no errors>

C:\Users\Peter>net start mysql56
Tjenesten mysql56 starter....
Tjenesten mysql56 kunne ikke startes.

Der opstod en systemfejl.

Systemfejlen 1067 opstod.

Processen sluttede uventet.

C:\Users\Peter>

How to repeat:
see above.

Further I replaced the old my.ini (that worked fine with 5.6.5) with the my-medium.ini template shipping with 5.6.6 and the server now started.

Suggested fix:
I wonder if this is related:
http://bugs.mysql.com/bug.php?id=66303

Whatever it is I cannot find documentation for what incompatibe options taht couse this.  And ctually the old .ini was built with the configuration wizard of a previous (early) 5.6x version

this is the problematic option. Afte removing it the server starts

#Path to the database root
datadir="C:/ProgramData/MySQL/MySQL Server 5.6/Data/"

So 5.5.6 cannot start with the datdir of 5.5.5? really?

Not the only problem ... grrrr!

I am closing this.  I have messed up my files so much that I am not able to reproduce systematically now.

Opening again.  It was not the datadir.  If I insert into my-medium.ini a /datadir specification pointing the datadir used by 5.5.5 the server starts.

So some other option is incompatible. I will attach the ini that fails to work with 5.5.6, worked with 5.5.5 and was generated by an earlier 5.6x version's config wizard.

ini that does not work with 5.5.6.

Attachment: my. 2012-08-10.ini.zip (application/zip, text), 3.59 KiB.

Can you upload relevant part of the error log, since first startup of 5.6.6?

I think the culprit is this:

120810 13:53:46 [Note] Plugin 'FEDERATED' is disabled.
120810 13:53:46 InnoDB: The InnoDB memory heap is disabled
120810 13:53:46 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120810 13:53:46 InnoDB: Compressed tables use zlib 1.2.3
120810 13:53:46 InnoDB: CPU does not support crc32 instructions
120810 13:53:46 InnoDB: Initializing buffer pool, size = 128.0M
120810 13:53:46 InnoDB: Completed initialization of buffer pool
InnoDB: Error: log file .\ib_logfile0 is of different size 55574528 bytes
InnoDB: than specified in the .cnf file 5242880 bytes!
120810 13:53:46 [ERROR] Plugin 'InnoDB' init function returned error.
120810 13:53:46 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
120810 13:53:46 [Warning] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld: unknown variable 'loose-validate_password_dictionary_file=C:/Program Files (x86)/MySQL/share/dictionary.txt'
120810 13:53:46 [ERROR] Unknown/unsupported storage engine: InnoDB
120810 13:53:46 [ERROR] Aborting

.. but I will put up the complete log file

complete file

Attachment: Peter-Pc.err (application/octet-stream, text), 363.97 KiB.

So it is log file size problem, I think. But I did not change anything in configuration during the upgrade. 

I will try to rename log files and start server with old .ini.

It did not help to rename the InnoDB log files (ib_logfile0 > bak_ib_logfile0 etc.). Server still does not start with the .ini that worked as a charm with 5.6.5. "my-medium.ini" starts after deleting log files - also after adding a /datadir setting pointing to my old 5.6.5 datadir.

Thank you for the feedback.

For me this looks like free support request. Anyway we need full error log file from last failed start attempt to be able to diagnostify the reason.

I have no option to provide more details now.  I have deleted everything from 5.6.5 and installed 5-6-6 with "mysqld install servicename" command.

Thank you for the feedback.

Closed as "Can't repeat" for now. Please reopen the report if you are able to provide precise instructions of how to repeat it.

The log file size problem is a duplicate of Bug#13494.