Bug #56387 Windows Installer does not create system tables in the data folder

• Submitted: 30 Aug 2010 19:41
• Modified: 27 Jul 2012 16:15
• Reporter: Elena Stepanova
• Status: Closed
• Category: MySQL Server: Installing
• Severity: S1 (Critical)
• Version: 5.5.6-m3
• OS: Windows
• Assigned to: Daniel Fischer
• CPU Architecture: Any
• Tags: regression

[30 Aug 2010 19:41] Elena Stepanova

Description:
After a fresh installation, data dir contains mysql folder, but it is empty. System tables are not installed, and server does not start.

All setup modes (complete, typical, custom with default folders, custom with non-default folders) are affected.
When setup is run in custom mode, it says about 'Server data files' feature that it would take 0 KB on hard drive, which turns out to be true.

This is a regression from 5.5.5-m3 where system tables were installed, although there was an issue with custom installation (bug#55169).

How to repeat:
- run MSI installer;
- check data folder after installation;
optionally:
- configure the instance;
- try to start the service.

[31 Aug 2010 10:43] Daniel Fischer

The cause is with high likelihood this push: http://pb2.norway.sun.com/web.py?template=push_details&push=1467638

Particularly:

    ADD_CUSTOM_COMMAND(
-     OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/data/mysql/user.frm
+     OUTPUT initdb.dep
      COMMAND ${CMAKE_COMMAND}
      ${CONFIG_PARAM} -P ${CMAKE_CURRENT_BINARY_DIR}/create_initial_db.cmake
      WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}/data
+     COMMAND  ${CMAKE_COMMAND} -E touch initdb.dep
+     WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}
      DEPENDS mysqld
   )

WORKING_DIRECTORY may only be given once, so the second overwrites the first, resulting in the database files being created one directory level above the intended location.

The bug isn't visible in pushbuild because mtr always creates the database from scratch and doesn't actually require the included database files to run.

I will have a fix momentarily...

[31 Aug 2010 11:07] Bugs System

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/117204

3083 Daniel Fischer	2010-08-31
      Bug#56387 Create initial database in the proper location

[31 Aug 2010 11:18] Daniel Fischer

Pushed to 5.5.6 release clone, let's see if it works. :)

[10 Sep 2010 18:51] Bugs System

Pushed into mysql-5.5 5.5.7-rc (revid:[e-mail]-20100910184813-csdto6tk4nlogrsq) (version source revid:[e-mail]-20100831090419-rzr5ktekby2gspm1) (merge vers: 5.5.6-m3) (pib:21)

[13 Sep 2010 13:49] Bugs System

Pushed into mysql-trunk 5.6.1-m4 (revid:[e-mail]-20100913103627-p2oqplu42x1gv2bd) (version source revid:[e-mail]-20100831090419-rzr5ktekby2gspm1) (merge vers: 5.5.6-m3) (pib:21)

[13 Sep 2010 13:51] Bugs System

Pushed into mysql-next-mr (revid:[e-mail]-20100913121556-sfxqlpj9kbc28kaf) (version source revid:[e-mail]-20100831090419-rzr5ktekby2gspm1) (pib:21)

[27 Jul 2012 16:15] Omer Barnir

Closing as issue no longer requires additional information for documentation