Bug 773577 - webadmin not available and logs not written after engine-setup on cleaned-with-engine-cleanup environment
Summary: webadmin not available and logs not written after engine-setup on cleaned-wit...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-installer
Version: unspecified
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
: 3.1
Assignee: Moran Goldboim
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-12 10:10 UTC by Rami Vaknin
Modified: 2014-01-12 23:53 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-09 08:01:59 UTC
oVirt Team: ---


Attachments (Terms of Use)
All Relevant Logs (625.33 KB, application/x-gzip)
2012-01-12 10:10 UTC, Rami Vaknin
no flags Details

Description Rami Vaknin 2012-01-12 10:10:20 UTC
Created attachment 552370 [details]
All Relevant Logs

Scenario:
1. Install ovirt-engine build 0.0.2-1 or 0.0.2-3 (the first builds that contain jboss7), use the default ports (8080 and 8443 for http/https) in engine-setup
2. Clean the env with engine-cleanup and run engine-setup with different ports (I used 8000 and 8001 for http/https)

Results:
1. jboss-as service started successfully but the webadmin is not available
2. logs are now written anymore
3. New missing/unsatisfied dependencies message in server.log
4. java.lang.IllegalStateException: JBAS014666: Duplicate resource [("subsystem" => "datasources"),("jdbc-driver" => "postgresql")] in boot.log


How reproducible:
3 out of 3


From server.log:
----------------
17:25:30,895 INFO  [org.jboss.as.controller] (MSC service thread 1-1) JBAS014774: Service status report
JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.deployment.subunit."engine.ear"."engine-genericapi.jar".component.GenericApiService.CREATE (missing) dependents: [service jboss.deployment.subunit."engine.ear"."engine-genericapi.jar".component.GenericApiService.VIEW."org.ovirt.engine.ui.genericapi.GenericApiService".LOCAL, service jboss.deployment.subunit."engine.ear"."engine-genericapi.jar".component.GenericApiService.ejb3.timerService, service jboss.deployment.subunit."engine.ear"."engine-genericapi.jar".component.GenericApiService.START, service jboss.deployment.subunit."engine.ear"."engine-genericapi.jar".moduleDeploymentRuntimeInformation] 

17:25:30,921 INFO  [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011921: Stopping OSGi Framework


From boot.log:
--------------
17:37:36,935 DEBUG [org.jboss.as.config] VM Arguments: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/usr/share/jboss-as/standalone/log/boot.log -Dlogging.configuration=file:/usr/share/jboss-as/standalone/configuration/logging.properties 
17:37:38,526 ERROR [org.jboss.as.controller] JBAS014612: Operation ("add") failed - address: ([
    ("subsystem" => "datasources"),
    ("jdbc-driver" => "postgresql")
]): java.lang.IllegalStateException: JBAS014666: Duplicate resource [
    ("subsystem" => "datasources"),
    ("jdbc-driver" => "postgresql")
]
	at org.jboss.as.controller.OperationContextImpl.addResource(OperationContextImpl.java:503) [jboss-as-controller-7.1.0.Beta1b.jar:]
	at org.jboss.as.controller.OperationContextImpl.createResource(OperationContextImpl.java:471) [jboss-as-controller-7.1.0.Beta1b.jar:]
	at org.jboss.as.controller.ParallelBootOperationContext.createResource(ParallelBootOperationContext.java:179) [jboss-as-controller-7.1.0.Beta1b.jar:]
	at org.jboss.as.controller.AbstractAddStepHandler.execute(AbstractAddStepHandler.java:41) [jboss-as-controller-7.1.0.Beta1b.jar:]
	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:322) [jboss-as-controller-7.1.0.Beta1b.jar:]
	at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:216) [jboss-as-controller-7.1.0.Beta1b.jar:]
	at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:152) [jboss-as-controller-7.1.0.Beta1b.jar:]
	at org.jboss.as.connector.subsystems.datasources.DataSourceEnable.execute(DataSourceEnable.java:240) [jboss-as-connector-7.1.0.Beta1b.jar:]
	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:322) [jboss-as-controller-7.1.0.Beta1b.jar:]
	at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:216) [jboss-as-controller-7.1.0.Beta1b.jar:]
	at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:152) [jboss-as-controller-7.1.0.Beta1b.jar:]
	at org.jboss.as.connector.subsystems.datasources.DataSourceEnable.execute(DataSourceEnable.java:240) [jboss-as-connector-7.1.0.Beta1b.jar:]
	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:322) [jboss-as-controller-7.1.0.Beta1b.jar:]
	at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:216) [jboss-as-controller-7.1.0.Beta1b.jar:]
	at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:152) [jboss-as-controller-7.1.0.Beta1b.jar:]
	at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:309) [jboss-as-controller-7.1.0.Beta1b.jar:]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22]
	at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
	at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:]

Comment 1 Ronen Angluster 2012-01-12 11:02:08 UTC
1. this issue has NOTHING to do with changing the ports or cleanup
the issue is with re-running engine-setup and the editing done with the standalone.xml
2. logs were "not written" since Jboss crushed on load (the console.log file was written, but server.log was not since the process did not initiate.)

3. a fix was submitted in patchset 16 of http://gerrit.ovirt.org/849 (the Jboss AS 7 adaptation patch)

Comment 3 Itamar Heim 2012-08-09 08:01:59 UTC
closing ON_QA bugs as oVirt 3.1 was released:
http://www.ovirt.org/get-ovirt/

Comment 4 Itamar Heim 2012-08-09 08:03:25 UTC
closing ON_QA bugs as oVirt 3.1 was released:
http://www.ovirt.org/get-ovirt/


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