Bug 908617 - engine-service was not started after engine-setup finished successfully
Summary: engine-service was not started after engine-setup finished successfully
Keywords:
Status: CLOSED DUPLICATE of bug 908497
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-installer
Version: 3.2
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Ofer Schreiber
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-07 07:25 UTC by shu ming
Modified: 2013-02-07 09:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-07 09:05:46 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)

Description shu ming 2013-02-07 07:25:22 UTC
Description of problem:
The webadmin interface can not be opened by browser after ovirt 3.2 was installed on FC18.

Version-Release number of selected component (if applicable):
[root@localhost ~]# rpm -qa |grep engine
ovirt-engine-backend-3.2.0-2.fc18.noarch
ovirt-engine-restapi-3.2.0-2.fc18.noarch
ovirt-engine-cli-3.2.0.7-1.20121212.gitd77dad3.fc18.noarch
ovirt-engine-tools-common-3.2.0-2.fc18.noarch
ovirt-engine-genericapi-3.2.0-2.fc18.noarch
ovirt-engine-setup-3.2.0-2.fc18.noarch
ovirt-engine-sdk-3.2.0.5-1.20121213.gitc0ab704.fc18.noarch
ovirt-engine-webadmin-portal-3.2.0-2.fc18.noarch
ovirt-engine-config-3.2.0-2.fc18.noarch
ovirt-engine-dbscripts-3.2.0-2.fc18.noarch
ovirt-engine-3.2.0-2.fc18.noarch
ovirt-engine-notification-service-3.2.0-2.fc18.noarch
ovirt-engine-userportal-3.2.0-2.fc18.noarch

How reproducible:
Installed the oVirt engine based on the http://www.ovirt.org/Testing/OvirtTestDay and run engine-setup

Steps to Reproduce:
1.
2.
3.
  
Actual results:
When the webadmin url was opened, the page told me:

Service Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Expected results:
The webadmin interfaces should be opened by the browser.

Additional info:
#cat /var/log/ovirt-engine/console.log

Exception in thread "main" java.lang.ExceptionInInitializerError
at org.jboss.as.server.Main.main(Main.java:73)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.modules.Module.run(Module.java:260)
at org.jboss.modules.Main.main(Main.java:291)
Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
at org.jboss.logmanager.Logger.getLogger(Logger.java:60)
at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42)
... 7 more
Exception in thread "main" java.lang.ExceptionInInitializerError
at org.jboss.as.server.Main.main(Main.java:73)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.modules.Module.run(Module.java:260)
at org.jboss.modules.Main.main(Main.java:291)
Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
at org.jboss.logmanager.Logger.getLogger(Logger.java:60)
at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42)
... 7 more
Exception in thread "main" java.lang.ExceptionInInitializerError
at org.jboss.as.server.Main.main(Main.java:73)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.modules.Module.run(Module.java:260)
at org.jboss.modules.Main.main(Main.java:291)
Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager")
at org.jboss.logmanager.Logger.getLogger(Logger.java:60)
at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42)
... 7 more

Comment 1 shu ming 2013-02-07 09:05:46 UTC
After updating openjdk packages from here 

http://koji.fedoraproject.org/koji/buildinfo?buildID=382581

The bug was gone.

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


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