Bug #60823 Installer issues with 5.6.2
Submitted: 10 Apr 2011 8:30 Modified: 12 Apr 2011 14:52
Reporter: Peter Laursen (Basic Quality Contributor) Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Installing Severity:S3 (Non-critical)
Version:5.6.2 OS:Windows (7/64)
Assigned to: CPU Architecture:Any
Tags: qc

[10 Apr 2011 8:30] Peter Laursen
Description:
5.6.2 from here: ftp://ftp.easynet.be/mysql/Downloads/MySQL-5.6/
During installation the installer+config wizard package fails in two places.

1) I have an 5.0, a 5.1 and a 5.5 installed in advance. It finds them all but is not able to identify service name of the 5.5 instance.  Also some are marekd wiht a red color what I do not understand the meaning of.  

2) 
During 'apply security settings' the wiozard screen hanges for long and finally reports that 'apply security settings failed

.. but 'security settings' were in fact applied what this tells:

SELECT USER, HOST FROM mysql.user;
/* returns

user    host     
------  ---------
root    localhost
*/

.. what was what I asked and also the password I specified is being set for root@localhost user.  

I am not perfectly sure if 2) is a duplciate of an existing report with previous server versions.  But I don't think I saw before that it is reported that 'apply security settings failed' when it in fact did *not* fail.

How to repeat:
I will put up an image  

Suggested fix:
Please fix all the issues with the installer packages.
[10 Apr 2011 8:31] Peter Laursen
Details for running 5.5 server cannot be identified by 5.6 installer

Attachment: servers.jpg (image/jpeg, text), 49.92 KiB.

[10 Apr 2011 15:32] Valeriy Kravchuk
Please, send the output of

sc qc <service_name>

for the Windows service that represents MySQL server 5.5. I wonder if service name is any specific and if --defaults-file is accessible to the installer.
[10 Apr 2011 15:34] Peter Laursen
Here you go:

C:\Users\Peter>sc qc mysql55
[SC] QueryServiceConfig LYKKEDES

SERVICE_NAME: mysql55
        TYPE               : 10  WIN32_OWN_PROCESS
        START_TYPE         : 2   AUTO_START
        ERROR_CONTROL      : 1   NORMAL
        BINARY_PATH_NAME   : "C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld
" --defaults-file="C:\Program Files\MySQL\MySQL Server 5.5\my.ini" MySQL55
        LOAD_ORDER_GROUP   :
        TAG                : 0
        DISPLAY_NAME       : MySQL55
        DEPENDENCIES       :
        SERVICE_START_NAME : LocalSystem

C:\Users\Peter>
[10 Apr 2011 15:38] Peter Laursen
Let my add that I have/had MySQL 5.0, 5.1, 5.5 (and now) 5.6 + MariaDB 5.2 + InfiniDB installed as services.  Except for MySQL 5.0 and InfiniDB they all start with the OS.
[12 Apr 2011 13:38] Valeriy Kravchuk
I had no real problems installing 5.6.2 on 32-bit Windows XP where 5.0, 5.1 and 5.5 are also installed:

C:\Program Files\MySQL\MySQL Server 5.5\bin>mysql -uroot -proot -P3314 test
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 2
Server version: 5.6.2-m5 MySQL Community Server (GPL)

Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql>

I had noted one red line for server version 6.0.9 that I had on this laptop long time ago. Probably some records for this version left in the registry, but red color means that wizard was not able to get all the necessary information to properly configure it. So, it is "non-functional" instance.
[12 Apr 2011 13:40] Valeriy Kravchuk
Problem with applying security settings step may be related to the fact that you had 5.6.0 installed on this machine previously. Please, confirm.

To summarize, I had not noted any *new*, yet unknown or 5.6 specific problems of .msi installer, yet.
[12 Apr 2011 13:48] Peter Laursen
1) Well .. *red* means then 'non-functional for the Wizard'.  In every other respect the 5.5 instance is indeed functional.  I do not claim that this is specific for 5.6 tree. But I did not note the *red* indication for functional instances before. I have no idea why the 5.5 instance does not show up the same details as 5.0 and 5.5. 

2) yes .. I did have 5.6.0 installed.  That was when I reported http://bugs.mysql.com/bug.php?id=56889.  But I believe it has been *completely removed* (all files, service in registry) before installing 5.5.6. But I agreee that this could be just another 'flavour' of existing reports with the configuration wizard.
[12 Apr 2011 13:52] Valeriy Kravchuk
Item 1) (why your 5.5 instance is "red") is something that we have to figure out. My 5.5.10 is not red in the wizard of 5.6.2, and I was not able to identify anything unusual/specific in "sc qc" results for 5.5 in your case. 

This can be some new bug, but I do not know yet how to repeat it.
[12 Apr 2011 14:22] Peter Laursen
Well .. you set status to 'Need Feedback'.  I do not know what more feedback I should provide now.
[12 Apr 2011 14:43] Valeriy Kravchuk
Probably I wanted to ask if 5.5.x is 32-bit or 64-bit, and is 5.6.2 you tried to install 32-bit or 64-bit (having in mind that other your bug report we discussed today).

In my case all versions were 32-bit...
[12 Apr 2011 14:44] Valeriy Kravchuk
I assume 5.5 is 64-bit (from sc qc and pathname), but what about 5.6.2?
[12 Apr 2011 14:48] Peter Laursen
ahhh ... I think you hit the nail here!

I only intend to install 64 bit servers on this system. But as we have discussed I have actually both 5.5.10 64 bit (running and functional) and 5.5.11 32 bit (what was installed by mistake and is not running and not even functional as configuration does not exist.  And no service exists for it).

So the wizard undodubtedly sees the 5.5.11 32 bit and not the 5.5.10 64bit.  So I think that this report could be marked a duplicate of http://bugs.mysql.com/bug.php?id=60830.
[12 Apr 2011 14:48] Peter Laursen
All servers except for non-functional 5.5.11 are 64 bit.
[12 Apr 2011 14:52] Valeriy Kravchuk
So, let's say, for now, that this is a duplicate of bug #60830. I see nothing 5.6.x specific here anyway.