Bug 1235632 - Service ovirt-engine-reportsd won't start
Summary: Service ovirt-engine-reportsd won't start
Keywords:
Status: CLOSED DUPLICATE of bug 1209022
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-reports
Version: 3.6
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 3.6.0
Assignee: Yedidyah Bar David
QA Contact: Petr Matyáš
URL:
Whiteboard: integration
Depends On:
Blocks: 956226
TreeView+ depends on / blocked
 
Reported: 2015-06-25 11:19 UTC by Petr Matyáš
Modified: 2015-06-30 07:21 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-30 07:21:32 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
reports boot log (4.06 KB, text/plain)
2015-06-25 11:19 UTC, Petr Matyáš
no flags Details

Description Petr Matyáš 2015-06-25 11:19:33 UTC
Created attachment 1043069 [details]
reports boot log

Description of problem:
Ovirt-engine-reportsd service won't start after clean install and it can't be started manually. WildFly fails to parse config.

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

How reproducible:
always on my setup

Steps to Reproduce:
1. install ovirt+dwh+reports
2. check ovirt-engine-reportsd status
3. try to start the service and check status again

Actual results:
ovirt-engine-reportsd dead but pid file exists

Expected results:
running ovirt-engine-reportsd service

Additional info:
ovirt-engine-3.6.0-0.0.master.20150624173726.git0568f1b.el6.noarch
ovirt-engine-reports-3.6.0-0.0.master.20150624094644.20150624094424.git019fd83.el6.noarch
ovirt-engine-wildfly-8.2.0-1.el6.x86_64

Comment 1 Yedidyah Bar David 2015-06-30 07:21:32 UTC
Closing currently as clone of bug 1209022 which is about making reports work with jboss-as 7.1.1 side-by-side with engine on wildfly on same machine.

If you just need reports, you can set it up on a separate machine using a supported os (fedora 20 or el6 should work).

*** This bug has been marked as a duplicate of bug 1209022 ***


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