MySQL Bugs: #65352: In Workbench Server Administration, setting general-log crashes MySQL on restart

Bug #65352	In Workbench Server Administration, setting general-log crashes MySQL on restart
Submitted:	17 May 2012 16:24	Modified:	7 Sep 2012 16:25
Reporter:	Alan Lewis	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	Workbench 5.2.37, 5.2.40	OS:	Microsoft Windows (XP, to administrate MySQL server on Centos 6)
Assigned to:		CPU Architecture:	Any

Description:
In MySQL Workbench Server Administration, setting general-log in the Options File/Log File tab puts a line "general-l" into /etc/my.cnf, which crashes MySQL on restart with "ambiguous option --general-l". The correct line should of course be "--general-log"

How to repeat:
Run MySQL as a service on Linux (only tried on Linux Centos 6) Set up MySQL Workbench on a Windows XP machine on the local LAN and set up for Server Administration. In the CONFIGURATION/Options File select the Log Files tab and check the first option "general-log" and click Apply ... The popup shows +log-error = but the value inserted into /etc/my.cnf in the server machine is truncated to general-l. All other tabs and options tried work correctly.

Suggested fix:
Update /etc/my.cnf manually with the correct line "general-log" in place of "general-l".

Please, check if the same problem still happens with a newer version, 5.2.40.

Thank you for the prompt reply. With version 5.2.40 the popup says correctly +general-log but /etc/my.cnf is not changed when you click apply. Selecting or de-selecting general-log with the workbench now does nothing. The problem is with the Workbench since the general-log can be switched on and off by changing my.cnf manually, it just doesn't work from the Workbench.

Running MySQL Workbench on local host, the Centos server that is the MySQL host, everything is 100%. The problem only occurs running the Workbench on an XP machine on the local network for remote administration, which is what I need to do to avoid logging on to the server.

Please try version 5.2.41. Thanks.

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".