• RSA Governance & Lifecycle 8.0.0

This is a known issue in the following RHEL (Red Hat Linux) versions:

• RHEL 8.4
• RHEL 8.5
• RHEL 8.6
• RHEL 8.7
• RHEL 8.8

This affects RSA Governance & Lifecycle 8.0.0 on the affected RHEL versions where AFX runs locally.

It also affects 8.0.0 versions of AFX Server where a remote AFX instance is installed on a remote server with the affected RHEL versions.

AFX Server fails to start with the following message in the command line:

service afx_server start

Maven home is set to /apps/oracle/apache-maven providing permissions
Successful connection detected to RSA Identity Governance and Lifecycle
Starting AFX Server: Setting MULE_HOME to /apps/oracle/AFX/esb...
Maven home is set to /apps/oracle/apache-maven providing permissions
Java version 1.8.0_362
Checking Aveksa OEM ESB License for AFX...
INFO: Loading '/apps/oracle/AFX/activemq/bin/env'
INFO: Using java '/usr/lib/jvm/jdk8u362-b09/bin/java'
INFO: Starting - inspect logfiles specified in logging.properties and log4j.properties to get details
INFO: pidfile created : '/apps/oracle/AFX/activemq/data/activemq.pid' (pid '45330')
Waiting for ActiveMQ to start....
ActiveMQ has started.

MULE_HOME is set to /apps/oracle/AFX/esb
MULE_BASE is set to /apps/oracle/AFX/esb
Starting Mule Enterprise Edition...
Waiting for Mule Enterprise Edition...........................................................................................................................
running: PID:45588
Waiting for AFX applications to start...
Waiting for AFX applications to start...
Waiting for AFX applications to start...

The only log file created is mule_ee.log under AFX Server installation folder and the following is logged in mule_ee.log file:

--> Wrapper Started as Daemon
Java Service Wrapper Standard Edition 64-bit 3.5.51
  Copyright (C) 1999-2022 Tanuki Software, Ltd. All Rights Reserved.
    http://wrapper.tanukisoftware.com
  Licensed to MuleSoft Inc. for Mule Runtime Enterprise Edition

Launching a JVM...
Starting the Mule Container...
WrapperManager: Initializing...

Valid license key --> Evaluation = false, Expiration Date = Tue Sep 02 08:00:00 SST 3000, Contact Name = Jim Ducharme, Contact Email Address = james.ducharme@rsa.com, Contact Telephone = 0000000000, Contact Company = RSA Security LLC, Contact Country = US, Entitlements = oracleebs-connector,api-gateway,sap-connector,sap-s4hana-connector,clustering,datamapper,epicbridges-connector,hl7,peoplesoft-connector,siebel-connector

Startup failed: Timed out waiting for signal from JVM.
JVM did not exit on request, termination requested.
JVM received a signal SIGKILL (9).
JVM process is gone.
JVM exited after being requested to terminate.

This is a known issue if RHEL is installed with FIPS mode disabled.  In RHEL 8.3 and earlier FIPS mode is enabled by default.  In RHEL 8.4 and later FIPS mode is disabled by default.

1. When installing RHEL for use with RSA Governance & Lifecycle, ensure that the operating system is installed with FIPS enabled.  Refer to the Red Hat documentation "Chapter 3. Installing the system in FIPS mode".
2. If the operating system is already installed with FIPS mode disabled, execute the following as root from the shell prompt and then restart the machine:

   fips-mode-setup --enable