000036198 - RSA Identity Governance & Lifecycle 7.1 installation on Red Hat 6.x fails with the error:  Could not start 'default' listener and others

Document created by RSA Customer Support Employee on Jun 27, 2018
Version 1Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000036198
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0
Platform: Red Hat 6.x
 
IssueWhen 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:
  • In /tmp/aveksa-install.log:

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. 
 


  • In /home/oracle/wildfly/standalone/log/stdout.log:

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)
CauseThis issue was introduced due to defect ACM-85437.
ResolutionTo 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.

  1. Log in to the installation machine as the root user. Note: You must log in as the root account to ensure that the proper permissions are granted. This procedure may not work using any other account.
  2. Stop all RSA Identity Governance & Lifecycle and Oracle services. See Stopping RSA Identity Governance and Lifecycle Services and Starting and Stopping the Oracle Database and Oracle Services for more information.
  3. Navigate to the following directory:


cd /tmp/aveksa/staging/deploy


  1. Run the following command:


./uninstall.sh


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


  1. RSA Support recommends a reboot after the above procedure

Put workaround in place and reinstall



  1. Download the attached ACM-85437.zip and unzip the files to a temporary location.
  2. Replace the original files with the unzipped files:


cd <your temporary location>
mv aveksa_server /tmp/aveksa/staging/deploy/init.d/aveksa_server
mv domain.xml /tmp/aveksa/staging/deploy/wildfly-conf/configuration/domain.xml


  1. Only after the files are replaced should you proceed with running the install.as as outlined in the RSA Identity Governance and Lifecycle 7.1 Installation Guide.
NotesThis 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.

Attachments

Outcomes