| Bug #97263 | MySQL for Windows: Installer fails when reconfiguring server | ||
|---|---|---|---|
| Submitted: | 16 Oct 2019 20:03 | Modified: | 20 Aug 2021 18:54 |
| Reporter: | Christopher Reese | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Installing | Severity: | S2 (Serious) |
| Version: | 1.4.31 | OS: | Windows (Server 2008 R2) |
| Assigned to: | CPU Architecture: | x86 | |
| Tags: | installer | ||
[16 Oct 2019 20:03]
Christopher Reese
[17 Oct 2019 8:31]
MySQL Verification Team
Thank you for the bug report.
[22 Oct 2019 16:38]
Jose Ramirez Ruiz
After reviewing the image attached to the original MySQL Bug I was able to identify that an upgrade is indeed being attempted, however I'm still unable to reproduce the issue. I've tested configuring MySQL Server as a service and as process, in both scenarios the upgrade completes successfully. Miguel, can you provide the full list of steps to reproduce the failing connection attempt shown in your image? I can see that when the server is not running, MySQL Installer runs a mysqld process to perform the connection attempt and is successful on my side, so something must be preventing MySQL from running on your side. Christopher Please provide as much info as possible for the following questions: What version were you upgrading from? What were the configuration settings used when setting up the old MySQL 5.7 installation and what were the new configurations used for 5.7.28? Can you provide a detailed list of steps to reproduce the issue? Thanks.
[23 Oct 2019 13:27]
Christopher Reese
Hi JOSE, Upgrading Version 5.7.27 to 5.7.28, I can also reproduce the issue by doing the following: Launch MySQL Installer with 5.7.28 and click on Reconfigure Under High Availability select Standalone MySQL Server Type and Networking change Config Type to Server Computer, check TCP/IP with port of 3307, check Open Windows Firewall..., check Show Advanced and Logging Options Account and Roles, Enter MySQL Root Password Windows Service, Check Configure MySQL Server as a Windows Service, check Start the MySQL Server at System Startup, Select Custom User and enter user name and password Logging, uncheck all Advanced Option, Table Names Case - Select Lower Case Execute Hangs at Backing up MySQL Database ... -------------------------------------------------- Output of Configuration Log -------------------------------------------------- Beginning configuration step: Writing configuration file Saving installer_config.xml configuration file... Saved installer_config.xml configuration file. Ended configuration step: Writing configuration file Beginning configuration step: Backing up MySQL database Starting MySQL Server in order to run the mysql_upgrade tool. Warning: There may be some errors thrown by MySQL Server, the mysql_upgrade tool is going to be run next to attempt to fix database incompatibilities. Starting process for MySQL Server 5.7.28... Starting process with command: E:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe --defaults-file="E:\Program Files\MySQL\MySQL Server 5.7\my.ini" --console... Process for mysqld, with ID 2372, has been started successfully and is running. Successfully started process for MySQL Server 5.7.28. 2019-10-23T13:10:59.161209Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled 2019-10-23T13:10:59.161209Z 0 [Note] E:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe (mysqld 5.7.28) starting as process 2372 ... 2019-10-23T13:10:59.176809Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2019-10-23T13:10:59.176809Z 0 [Note] InnoDB: Uses event mutexes 2019-10-23T13:10:59.176809Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier 2019-10-23T13:10:59.176809Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2019-10-23T13:10:59.176809Z 0 [Note] InnoDB: Adjusting innodb_buffer_pool_instances from 8 to 1 since innodb_buffer_pool_size is less than 1024 MiB 2019-10-23T13:10:59.176809Z 0 [Note] InnoDB: Number of pools: 1 2019-10-23T13:10:59.176809Z 0 [Note] InnoDB: Not using CPU crc32 instructions 2019-10-23T13:10:59.176809Z 0 [Note] InnoDB: Initializing buffer pool, total size = 512M, instances = 1, chunk size = 128M 2019-10-23T13:10:59.254810Z 0 [Note] InnoDB: Completed initialization of buffer pool 2019-10-23T13:10:59.317211Z 0 [ERROR] InnoDB: The innodb_system data file 'ibdata1' must be writable 2019-10-23T13:10:59.317211Z 0 [ERROR] InnoDB: The innodb_system data file 'ibdata1' must be writable 2019-10-23T13:10:59.317211Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2019-10-23T13:10:59.644815Z 0 [ERROR] Plugin 'InnoDB' init function returned error. 2019-10-23T13:10:59.644815Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2019-10-23T13:10:59.644815Z 0 [ERROR] Failed to initialize builtin plugins. 2019-10-23T13:10:59.644815Z 0 [ERROR] Aborting 2019-10-23T13:10:59.644815Z 0 [Note] Binlog end 2019-10-23T13:10:59.644815Z 0 [Note] Shutting down plugin 'CSV' 2019-10-23T13:10:59.644815Z 0 [Note] E:\Program Files\MySQL\MySQL Server 5.7\bin\mysqld.exe: Shutdown complete........................ Running mysqldump tool to backup the database... Backup files will be dumped to "E:\Program Files\MySQL\MySQL Server 5.7\Backup\mysql_dump-2019-10-23T09.13.03.sql". Starting process with command: E:\Program Files\MySQL\MySQL Server 5.7\bin\mysqldump.exe --user=root --host=localhost --port=3307 --default-character-set=utf8 --routines --events --single-transaction=TRUE --all-databases --result-file="E:\Program Files\MySQL\MySQL Server 5.7\Backup\mysql_dump-2019-10-23T09.13.03.sql"... mysqldump: Got error: 1045: Access denied for user 'root'@'localhost' (using password: NO) when trying to connect Process for mysqldump, with ID 2712, was run successfully and exited with code 2. Ended configuration step: Backing up MySQL database -------------------------------------------------------- Error above showing 'ibdata1' as not writeable. ibdata1 file shows Same Local User that MySQL runs as with Full Control System is also listed with Full Control Backup process with mysqldump errors because password provided in not supplied. Any help is appreciated, Thanks in advance.
[20 Aug 2021 18:54]
Christine Cole
Posted by developer: Fixed as of the upcoming MySQL Installer 1.4.39 release, and here's the proposed changelog entry from the documentation team: MySQL Installer now uses the my.ini file to determine the location of a data directory, which permits MySQL Installer to recognize a new path if the directory path is changed manually. Previously, specifying an alternative directory path was permitted only during the initial installation of a server. Thank you for the bug report.
