MySQL Bugs: #53557: MEM installer does not give useful message when upgrading if db backend is down

Bug #53557	MEM installer does not give useful message when upgrading if db backend is down
Submitted:	11 May 2010 9:12	Modified:	24 May 2010 13:51
Reporter:	Roel Van de Paar	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Enterprise Monitor: Installing	Severity:	S3 (Non-critical)
Version:	2.2.0.1709	OS:	Any
Assigned to:	Andy Bang	CPU Architecture:	Any

Description:
Using mysqlmonitor-2.2.0.1709-linux-x86_64-update-installer.bin

Previous Installation [/opt/mysql/enterprise/monitor]:
Warning: DbExisting.ThrowError.MySQLConnection

How to repeat:
This happened after the db was stopped to do a backup, and forgot to restart it.

Suggested fix:
Instead please state: "Unable to reach the MySQL db server, please check it is running."

Hi Andy,

This is an issue on our side, the "DbExisting.ThrowError.MySQLConnection" string should be completely removed when we fixed the #48253 issue (Service Manager Installer should show mysql error for remote installations). Following the approach commented in this issue, the installer will throw the MySQL connection error. We will send you the fix today.

Patch sent to Keith.

Keith Russell writes: 
Patch checked in to installer repository.

Andy Bang writes: 
In build 2.2.1.1718.

Marcos Palacios writes: 
Tested successfully with Monitor upgrade installer build 2.2.1.1720 on Mac OS X 10.5.

Marcos Palacios writes: 
Also: Tested successfully with Monitor upgrade installer build 2.2.1.1720 on Fedora 6 (Linux x86). The message displayed is:

"Warning: Unable to login to the existing MySQL server to verify its ability to 
serve as an Enterprise Monitor data repository.  Please be sure the username, 
password, hostname, and port are all correct and try again.
Press [Enter] to continue :"

Marcos Palacios writes: 
Also: Tested successfully with Monitor upgrade installer build 2.2.1.1720 on Microsoft Windows XP. The message displayed is the same as in the previous 2 tests.

A note has been added to the 2.2.1 changelog;

        If the backend MySQL database being used for &merlin_server;                                                                                       
        is unavailable during an update installation, the installer                                                                                        
        may give a misleading message indicating the problem.