Article Content
Article Number | 000036198 |
Applies To | RSA Product Set: RSA Identity Governance & Lifecycle RSA Version/Condition: 7.1.0 Platform: Red Hat 6.x |
Issue | When upgrading to or installing RSA Identity Governance & Lifecycle 7.1 on Red Hat 6.x, the following errors occur at the end of the installation:
Clean up backup directories Unzip ear to a temporary folder /tmp/aveksa.ear... Updating ear in the temporary folder /tmp/aveksa.ear... Setting permissions.. Repackage aveksa.ear to /tmp/repackaged_ear_dir Deploying aveksa.ear... {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined, "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {"Services that were unable to start:" => ["jboss.deployment.subunit.\"aveksa.ear\".\"acmSubscriber.jar\".PARSE","jboss.deployment.subunit.\"aveksa.ear\".\"aveksa.war\".PARSE","jboss.deployment.subunit.\"aveksa.ear\".\"wpConsole.war\".PARSE","jboss.deployment.subunit.\"aveksa.ear\".\"wpServices.war\".PARSE","jboss.deployment.unit.\"aveksa.ear\".PARSE"],"Services that may be the cause:" => ["jboss.http-upgrade-registry.default","jboss.naming.context.java.JmsXA","jboss.remoting.remotingConnectorInfoService.http-remoting-connector"]}}}} Failed to deploy aveksa.ear Fresh install failed.. deleting /home/oracle/install, /home/oracle/Aveksa_System.cfg and /home/oracle/setDeployEnv.sh as part of cleanup. Step failed! See /tmp/aveksa-install.log for more information.
12:54:29,268 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "undertow"), ("server" => "default-server"), ("http-listener" => "default") ]) - failure description: { "WFLYCTL0080: Failed services" => {"jboss.undertow.listener.default" => "org.jboss.msc.service.StartException in service jboss.undertow.listener.default: WFLYUT0082: Could not start 'default' listener. Caused by: java.net.SocketException: Protocol family unavailable"}, "WFLYCTL0412: Required services that are not installed:" => ["jboss.undertow.listener.default"], "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined 12:54:29,336 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started (with errors) in 358ms - Started 396 of 672 services (11 services failed or missing dependencies, 427 services are lazy, passive or on-demand) 12:54:30,085 INFO [org.jboss.as.controller] (management-handler-thread - 4) WFLYCTL0183: Service status report WFLYCTL0186: Services which failed to start: service jboss.undertow.listener.https: org.jboss.msc.service.StartException in service jboss.undertow.listener.https: WFLYUT0082: Could not start 'https' listener. service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: WFLYUT0082: Could not start 'default' listener. service jboss.undertow.listener.agent-ssl: org.jboss.msc.service.StartException in service jboss.undertow.listener.agent-ssl: WFLYUT0082: Could not start 'agent-ssl' listener. 1 2:54:30,288 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: WFLYUT0082: Could not start 'default' listener. at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:153) |
Cause | This issue was introduced due to defect ACM-85437. |
Resolution | To resolve this issue, please do the following steps: Do a clean uninstall Please do a clean uninstall of the failed installed by following the steps on page 219 of the RSA Identity Governance and Lifecycle 7.1 Installation Guide.
You can check results of the uninstall process in the uninstall log file in the /tmp directory. For example, /tmp/aveksa-uninstall.log.Dec-21-2011.07.42.26
Put workaround in place and reinstall
|
Notes | This defect is fixed in 7.1 P01. We do deliver a full kit for 7.1 P01, so you may choose to go directly to 7.1 P01. |