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
Could not determine the AVDB SPFILE from "srvctl config database -d AVDB" when running modifyhostname.sh in RSA Via Lifec… 113Number of Views Authentication Manager 8.x ./rsautil store -a update_config gives WARNING cannot find the config name 314Number of Views Error scheduling data purging after new installation of RSA Identity Governance & Lifecycle 7.1.0 GA 181Number of Views Backup failure with error: entry '/system.config.network.5.needEncryption/routes' closed at '0' before the '30' bytes spec… 70Number of Views Installation of RSA Identity Governance and Lifecycle 7.0.1 P03 fails with a groovy error 120Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?