MySQL Bugs: #23822: Administrator

Bug #23822	Administrator
Submitted:	31 Oct 2006 23:41	Modified:	4 Dec 2006 22:58
Reporter:	Jared S (Silver Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.2.5 BETA	OS:	Windows (WinXP)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any
Tags:	administrator, interactive_timeout, startup variables

Description:
Few issues here with changing couple of Advanced network options.  

1. Changing interactive_timeout=30 will actually change it to 1000000(1 Million)
2. Changing interactive_timeout will 'Hash out/comment' all previous startup variable in my.ini that were set using config wizard
3. Changing interactive_timeout will cause service not to start properly

How to repeat:
> Administrator
> Startup Variables
> Advanced networking
> Interactive_timeout=30
> refresh service if you like
> check my.ini file to see value of 1000000?

NOTE service may not start correctly?

Suggested fix:
Spend some time on windows machine ensure changing the most basic of variables settings work as you would expect.

Thank you for the bug report. On my side the my.ini file was updated as:

#The number of seconds the server waits for activity on an interactive connection before closing it.
interactive_timeout=30

c:\mysql\bin>mysql -uroot
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 2
Server version: 5.0.26-community-nt MySQL Community Edition (GPL)

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> show variables like "interactive_timeout";
+---------------------+-------+
| Variable_name       | Value |
+---------------------+-------+
| interactive_timeout | 30    |
+---------------------+-------+
1 row in set (0.00 sec)

mysql>

However I was unable to re-start the service with MySQL Administrator.

I cannot reproduce any of the mentioned problems. What I tried was:

1) Rename my.ini in the 5.0 server folder (I have several servers installed, but considered only 5.0 here).
2) Run config wizard in the bin folder.
3) Selected the 5.0 instance and set the port number and a few other options again.
4) Let the wizard start the server.
5) Go to MA, Advanced Networking, and set interactive_timeout to 30. Applied the changes.
6) Went back to the server folder and looked in my.ini.

What I saw was exactly two lines that have been changed (actually added):

#The number of seconds the server waits for activity on an interactive connection before closing it.
interactive_timeout=30

That's it. No other changes were made. Can you try the same and let me know the outcome?

Should of made my version more clear, they are..

MySQL 5.0.27 for windows (important)
MySQL GUI-TOOLS 1.2 BETA

The INI file is not the problem here (besides the fact everythine gets hashed out).  The real probelm is when I run following query..

SHOW VARIABLES LIKE 'interactive_timeouet';

----------------------+--------------
interactive_timeout   | 1000000

Can I expect you to fix the server restarting issue also?

Jared, I suspect the server starting problem to be something caused by earlier problems, so I would like to focus on variables and the ini file. The interactive_timeout value is a very special case as it is set (per session, to one million) in our code, hence the large value. However I think this is not a good idea for several reasons so I removed that line and found that the show variables command now returns the correct value. However I could see the 1 Mio value only in Query Browser, as it uses our common C library too. The command line client was not involved.

Aside from that I have trouble to reproduce any of the other problems you mentioned. Particularly the wrong handling of entries in the ini file sounds very strange. Can you attach a "before" and an "after" variant of your ini file that shows the problem? Please do as few as possible and explain exactly what you did to get the wrong result. I'll be hopefully able to reproduce it here too and once I can it'll easy to fix it.

Hi Mike,

I realize now interactive_timeout is not the setting causing me headaches when my software bombs out overnight.  Specifically, this overnight issue will be resolved the .NET connector bug I have also submitted.  Thank you for fixing 1 Million problem though.

When I change interactive_timeout all previous INI setting are hashed out.  I am sure that you could of repeated that but I will now attach the files.

Thanks for help on all issues!
Jared

Before and after as requested.

Attachment: INI.Files.zip (application/x-zip-compressed, text), 7.16 KiB.

Ounce you fixed up the INI file bug do you think you could take a look at the setting of wait_timeout.

The only way to set this server variable in Query Browser or an INI file is to set the interactive_timeout first and have value applied from that variable.

I think it needs to be independant.

Jared, I'm sorry but I cannot reproduce this problem whatever I try. For me MA works just as expected. The ini file is updated just as expected. Unfortunately I ran out of ideas what else I could do. So I give this issue report back to Miguel. Maybe he finds a way to reliably reproduce the error. (I assume you tried the latest release already, since you changed the version number for the report.)

For the wait_timeout: what are you talking about? You haven't mentioned a problem regarding wait_timeout yet here. So what is this about? Please do not report more than one issue per bug report.

Hi,

Is anybody looking at the following issue?

2. Changing interactive_timeout will 'Hash out/comment' all previous startup
variable in my.ini that were set using config wizard. (Have supplied sample INI files)

Also, I notice code changes have been made but it would now appear that I was selecting session variable when I should of been selecting global variable.  Maybe Mike may just want to double check.

Thanks
Jared

Hi,  Am closing bug of cause I think I got session and global variables mixed up.  As for other issue of My.IN I have seperated into another bug submission.