MySQL Bugs: #61219: Configuration File Options Missing

Bug #61219	Configuration File Options Missing
Submitted:	18 May 2011 23:07	Modified:	27 Jan 2012 6:37
Reporter:	Jake Drew	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S1 (Critical)
Version:	5.2.34	OS:	Windows
Assigned to:	Maksym Yehorov	CPU Architecture:	Any
Tags:	MariaDB

Description:
When connecting to MariaDB 5.2.6, all tabs on the edit configuration file page are blank.   

How to repeat:
1.  Open MySQL Workbench
2.  Connect to MariaDB 5.2.6 Server by double clicking the server name under "Server Administration" on the main screen.
3.  Click on "Configuration / edit configuration file" in the Server Administrator.

Suggested fix:
Change workbench to recognize 5.2.6 as a valid MySQL version number.

Thank you for the bug report. How you did the install of the MySQL Server?. Thanks in advance.

I used the MariaDB 5.2.6 windows installer exe.

Do you have Windows service created for MariaDB, and if you do, what's the name of it?

Yes, the windows service for MariaDB is named MySQL.  No other versions of MySQL are installed in the machine.  This bug seems to occur on Windows XP, 7, and server 2008 R2.

I have also tried installing the service under the name mysqlmaria52 as suggested in the MariaDB forum with no success.  I was able to install the service mysqlmaria52. However, WB does not show any configuration options as described above.

Jake, there is no point in trying out mysqlmaria52. If that does not work with "MySQL" which is by far be the most tested configuration in WB, it won't work otherwise.

Well, hopefully you guys can come up with a workaround for us then!

I am just curious what the status of this bug is?  Are there any plans to support the display of configuration options for MariaDB 5.2.xx in MySQL WB?

Jake,

status of MySQL service is not related to config file page. Can you make sure that the file specified in the server instance settings really exists?

Maksym Yehorov,  Your response does not appear to be related to the problem I have described on this bug at all.  Please take a closer look at the problem description when responding next.  

To further clarify, there is NO problem with the MySQL service.  I have no problem accessing our databases or starting and stopping the database service from Workbench.  All WB configuration options just are not displayed on the WB config screen when attaching to a MariaDB 5.2.6. I am attaching a screenshot so this will hopefully help everyone understand what the problem is.

All configuration tabs are blank. Please make 5.2.xxx a "known" version of MySQL in WB.

Attachment: wb screen shot 3.bmp (image/bmp, text), 423.33 KiB.

One need not to have mysql service running (even installed) to work with configuration file. It is only that the ini file path must be specified.

If you can provide us some additional information, pls, add env variable DEBUG_ADMIN set to 5, and attach text from Output View to this bug report.

thanks.

I can reproduce what Jake is seeing too. I assume the sysinternals DebugView output is what is meant with Debug Output windows, I'll attach that  ouptut in a second.

DebugView output

Attachment: DELLBOX.LOG (application/octet-stream, text), 11.44 KiB.

ini file

Attachment: my.ini (application/octet-stream, text), 294 bytes.

Service configuration:
C:\Users\vvaintroub>sc qc mysql
[SC] QueryServiceConfig SUCCESS

SERVICE_NAME: mysql
        TYPE               : 10  WIN32_OWN_PROCESS
        START_TYPE         : 2   AUTO_START
        ERROR_CONTROL      : 1   NORMAL
        BINARY_PATH_NAME   : "C:\Program Files (x86)\MariaDB 5.2\bin\mysqld.exe"
 "--defaults-file=C:\Program Files (x86)\MariaDB 5.2\data\my.ini" "MySQL"
        LOAD_ORDER_GROUP   :
        TAG                : 0
        DISPLAY_NAME       : MySQL
        DEPENDENCIES       :
        SERVICE_START_NAME : NT AUTHORITY\NetworkService

Output View is a Workbench thing - Ctrl-F2. The attached file seems to have the same output.

What Workbench version do you use? What Windows version do you use?

Workbench version is 5.2.31 CE Revision 7115, running on Windows 2008 R2 SP1.

I have the same problem using Workbench version is 5.2.31 CE Revision 7508, running on Windows 2008 R2 SP1, Windows 7, or Windows XP.

So far, can you try it on the latest Workbench? It is 5.2.34 when it is out.

Any estimate on a release date?

Very very soon. Due to some rules and regulations I can not disclose such a sensitive information.

5.2.34 is not available to general public, so far I can try the latest workbench available. It is 5.2.33 CE and it does not process config file, exactly as its predecessor version.

I'm quite sure it won't change in not-yet-released one.

5.2.34 did not fix it.

Workbench works as expected, it is only that the options set is dependent on a server version, so there is 1 valid option for 5.2.6 according to docteam's xml file which describes mysql options.
We will work on manual override of the version in this and similar situations.
The fix can be included in the next version.

Thank you for your support on this.  We look forward to your next version of WB!

I have the same problem on Linux.

Server configuration:
Debian 6
MariaDB 5.2.7

MySQL WB configuration:
Windows XP
MySQL WB 5.2.34 CE (Revision 7780)
Connection to server via TCP/IP over SSH

The previous version MariaDB was 5.1 and tabs with Configuration Files Option were OK. After upgrade to version 5.2, this problem appeared.

Fixed as of 5.2.35:

On Mac OS X, disabling the Enable data changes commit
wizard preference setting would not disable the
wizard.

I have not understood a word from this "disabiing enabled.. " though it seems to rhyme well.