Bug #58614 MySQL Server Instalation Configuration Wizard (Not Responding)
Submitted: 1 Dec 2010 2:26 Modified: 22 Jul 2015 0:14
Reporter: Robert Gebis Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Installing Severity:S2 (Serious)
Version:5.5.7-rc x64 OS:Windows (Win7 x64, XP x64)
Assigned to: CPU Architecture:Any
Tags: configuration, hangs, Windows7 x64

[1 Dec 2010 2:26] Robert Gebis
While upgrading existing 5.5.6-rc (x64), 5.5.7-rc (x64) installation was completed with out any problems, but MySQLInstanceConfig hangs after creating ini file and before starting service. Complete installation was chosen (first un-installing 5.5.6) with "Complete" installation. When MySQLInstanceConfig starts such option are selected. 

How to repeat:
Start MySQLInstanceConfig
1. Select "Detail Configuration"
2. Developer Machine
3. Multifunctional Database
4. Decision Support (DSS)/OLAP
5. Enable TCP/IP Networking with Strict Mode
6. Manual Selected Default Character : utf8
7. Install As Windows Service
8. Hangs after writing ini file and before starting service.

Starting mysqld with --console I get this

C:\Program Files\MySQL\MySQL Server 5.5\bin>mysqld.exe --console
101130 20:16:18 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use Windows interlocked functions
InnoDB: Compressed tables use zlib 1.2.3
101130 20:16:18  InnoDB: Initializing buffer pool, size = 107.0M
101130 20:16:18  InnoDB: Completed initialization of buffer pool
101130 20:16:18  InnoDB: highest supported file format is Barracuda.
101130 20:16:18  InnoDB: 1.1.3 started; log sequence number 1636721
101130 20:16:18 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.proxies_priv' doesn't exist

Suggested fix:
start mysqld from cmd.exe as
> C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld.exe --console --skip-grant-tables
in second cme.exe run
> C:\Program Files\MySQL\MySQL Server 5.5\bin\mysql_upgrade.exe
now Control-C mysqld in first cmd.exe
Start Service 
> net MySql start
[1 Dec 2010 4:13] Valeriy Kravchuk
I've seen the same problem while upgrading on 64-bit XP. Wizard should be smart enough to detect this (and either fix it as suggested or output instructions on what to do for DBA).
[1 Dec 2010 8:50] Peter Laursen
Docs are clear: http://dev.mysql.com/doc/refman/5.5/en/news-5-5-7.html

"A new mysql.proxies_priv grant table that records proxy information for MySQL accounts. 

Due to these changes, the server requires that a new grant table, proxies_priv, be present in the mysql database. If you are upgrading from a previous MySQL release rather than performing a new installation, the server will find that this table is missing and exit during startup with the following message: 
Table 'mysql.proxies_priv' doesn't exist

To create the proxies_priv table, start the server with the --skip-grant-tables option to cause it to skip the normal grant table checks, then run mysql_upgrade"

I recommend always to read release notes before installing a new version (though it is probably true that most users won't).

(not a MySQL person)
[1 Dec 2010 9:00] Peter Laursen
.. but ideally the wizard should exit with a 'graceful' error like
"servers older than 5.5.7 cannot be upgraded to 5.5.7 or higher with
this wizard. Refer <link>documentation</link> on how to perform this
[1 Dec 2010 9:06] Peter Laursen
.. actually you may skip the wizard.  So putting such inside the wizard is not the right place ... It should be last step of the MSI script rather.

"Server x.y.z has been installed, but you are upgrading from a version before 5.5.7 so a manual step is required to prepare the new server before it can be started.  Please refer ... (or 'show full details' option)"
[2 Dec 2010 15:46] Lawrenty Novitsky
I'm observing the same bug. But I can see that table proxies_priv is created, but in a wrong place. it is created in .../Program Files/.../data/mysql
while generated my.ini points to ...ProgramData/.../data
I'm not sure is that about upgrading - first time i was upgrading in indeed, but after that i deinstalled/installed many times with same result.
i'm on vista64, was installing 5.5.7-64bit
[7 Dec 2010 15:18] Reggie Burnett
Oops.  Sorry, I set the status correctly but the canned response is wrong.  Please disregard the last response to this bug report.

We are no longer developing the config wizard and are instead replacing that tool in the 5.6 timeframe.  Please stay tuned for more information.
[7 Dec 2010 15:43] Peter Laursen
@Reggie .. aren't MySQL Administrator and MySQL Query Browser deprecated now?

Looks to me like you took the wrong standard reply here!
[7 Dec 2010 15:46] Peter Laursen
hmmm .. looks like what I replied to has gone!

I think this bugs system sometimes mismatches threads!
[18 Dec 2010 18:59] Robert Gebis
5.5.8 builds and works fine.
[18 Dec 2010 19:52] Peter Laursen
@Robert .. yes.  Because you now upgraded from 5.5.7 to 5.5.8.  It would not (I think) if you upgraded from 5.5-6 (or lower) to 5.5.8.
[20 Dec 2010 14:43] Robert Gebis
I understand. I was aware of the upgrade from x.6 to x.8. Just wanted to report that @ least that part is ok :)

[22 Jul 2015 0:13] Jose Gabriel Valencia Ornelas
Posted by developer:
in latest Installer 1.4.9 the configuration wizard take care and initialize the server using the skip-grant-tables and then execute the mysql-upgrade utility, even that the isntaller doesn't work with any server older than 5.5.16, was tested isntalling 5.5.16 and then upgrade to 5.6.44 this is the log, this bug looks to be obsolete

Beginning configuration step: Stopping Server [if necessary]
Ended configuration step: Stopping Server [if necessary]

Beginning configuration step: Updating server
Attempting to run mysql_upgrade.exe
Running process: C:\Program Files (x86)\MySQL\MySQL Server 5.5\bin\mysqld.exe --defaults-file="C:\ProgramData\MySQL\MySQL Server 5.5\my.ini" --skip-grant-tables --console
150721 18:59:12 [Note] C:\Program Files (x86)\MySQL\MySQL Server 5.5\bin\mysqld.exe (mysqld 5.5.44-enterprise-commercial-advanced-log) starting as process 22784 ...
Looking for 'mysql.exe' as: C:\Program Files (x86)\MySQL\MySQL Server 5.5\bin\mysql.exe
Looking for 'mysqlcheck.exe' as: C:\Program Files (x86)\MySQL\MySQL Server 5.5\bin\mysqlcheck.exe
Running 'mysqlcheck' with connection arguments: "--host=localhost" "--port=3306" 
Running 'mysqlcheck' with connection arguments: "--host=localhost" "--port=3306" 
mysql.columns_priv                                 OK
mysql.db                                           OK
mysql.event                                        OK
mysql.func                                         OK
mysql.general_log                                  OK
mysql.help_category                                OK
mysql.help_keyword                                 OK
mysql.help_relation                                OK
mysql.help_topic                                   OK
mysql.host                                         OK
mysql.ndb_binlog_index                             OK
mysql.plugin                                       OK
mysql.proc                                         OK
mysql.procs_priv                                   OK
mysql.proxies_priv                                 OK
mysql.servers                                      OK
mysql.slow_log                                     OK
mysql.tables_priv                                  OK
mysql.time_zone                                    OK
mysql.time_zone_leap_second                        OK
mysql.time_zone_name                               OK
mysql.time_zone_transition                         OK
mysql.time_zone_transition_type                    OK
mysql.user                                         OK
Running 'mysql_fix_privilege_tables'...

Stopping server process: C:\Program Files (x86)\MySQL\MySQL Server 5.5\bin\mysqld.exe --defaults-file="C:\ProgramData\MySQL\MySQL Server 5.5\my.ini" --skip-grant-tables --console
Finished running mysql_upgrade.exe
Ended configuration step: Updating server

Beginning configuration step: Starting Server
Starting MySQL as a service
Ended configuration step: Starting Server

Beginning configuration step: Updating Start Menu Link
Attempting to verify command-line client shortcut.
Verified command-line client shortcut.
Ended configuration step: Updating Start Menu Link