MySQL Bugs: #53763: Create new server instance profile /etc/my.cnf does not exist

Bug #53763	Create new server instance profile /etc/my.cnf does not exist
Submitted:	18 May 2010 20:11	Modified:	9 Jan 2015 15:55
Reporter:	Bishnu Timalsina	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S4 (Feature request)
Version:	10.6.3	OS:	MacOS
Assigned to:		CPU Architecture:	Any
Tags:	server instance profile

Description:
While creating a New Server Instance Profile, WB looks for /etc/my.cnf file and throws file does not exist error message.

It is default installation of MySql 64bit OS X 10.6 dmg package. I looked into /etc/ for my.cnf which does not exist.

How to repeat:
Default installation of MySql community server OS X 10.6 64bit package. Default installation of Workbench. Create New Server Instance under Server Administration.

Error message

Attachment: Screen shot 2010-05-18 at 12.43.21 PM.png (image/png, text), 100.25 KiB.

/etc/my.cnf is just a usual location of configuration file with global options (see http://dev.mysql.com/doc/refman/5.1/en/option-files.html). 

Yes, when you install from .dmg it is NOT created (no my.cnf is created at all), but Workbench should start looking for configuration file with something, and it starts with /etc/my.cnf as usual, documented location. You can create configuration file in any location and set your instance accordingly in Workbench.

To summarize: if you suggest to start with no path for my.cnf if .dmg profile is selected for a new instance on Mac OS X, that would be a feature request, and I see no big need to implement it. If you suggest something better, please, describe in details.

I am making it a feature request.

Thank you.

I just tested on Linux and the following worked fine.

Please test on MAC.

When you configure your instance ....
(CREATE NEW INSTANCE or MANAGE SERVER INSTANCE)

You can set where to find my.cnf.

If my.cnf is not existing the test/check will fail but this doesn't matter.

You put there /etc/my.cnf or whatever path is necessary that the server will find the configure file.

When you know want to configure your server and create a my.cnf then you can do it with Workbench Administrator.

You just click on whatever you want to set in Administrator -> configuration.

After you pressed APPLY ...

If Workbench can't find /PATH/my.cnf it will create it.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

I have noticed the issue while configuring MySQL Workbench on Linux Mint:
MySQL is looking for the configuration file in /etc/, although it is located in /etc/mysql/.

I have copied the my.cnf file to /etc/ then the configuration succeeded.
Here is my specific configuration:
#
Remote management is disabled

MySQL Configuration
    MySQL Version:  5.5.29-0ubuntu0.12.10.1
    Settings Template:  Generic Linux (MySQL tar package)
    Path to Configuration File:  /etc/my.cnf
    Instance Name in Configuration File:  mysqld

Commands for MySQL Management
    Start MySQL:  /etc/init.d/mysql start
    Stop MySQL:  /etc/init.d/mysql stop
    Check status:  ps -C mysqld -o pid=
    Use sudo:  Yes
#

Changed to Feature request since original reporter was for MAC OS X