Bug #61469 | config wizard can't start the service | ||
---|---|---|---|
Submitted: | 9 Jun 2011 23:31 | Modified: | 4 Oct 2012 7:04 |
Reporter: | Milton Mobley | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Config Wizard | Severity: | S1 (Critical) |
Version: | 5.5.13 | OS: | Windows (64-bit) |
Assigned to: | CPU Architecture: | Any |
[9 Jun 2011 23:31]
Milton Mobley
[10 Jun 2011 0:12]
MySQL Verification Team
Please look for *.err file on your install datadir directory and print here an eventual error message. Thanks.
[10 Jun 2011 22:36]
Milton Mobley
Since original report I determined that the service can be installed manually from a command window script, and then appears in the Control Panel's list of services. But when I try to start it from the same command window, as described in comments in my.ini, the service aborts. The event log shows Event ID 100 (Aborting) and an error message is displayed in the command window "System error 1067 occurred."
[11 Jun 2011 5:21]
Milton Mobley
A Microsoft support person suggested launching mysqld with --console option. I did and this is what I got: C:\Program Files (x86)\MySQL>mysqld --console ... successful steps deleted for brevity ... InnoDB: Error: log file .\ib_logfile0 is of different size 0 58720256 bytes InnoDB: than specified in the .cnf file 0 55574528 bytes! 110610 21:58:53 [ERROR] Plugin 'InnoDB' init function returned error. 110610 21:58:53 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 110610 21:58:53 [ERROR] Unknown/unsupported storage engine: INNODB 110610 21:58:53 [ERROR] Aborting 110610 21:58:53 [Note] mysqld: Shutdown complete C:\Program Files (x86)\MySQL> From my.ini: innodb_log_file_size=53M Will replacing ib_logfile0 with an all zeros file that is exactly 53M bytes fix the problem? Will I also have to fix ib_logfile1?
[11 Jun 2011 19:09]
Milton Mobley
I have overcome the problem by deleting the files with incorrect size before relaunching mysqld. Apparently ib_logfile0 and ib_logfile1 were created in a previous invocation of mysqld, probably by the msi installer. But that invocation failed due to concurrent access to the files by another program, possibly the installer or a virus checker. The size parameters used were different than in the my.ini file I used, so subsequent launches failed also. But now it seems to be working normally. Someone should verify the installer does not have these files open when it tries to launch the service.
[16 Jun 2011 15:30]
MySQL Verification Team
Thank you for the feedback.
[4 Oct 2012 7:04]
Marko Mäkelä
Duplicate of Bug#13494