[MDEV-2454] LP:716316 - Upgrade wizard does not seem to detect manually-created mysql-5.1 instances Created: 2011-02-10  Updated: 2015-02-02  Resolved: 2012-10-04

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Philip Stoev (Inactive) Assignee: Vladislav Vaintroub
Resolution: Not a Bug Votes: 0
Labels: Launchpad

Attachments: XML File LPexportBug716316.xml    

 Description   

Here is what I did:

1. Installed mysql-5.1 from MSI in a non-default directory and skipped the config wizard. So, mysql-5.1 binaries were installed, but no service.

2. In an elevated command promt, ran mysql --install to install a service. Then started the service by using the Control Panel, specifying --skip-grant-tables and --datadir. Service runs and accepts queries.

3. Ran mariadb-5.1 MSI. Installer completed succesfully but no option to run the upgrade wizard was provided. Manually starting the wizard .exe reports "there is no service that can be upgraded", even though a MySQL service does exist, even if does not have a my.ini or registry entries outside of those managed by the service manager.

bzr version-info:

revision-id: <email address hidden>
date: 2011-02-08 13:07:31 +0100
build-date: 2011-02-10 11:35:49 +0200
revno: 2943
branch-nick: maria-5.2-windows-packaging-upgrade

host: windows 7, 32bit

 Comments   
Comment by Vladislav Vaintroub [ 2011-02-10 ]

Re: Upgrade wizard does not seem to detect manually-created mysql-5.1 instances
Philip, can you run
sc qc <servicename>
from command line and post the results here?

MySQL (or Maria) would actually start as service ( communicate with service control manager ) only in 2 cases , when service definition is either
<path\to\mysqld.exe> --defaults-file=<path\to\my.ini> <servicename>
or
<path\to\mysqld.exe> <servicename>

Comment by Vladislav Vaintroub [ 2011-02-10 ]

Re: Upgrade wizard does not seem to detect manually-created mysql-5.1 instances
Tried as described, confirm that service comes up if start parameters are set.

Still, closing as "invalid", since it appears to be too obscure (accepting objections though

Service startup parameters are not persistent in service control manager, that is one can manage to start a service once this way, but not automatically after reboot.

Comment by Rasmus Johansson (Inactive) [ 2011-02-10 ]

Launchpad bug id: 716316

Generated at Thu Feb 08 06:41:57 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.