Installation of RSA Identity Governance & Lifecycle 7.0.2 fails during WildFly install/config phase with jboss-modules.jar file access error
Originally Published: 2018-04-13
Article Number
Applies To
RSA Version/Condition: Any
Platform: Any
Issue
Waiting for RSA Identity Governance and Lifecycle to start.....
The RSA Identity Governance and Lifecycle server is not running and is not in a starting state
The RSA Identity Governance and Lifecycle server is not running and is not in a starting state
The issue been noticed with the WildFly configuration/Installation.
The stdout.log throws the following error:
Error: Unable to access jarfile /home/oracle/wildfly/jboss-modules.jar
The jboss-modules.jar file is missing from /home/oracle/wildfly/, indicating that the WildFly install didn't complete successfully.
Cause
Resolution
- Login to the system as root.
- Download a new wildfly-8.2.0.Final.tar and copy to /tmp/aveksa/packages.
- Verify that the downloaded .tar file/package is not corrupted.
- Navigate /tmp/aveksa/packages and run the following command to list the packages and indicates if errors were detected:
cd /tmp/aveksa/packages tar -tvf wildfly-8.2.0.Final.tar
- Verify the integrity of all other required packages. Run the following commands in the /tmp/aveksa/packages directory:
- On all downloaded .tar.bz2 files:
tar -jtvf
- On all downloaded .zip files:
unzip -t
- Uninstall acm (uninstall previous install to start fresh):
- Navigate to /tmp/aveksa/staging/deploy.
- Run the following command to start the uninstall:
./uninstall.sh -afx
Use the -afx option if you have the Access Fulfillment Express (AFX) module.
- Remove the existing staging directory:
rm -rf /tmp/aveksa/staging/
- Create a new staging directory:
mkdir -p /tmp/aveksa/staging
- Extract the Aveksa package in the new staging directory:
cd /tmp/aveksa/staging tar -jxvf /tmp/aveksa/packages/aveksa-<product-version>.tar.bz2
- Change to the staging directory:
cd /tmp/aveksa/staging
- Perform the installation:
/install.sh -afx
- Verify the installation completed successfully.
Related Articles
Authentication Manager 8.x ./rsautil store -a update_config gives WARNING cannot find the config name 299Number of Views AAOP - Scheduler SP3P1 on Weblogic 10.3 deployment issue->Cannot find the declaration of element 'beans'. 18Number of Views What are RSA Security's plans to support SHA-256 with KCA? 69Number of Views Could not determine the AVDB SPFILE from "srvctl config database -d AVDB" when running modifyhostname.sh in RSA Via Lifec… 113Number of Views OpenSSL Vulnerability in RSA Authentication Manager 8.1 & 7.1 CVE-2015-3197 and CVE-2016-0701 - False Positive 44Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Release Notes for RSA Authentication Manager 8.8 RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide "HTTP response error! Response code=401" when starting RSA Identity Governance and Lifecycle Access Fulfillment Express (A… RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?