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

DB errors during RPM installation of HQ points to wrong path (missing logs dir in the path)

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Deferred
  • Affects Version/s: 4.2.0.7
  • Fix Version/s: None
  • Component/s: Installation / Upgrade
  • Environment:
  • Case Links:
    none
  • Regression:
    No

Description

HQ 4.2.0.7 server startup went wrong somehow in the built-in database startup. Stdout from the startup is pointing to the database log file here: /opt/hyperic/server-4.2.0.7-EE/hqdb/data/hqdb.log

but that does not exist. I do see a database startup log file in the <install>/server-4.2.0.7-EE/logs directory though.

1) as root:
1a) rpm -vhi hyperic-hq-installer-4.2.0.7-EE.1.x86_64.rpm
1b) chown -R hyperic /opt/hyperic
1c) chgrp -R hyperic /opt/hyperic
1d) chmod -R 777 /opt/hyperic
1e) passwd hyperic (change password)
2) as user hyperic:
2a) cd /opt/hyperic/server-4.2.0.7-EE/bin
2b) -bash-3.2$ hq-server.sh start

Starting HQ server...
Initializing HQ server configuration...
Checking jboss jndi port...
Checking jboss mbean port...
Starting HQ built-in database...
HQ built-in database failed to start:
The log file /opt/hyperic/server-4.2.0.7-EE/hqdb/data/hqdb.log may contain further details on why it failed to start.

-bash-3.2$ ls -l /opt/hyperic/server-4.2.0.7-EE/hqdb/data/hqdb.log
ls: /opt/hyperic/server-4.2.0.7-EE/hqdb/data/hqdb.log: No such file or directory
-bash-3.2$ pwd
/opt/hyperic/server-4.2.0.7-EE/bin
-bash-3.2$ ls
ant ant.cmd db-archive.sh db-dropdb.sh db-start.sh hq-server.exe
ant.bat antenv.cmd db-createdb.sh db-psql.sh db-stop.sh hq-server.sh
-bash-3.2$ ls ..
bin conf data hqdb hq-engine hq-install.log jre lib logs README.txt tmp
-bash-3.2$ ls ../logs/
hqdb-2010-04-26.log hqdb.log hq-install.log hq-install.log.verbose

Activity

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, 3 days ago