MySQL Bugs: #56987: config file

Bug #56987	config file
Submitted:	23 Sep 2010 21:53	Modified:	13 Dec 2010 13:25
Reporter:	Uwe Thormann	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.28	OS:	Any
Assigned to:	Mike Lischke	CPU Architecture:	Any
Tags:	config file

Description:
Hi,

while installation of Workbench, it is not possible to access configfile. Is that a problem?

mysql 5.1 on windows 7, worbench 5.2.28

Yours
Uwe

How to repeat:
install mysql
install worbench over msi

Thank you for the bug report. Which config file are you referring (my.ini)?. Thanks in advance.

Hi,

yes, I think my.ini is the file. It is under c:\Program Files\MySQL\Mysql Server 5.1\.

In MySQL Workbench 5.2.26, Server Administration/Configuration is no access to this file.  The error message is IOError: invalid mode ('r') or filename: u". In opened File (MS-Editor) i see wrong entry for my data-directory for example.

But under Linux i see the config file is my,cnf!. What's that? I think i have a Beginners Problem...

Uwe

I face the same issue with both MySQL 5.1.50 and 5.5.6 running on local machine on port 3306 and 3307 respectively (and I told in another report). Service names are 'msyql51' and 'mysql55' (but probably this does not matter). The ini is in installdir and created by the config wizard (with only max_allowed_packed and lower_case_table_names settings edited manually (from Notepad/PSPad - not from WB)

I will upload an image in next comment.

when registering new instance wizard cannot find my.ini

Attachment: new.jpg (image/jpeg, text), 45.10 KiB.

Thank you for the feedback.

I have found the error.

Assumtion - most IT will STEP through the process selecting options as they proceed - conections, Transactional, etc.

The INSTALL therefore creates a 'CUSTOM' install.

When creating a @localhost instance for Workbench (assuming mysql is running) the wizard skips over the MANAGEMENT and OS section because it is a localhost

As such a PROFILE is NOT created and the config file, etc is unknown.

On completion of the wizard if you go to MANAGE the instance select the SYSTEM Profile and the pick the right install package, the config is autofilled and ready for use.

Should be a simple fix to show this step it is only available when selecting and initial SSH config.

Hope this helps.

Fixed in release.

fix confirmed in repository

An entry has been added to the 5.2.31 changelog:

The MySQL Configuration file could not be accessed during MySQL Workbench installation.