Red Hat Bugzilla – Bug 1019178
[RHEVM-DWH-SETUP] - installation fails since the service failed to start
Last modified: 2016-02-10 14:22:39 EST
Created attachment 812394 [details]
rhevm-dwh-setup, ovirt-engine-dwhd & ovirt-engine-setup logs
Description of problem:
DWH installation failed, on clean environment (6.5)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 812395 [details]
rhevm-dwh-setup & server logs
Merged upstream; http://gerrit.ovirt.org/gitweb?p=ovirt-dwh.git;a=commit;h=b41930873c97824cf6301c2040421149aaeaea4b
*** Bug 1021914 has been marked as a duplicate of this bug. ***
Verified in IS20.1
Welcome to ovirt-engine-dwh setup utility
Backing up the DB... [ DONE ]
Upgrade DB... [ DONE ]
Setting DB connectivity... [ DONE ]
Starting ovirt-engine... [ DONE ]
Starting oVirt-ETL... [ DONE ]
Successfully installed rhevm-dwh.
service --status-all | grep -i ovirt
ovirt-engine (pid 7037) is running...
/etc/init.d/ovirt-engine-dwhd is running (pid 8660)
ovirt-engine-notifier is stopped
ovirt-websocket-proxy (pid 486) is running...
This bug is currently attached to errata RHEA-2013:15116. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.