MySQL Bugs: #15770: Service won't start because my.ini file wasn't configured correctly

Bug #15770	Service won't start because my.ini file wasn't configured correctly
Submitted:	15 Dec 2005 7:13	Modified:	4 Oct 2012 7:04
Reporter:	Charles Rethman	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.0.16	OS:	Windows (Windows)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
I downloaded the new release of the server, 5.0.16. I checked the download with the MD5 checksum.

I stopped the old service but forgot to remove it.

I installed and ran the config wizard but the service wouldn't start. After checking the documentation, I removed the service. Ran the config wizard again. The service still wouldn't start. Error 0.

Checked the error log. This message came up after every attempt to start:

InnoDB: Error: log file .\ib_logfile0 is of different size 0 10485760 bytes
InnoDB: than specified in the .cnf file 0 13631488 bytes!
051214 22:16:42 [ERROR] Default storage engine (InnoDB) is not available
051214 22:16:42 [ERROR] Aborting

I went into the my.ini file and changed the innodb_log_file_size variable from 13M to 10M, i.e.:

innodb_log_file_size=10M

The service starts fine after that.

Cheers,

Charles

How to repeat:
Download and install 5.0.15 and start the service.
Stop the service. (do not remove the service)
Download 5.0.16.
Install 5.0.16 and run the config wizard.
If the service doesn't start, remove the old wizard, using C:\>sc delete mysql from the command line.
Run the config wizard again.
Service doesn't start.
On the command line, go to the C:\Program Files\MySQL\MySQL Server 5.0\bin folder and type >mysqld --console, if you get the above error message, you can fix it as I did.

Suggested fix:
Go into the my.ini file and change the innodb_log_file_size variable from 13M to 10M, i.e.:

innodb_log_file_size=10M

This isn't a bug but a mix of configuration values for InnoDB (10MB)
is the default value when not specified, so when the InnoDB engine
found a different value it aborts. So you did the correct procedure
to edit the my.ini file when the server display that error message.

I'm having the same issue.  However my file size was already at 10M.  I can't get the service to start.

Another way to solve the problem is to delete the 2 log files in:

/data/_ib_logfile0
/data/_ib_logfile1

They will then be created with the correct size when starting the service.

Duplicate of Bug#13494