Bug #40996 Service Manager update installer exits if a backup folder already exists

• Submitted: 24 Nov 2008 22:17
• Modified: 9 Feb 2009 11:40
• Reporter: Marcos Palacios
• Status: Closed
• Category: MySQL Enterprise Monitor: Installing
• Severity: S3 (Non-critical)
• Version: 2.0.0.7103
• OS: Any
• Assigned to: BitRock Merlin
• CPU Architecture: Any

[24 Nov 2008 22:17] Marcos Palacios

Description:
If the current installation of the Service Manager includes a 'backup' folder/directory, due to a previous upgrade, the Service Manager installer shows the message attached here and then exits.

How to repeat:
- install the Service Manager (monitor) ver. 1.3.x
- upgrade the installation to ver. 2.0.0.7102, and answer 'Yes' to backup question so the 'backup' folder is created
- upgrade again with at least ver. 2.0.0.7103

Suggested fix:
Allow the backup folder to exist when doing an upgrade.

[24 Nov 2008 22:19] Marcos Palacios

pop up shown

Attachment: Monitor7105update.png (image/png, text), 178.90 KiB.

[5 Dec 2008 17:00] Marcos Palacios

In build 2.0.0.7119, we found that it allows the 'backup' folder to exist but it does not say anything about it (like the agent update installer does) and just goes on, replacing what was in the original 'backup' folder.

[22 Jan 2009 17:18] Marcos Palacios

This problem still occurs when updating with build 2.0.4.7138 on Mac OSX but it does not happen on Windows XP.

The workaround is to rename or remove the 'backup' directory before running the update OR to use a different name for the new backup directory.

[23 Jan 2009 17:40] Marcos Palacios

We have verified that this problem occurs when updating from build 2.0.4.7138 to build 2.1.0.1003 on Windows XP.

[3 Feb 2009 9:54] BitRock Merlin

Patch sent to Keith.

[7 Feb 2009 0:07] Marcos Palacios

Verified fixed in service manager build 2.0.5.7144.

[9 Feb 2009 11:40] Tony Bedford

An entry was added to the 2.0.5 changelog:

If an installation of Service Manager 2.0.0.7102 included a backup directory, due to a previous upgrade, and was upgraded using at least Service Manager 2.0.0.7103, then the installer displayed an error message and exited.

The error message displayed was:

There has been an error.
Error renaming /Applications/mysql/enterprise/monitor/apache-tomcat to
/Applications/mysql/enterprise/monitor/backup/apache-tomcat
The application will exit now