Bug #23885 MySql Administrator comments out all [mysqld] settings in my.ini
Submitted: 2 Nov 2006 13:16 Modified: 6 Dec 2006 10:33
Reporter: Michael King Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Administrator Severity:S2 (Serious)
Version:GUI tools 5.0 r5 OS:Windows (Windows XP SP2)
Assigned to: CPU Architecture:Any

[2 Nov 2006 13:16] Michael King
Description:
Mysql Server 5.0.27, GUI tools 5.0 r5

When I make a change to the startup variables in MySql Administrator, all [mysqld] section settings are commented out and the changed setting is added at the end of the my.ini file.

Once this happens, any attempt by MySql server, client or Adminstrator to read my.ini causes an error (service doesn't start, client cannot connect etc).

How to repeat:
Install MySql 5.0.27

Install GUI Tools 5.0 r5

Change a startup variable (say connection timeout) in MySql Administrator, Apply changes and exit.

Check the my.ini file or run mysql client or go back into MySql administrator.
[2 Nov 2006 16:08] RUDOLF H��CKEL
A change of innodb_buffer_pool_size and innodb_lo_file_size has the same effect regardless of bigger or smaller values
[3 Nov 2006 7:42] Sveta Smirnova
Thank you for the report.

Please, provide content of your configuration file.
[3 Nov 2006 7:48] Sveta Smirnova
There is similar Bug #23906
[3 Nov 2006 11:23] Per Engh
Just to confirm the same behavior. Seems like its connected to the fact that the ini file is not reflected on the GUI. Same goes for r4, but in r4 the settings in the ini file are not commented out.

PE
[3 Nov 2006 13:41] Michael King
**** Extract before change ****
[mysqld]

# The TCP/IP Port the MySQL Server will listen on
port=3306

#Path to installation directory. All paths are usually resolved relative to this.
basedir="C:/Program Files/MySQL/MySQL Server 5.0/"

#Path to the database root
datadir="C:/Program Files/MySQL/MySQL Server 5.0/Data/"

# The default character set that will be used when a new schema or table is
# created and no character set is defined
default-character-set=latin1

# The default storage engine that will be used when create new tables when
default-storage-engine=MyISAM

# Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
max_connections=100

**** Extract after changing wait-timeout ****
[mysqld]

# The TCP/IP Port the MySQL Server will listen on
#port=3306

#Path to installation directory. All paths are usually resolved relative to this.
#basedir="C:/Program Files/MySQL/MySQL Server 5.0/"

#Path to the database root
#datadir="C:/Program Files/MySQL/MySQL Server 5.0/Data/"

# The default character set that will be used when a new schema or table is
# created and no character set is defined
#default-character-set=latin1

# The default storage engine that will be used when create new tables when
#default-storage-engine=MyISAM

# Set the SQL mode to strict
#sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

# The maximum amount of concurrent sessions the MySQL server will
# allow. One of these connections will be reserved for a user with
# SUPER privileges to allow the administrator to login even if the
# connection limit has been reached.
#max_connections=100
[3 Nov 2006 19:22] Sveta Smirnova
I can not repeat issue using self setting and information you provided.

Is it whole content of your configuration file? How many servers do you run?
[3 Nov 2006 20:21] Michael Ennis
I have the exact same problem happening with all entries in ini file being commented out.  In my case I was trying to enable old passwords.  After doing so I would get an error when trying to login to the Administrator that the "server or services could not be located".  I'd then look at the contents of the ini file and find all entries except the old passwords entry had been commented out.  Also, when I would reinstate a backup version of the proper ini and manually add the old passwords entry, when navigating to the proper page in Administrator, the checkbox for Old Passwords would NOT be selected as it should be if the ini contained this entry.  I think this might be related to Per Engh's entry above.

Thx,
Mike
[6 Nov 2006 12:55] Michael King
The extract provided is just a portion of the my.ini - but, to confirm, all settings under [mysqld] are commented-out, apart from the setting being changed (which is added at the end of the file).

In this case, I am running everything on one machine for development purposes.

Thanks
[13 Nov 2006 18:05] Sveta Smirnova
Please provide entire my.ini file: I can not repeat using part you provided.
[15 Nov 2006 18:24] Michael King
my.ini before Administrator change

Attachment: my.ini (application/octet-stream, text), 9.05 KiB.

[15 Nov 2006 18:26] Michael King
my.ini after changing wait-timeout to 120

Attachment: my.ini (application/octet-stream, text), 9.18 KiB.

[23 Nov 2006 10:08] Yahoo Serious
See also Bug #23822
[23 Nov 2006 10:15] Yahoo Serious
See also Bug #24019
[23 Nov 2006 14:18] Yahoo Serious
I can repeat it, with:
 - Windows SP2000 SP4
 - MySql Server 4.1.21 (no bug on 5.0.27 !)
 - MySql Administrator 1.2.5 rc

I will post <my.ini.right>, put this as <my.ini> in the MySql-install-directory.
 - start MySql Server 
 - start MySql Administrator
 - Go to "Startup variables" > "Performance"
 - Change "Query cache" e.g. to "50k"
 - exit MySql Administrator
 - check that <my.ini> now looks like posted <my.ini.wrong> 
   with many (but not all) commented parameters
(- try to start MySql Administrator and notice Bug #24019)
[23 Nov 2006 14:29] Yahoo Serious
I had to start a new bug, since only registered developers and the original submitters are allowed to attach files to the bug, and I can't add the files textually, as the contents are too long to post.
The files are at: Bug #24545 .
[23 Nov 2006 22:41] Jared S
I also confirm this bug using GUI-TOOLS 1.2.5 BETA and MySQL Server 5.0.27 on Windows XP with Standard configuration with no root password.

Michael King:
-------------
You sound like a .NET programmer who is having the problem of .NET Connector throwing an error after 8 hours of innactivity.  Much to my suprise this error can be discarded as I don't think it effects the last command executed.  See http://bugs.mysql.com/bug.php?id=23825.
[24 Nov 2006 19:06] Jared S
INI files are still bieng commented out in Administrator 1.2.6 BETA
[4 Dec 2006 16:15] Mihai Sorin Dobrescu
Hello,

I use MySQL 5.0.27-community-nt, Client Version 5.1.11 and MySQL Tools 1.2.6rc.
The settings are reset and I guess the cause might be the GUI of the Administrator tool that doesn't detect properly the changed attributes or doesn't load the settings from the my.ini file. Is this because of different paths used for 5.0 and 5.1 versions of the server? I don't know, but I hope I've been given you enough hints to start.

Thanks and best regards,
Mike
[5 Dec 2006 20:38] Sveta Smirnova
I still can not repeat described behaviour.

Please describe how you installed MySQL GUI Tools? Using installer wizard or zip archive?
[5 Dec 2006 21:13] Sveta Smirnova
Bug #24806 was marked as duplicate of this one
[5 Dec 2006 22:41] Jared S
Hi Sveta,

I will now post all comments to this original bug 23885.  Could you please uninstall your copy of GUI-TOOLS and reinstall from this link (as I know I do have the problem)..

http://dev.mysql.com/get/Downloads/MySQLGUITools/mysql-gui-tools-5.0-r6-win32.msi/from/htt...

May be a currupt installer, have had issues with WinRAR3.60 myself.  Just follow the wizard, I will also post image of commponents you should install with.
[5 Dec 2006 22:44] Jared S
Dam bug tracker wont let me add file.  Please try Custom install with following components..

-Common Components
-MySQL Administrator
-MySQL Query Browser

(no others!)

PS. This bug is always in 'Need feedback' status, probably because original poster is no longer participating.
[6 Dec 2006 10:33] Sveta Smirnova
There is similar verified bug #24824.

Altough that bug has been submitted after this one I'll leave that Verified and mark this as Duplicate.
[2 Aug 2009 22:51] Hongyan Li
I had the same error message. In my case, it was because I had an old MySQL service as part of hMailServer. There may have been a port conflict. I uninstalled hMailServer and its MySQL server, and now it is not giving me the error any more. I guess, it would have worked too if I had changed the port to something else. In light of this, in my opinion, this would not be such a nasty issue if the error message is more accurate.