Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

Overwrite the HQ server database is ending up with ERROR message

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Deferred
  • Affects Version/s: 4.2.0.4
  • Fix Version/s: None
  • Component/s: Core Monitoring
  • Environment:
    Mysql 5.1.x on MacOSX
  • Case Links:
    none
  • Regression:
    No

Description

This is directly related to https://issuetracker.springsource.com/browse/TCSRV-1234.

Anytime time the overwrite option is selected when running the installer and MySQL is on MacOSX the install fails.

This is what I just did:
1. Installed hyperic4.2.0.5 that was created for tc Server (noJRE) with a brand new db
2. Once the install was complete, I ran it again (installed HQ in a different directory) same database.
3. I selected the overwrite option and received the same error

Setting up server database...
--------------------------------------------------------------------------------
An ERROR occurred, the installation cannot continue.
FATAL EXCEPTION at /Users/jasonkonicki/Documents/hq/tcservers/hyperic-hq-installer-noJRE-tc-server-2.0.0.M5/installer-4.2.0.5-EE/data/setup.xml:434: : The following error occurred while executing this line:
/Users/jasonkonicki/Documents/hq/tcservers/hyperic-hq-installer-noJRE-tc-server-2.0.0.M5/installer-4.2.0.5-EE/data/setup.xml:440: The following error occurred while executing this line:
/Users/jasonkonicki/Documents/hq/tcservers/hyperic-hq-installer-noJRE-tc-server-2.0.0.M5/installer-4.2.0.5-EE/data/setup.xml:580: The following error occurred while executing this line:
/Users/jasonkonicki/Documents/hq/tcservers/hyperic-hq-installer-noJRE-tc-server-2.0.0.M5/installer-4.2.0.5-EE/data/setup-db-MySQL.xml:16: The following error occurred while executing this line:
/Users/jasonkonicki/Documents/hq/tcservers/hyperic-hq-installer-noJRE-tc-server-2.0.0.M5/installer-4.2.0.5-EE/data/setup-db-hibernate.xml:193: Errors while performing <hbm2ddl>

and the verbose log looks the same with the same cause. Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'eam_config_props' already exists

Activity

Hide
Jason Konicki added a comment -

Attaching the verbose install log.

Show
Jason Konicki added a comment - Attaching the verbose install log.
Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    41 weeks, 2 days ago