Bug 1369165 - Data is not being collected by DWH
Summary: Data is not being collected by DWH
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-dwh
Version: 3.5.5
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ovirt-4.1.0-alpha
: ---
Assignee: Shirly Radco
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-22 14:52 UTC by Javier Coscia
Modified: 2019-12-16 06:28 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-26 06:41:45 UTC
oVirt Team: Metrics
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2541691 0 None None None 2016-08-22 15:14:49 UTC

Description Javier Coscia 2016-08-22 14:52:08 UTC
Description of problem:

DWH is not collecting any new data after 6/21

Version-Release number of selected component (if applicable):

rhevm-3.5.0-0.32.el6ev.noarch

rhevm-dwh-3.5.5-1.el6ev.noarch
rhevm-dwh-setup-3.5.5-1.el6ev.noarch
rhevm-lib-3.5.8-0.1.el6ev.noarch
rhevm-reports-3.5.8-1.el6ev.noarch
rhevm-reports-setup-3.5.8-1.el6ev.noarch
rhevm-setup-base-3.5.8-0.1.el6ev.noarch
rhevm-setup-plugin-ovirt-engine-common-3.5.8-0.1.el6ev.noarch

postgresql-server-8.4.20-6.el6.x86_64



How reproducible:

Currently, 100% in customer's environment

Steps to Reproduce (random - sometimes DWH works, sometimes it doesn't):

Customer thinks it's related to a start up process where he noticed that starting the reports host first will make DWH to fail


Actual results:

ovirt-engine-dwhd.log fills with different error messages, like NPE, I/O in the backend, etc

Expected results:

DWH should work correctly

Additional info:

Reports and DWH are running on a separate host than RHEV Engine

DNS resolution: works
Remote access to DBs: works


Note You need to log in before you can comment on or make changes to this bug.