MySQL Bugs: #53158: Monitor not able to detect a local db installation when upgrading

Bug #53158	Monitor not able to detect a local db installation when upgrading
Submitted:	26 Apr 2010 12:09	Modified:	24 May 2010 13:56
Reporter:	Roger David Nay	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Installing	Severity:	S4 (Feature request)
Version:	2.2.0.1696	OS:	Any
Assigned to:	BitRock Merlin	CPU Architecture:	Any

Description:
Changing the config.properties to a server name which resolved to a eth0:1 local address caused problems during an upgrade. (Linux).

2.1 to 2.2 upgrade.

How to repeat:
Modify config.properties to use a host name as mysql.server which resolves to the local host. The server works fine with the config.properties change, but the upgrade fails to install new version of the embedded MySQL server, and can't continue.

Workaround is to put back in the local 127.0.0.1 value for mysql.server.

Suggested fix:
Better messages or handle the resolving.

1. Tell the dba/installer that you 'think' the db instance is remote, and therefore should be upgaded to version 1.2.3 first, AND 
2. Allow the dba/isntaller to say: "I know what I want to do: please continue".

The current error message "Warning: MySQL Server version 5.1.40 or later with partitioning enabled is
required." is not that helpful.

Patch sent to Keith.

Andy Bang writes: 
In build 2.2.1.1718.

Marcos Palacios writes: 
Tested with Monitor upgrade installer build 2.2.1.1718. Test scenario as follows:

- using Mac OS X 10.5
- installed monitor build 2.1.2.1163 with local repository
- stopped the MEM tomcat and mysql
- edited config.properties to use: mysql.server=marcos-palacioss-macbook-pro.local
- restarted the MEM tomcat and mysql
- ran monitor upgrade installer build 2.2.1.1718
* results:
-- the message (pop-up) mentioned above was not shown during the upgrade install
-- the upgrade completed w/o errors on screen
-- trying to start the app failed: got 'HTTP Status 404' error on browser
-- attaching here:
  --- upgrade bitrock_installer log,
  --- MEM mysql-monitor.log which has:
      "java.lang.RuntimeException: jdbc:mysql://marcos-palacioss-macbook-pro.local:33306/mem?"



Attachment: 10374_bitrock_installer_51423.log (text/plain), 113.78 KiB.



Attachment: 10375_mysql-monitor.log (text/plain), 20.14 KiB.

See bug #52877

Marcos Palacios writes: 
Verified fixed in Monitor upgrade installer build 2.2.1.1718.

The issue was not with the installer, but with the environment (a router) which resolved the hostname to a host not authorized in the MEM repository for the user.

A note has been added to the 2.2.1 changelog: 

        When upgrading an existing &merlin_server; installation, where                                                                                     
        the MySQL database is identified as not being on the current                                                                                       
        host (either because it is on the same machine with a                                                                                              
        different IP, or a different machine), the upgrade installer                                                                                       
        would fail to provide a warning that such a MySQL database                                                                                         
        installation cannot be upgraded automatically by the                                                                                               
        installer. A warning providing more information on how to                                                                                          
        upgrade is now provided.