Bug #12412 Displayed Service Features on Service Control page are incorrect
Submitted: 6 Aug 2005 10:21 Modified: 4 Aug 2006 16:01
Reporter: Paul van Rossem Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.0.21, 1.1.1, 1.1.2 OS:Windows (Windows XP)
Assigned to: Michael G. Zinner CPU Architecture:Any
Tags: Server Configuration

[6 Aug 2005 10:21] Paul van Rossem
Description:
Changing the service features on Service Control page has no effect. 
This bug already also exists in many previous versions.

How to repeat:
Start Administrator. Select Service Control. Switch to "Configure Service" tab. The Service feature section below has always the "Debug Information (slow)" checkbox selected.
Deselect this checkbox, for instance only select "Support for InnoDB" checkbox.
Click ApplyChanges. Close Administrator. Retart Administrator. Select Service Control. Switch to "Configure Service" tab. The Service feature section below again has always the "Debug Information (slow)" checkbox selected.
Conclusion: the applied changes are not read correctly by Administrator or making a change has no effect.

Suggested fix:
Make sure that the applied changes are read correctly by Administrator and making a change has the desired effect.
[6 Aug 2005 10:47] Jon Stephens
I cannot reproduce this bug. The Service Features selection works pefectly: the correct binary (-max/-max-nt/-debug/[standard]) is selected, and that binary is used once the server is restarted. If the "browse" button is used to select the binary, the appropriate Feature options are checked/unchecked.

Using MA 1.0.21 with MySQL 5.0.10-beta "noinstall" distribution. Win2K Server/SP4.

What version of MySQL is being used, and which binaries are present in the MySQL installation directory?
[6 Aug 2005 11:32] Paul van Rossem
The binary selected is completely different, namely 
C:\Program Files\MySQL\Server\bin\mysqld

Using MA 1.0.21 with MySQL 5.0.10-beta "install" distribution. Running on Windows XP Home.

The binaries I found are: 
libmySQL.dll, myisamchk.exe, myisamlog.exe, myisampack.exe, myisam_ftdump.exe, mysql.exe, mysqladmin.exe, mysqlbinlog.exe, mysqlcheck.exe, mysqld-debug.exe, mysqld-max-nt.exe, mysqld-max.exe, mysqld-nt.exe, mysqld.exe, mysqldump.exe, mysqlimport.exe, MySQLInstanceConfig.exe, mysqlshow.exe, mysqltest.exe, mysql_client_test.exe, my_print_defaults.exe, perror.exe, replace.exe.
[6 Aug 2005 21:57] Peter Laursen
did you stop and restart MySQL server after applying the change ?
[7 Aug 2005 5:58] Paul van Rossem
Restarting the service or not makes no difference.
[7 Aug 2005 6:31] Jon Stephens
FYI, I have the server installed to C:\mysql, data directory is M:\mydata (different physical drive), MA installation directory is C:\Program Files\MySQL\MySQL Administrator 1.0.

I have also repeated the test on a different Win2K Server machine using MA 1.0.21 with MySQL 4.1.13a (noinstall distribution), MySQL directory is C:\mysql, data directory is C:\mysql\data, MA installation directory is C:\Program Files\MySQL\MySQL Administrator 1.0.
[12 Aug 2005 17:28] Jorge del Conde
Thanks for your bug report.  I was able to reproduce this bug using MA 1.1.1
[7 Sep 2005 14:53] Vladimir Kolesnikov
Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://www.mysql.com/doc/en/Making_trace_files.html

Once you have generated a backtrace, please submit it to this bug
report and change the status back to 'Open'. Thank you for helping
us make our products better.

Additional info:

Hi Paul,

is your MySQL Server installed as a Windows service or as an application. To check this please open Start->Settings->Control Panel->Administrative Tools->Services and look for service with name containing MySQL (it can be MySQL<version-num> or simply MySQL). 

Also please check that the service is running when you encounter this bug.

Thanks.
[8 Sep 2005 19:55] Paul van Rossem
The server is running as a service, named "MySQL". It is running when I encounter this bug. 

However: I discovered that changing the service features checkboxes  on Service Control page *does* have the desired effect. It just doesn't show up on the Service Control page. 
For instance: after unchecking the debug option, stopping and restarting the service, closing administrator and restarting administrator, the debug option on the Server Features page is checked again, although *mysqld* is running, not *mysqld-debug*. So changing the service features is working properly. 
But the information is just not *shown* properly on the service control page after re-opening this page: the wrong Server Features checkboxes are checked and the path to binary is wrong.
[8 Oct 2005 3:24] MySQL Verification Team
I was unable for to repeat the issue how reported the checkbox
Debug Information (slow) only is enabled if Path to Binary
is changed to debug server. The service was modified as expected,
howver the my.ini file was not edited with the debug option for to
create the mysqld.trace file when Debug Information (slow) is
checked. For this reason I am changing status as verified.
[4 Aug 2006 16:01] Michael G. Zinner
A fix for this bug is now commited to the source repository. There were several issues with the service code which now should be addressed.

Please note that the service section does not automatically change the Startup Variables. The user has to enable options there if he wants them to be set.