Bug #32354 start mysql server failures by instance manager
Submitted: 14 Nov 2007 7:53 Modified: 27 Feb 2008 14:42
Reporter: ming lu Email Updates:
Status: Won't fix Impact on me:
None 
Category:Instance Manager Severity:S2 (Serious)
Version:5.1.21, 5.1 BK OS:Any
Assigned to: CPU Architecture:Any
Triage: D2 (Serious)

[14 Nov 2007 7:53] ming lu
Description:
I start the mysql server failured by instance manager. I find the error may be caused by the my.ini file, it includes some contents like this:
 
innodb_data_home_dir=
innodb_data_file_path=c:\data1\ibdata1:18M;c:\data2\ibdata2:18M

I start the mysql server successfully by mysql administrator using the same my.ini file.

How to repeat:
Add the following setting into my.ini file, then start the mysql server by instance manager.

innodb_data_home_dir=
innodb_data_file_path=c:\data1\ibdata1:18M;c:\data2\ibdata2:18M
[14 Nov 2007 8:51] Sveta Smirnova
Thank you for the report.

Verified as described.
[14 Nov 2007 8:52] Sveta Smirnova
Corresponding part of error log:

071114 11:49:48  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
InnoDB: File name --innodb_data_file_path=/Users/apple/Applications/mysql-5.0/data/ibdata2:20M;/ibdata1
InnoDB: File operation call: 'create'.
InnoDB: Cannot continue operation.

real setting was

innodb_data_file_path=/Users/apple/Applications/mysql-5.0/data/ibdata2:20M;
[27 Feb 2008 14:42] Konstantin Osipov
Instance Manager is deprecated in 5.1 and discontinued in 6.0