AFX Server on a WildFly cluster fails to start with 'Cannot connect to RSA Identity Governance and Lifecycle. The watchdog will start AFX when it can connect' error in RSA Identity Governance & Lifecycle
Originally Published: 2018-05-16
Last Modified: 2022-06-20
Article Number
Applies To
RSA Version/Condition: 7.0.1, 7.0.2, 7.1.0, 7.1.1
Platform/Application Server: WildFly cluster
Issue
$ afx start
Cannot connect to RSA Identity Governance and Lifecycle. The watchdog will start AFX when it can connect
to RSA Identity Governance and Lifecycle.
- The RSA Identity Governance & Lifecycle application and database are running.
- You are executing afx start as the afx user.
Cause
Resolution
- RSA Identity Governance & Lifecycle 7.0.2 P14
- RSA Identity Governance & Lifecycle 7.1.0 P07
- RSA Identity Governance & Lifecycle 7.1.1 P02
- RSA Identity Governance & Lifecycle 7.2.0
Workaround
$ afx restart
Related Articles
RSA Via Lifecycle and Governance/Aveksa server will not start after environment customization Number of Views ODA (on demand access) token.will not authenticate when connecting thru a Netscaler VPN Gateway Number of Views Using Passage 3.2 for certificate based authentication; ERROR: MAP_API_FILE_ERROR Major: MAP -339 Number of Views Replica Radius server will not synchronize, Primary status is listed as Standalone Number of Views RSA SecurID Access identity router will not start after reboot on Microsoft Hyper-V Number of Views
Trending Articles
Deploy an Identity Router Virtual Machine in Microsoft Azure How to Change the Token Lifetime Extension Window in Authentication Manager Using rsautil RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to Replace the Web Server Certificate for the RSA Identity Governance & Lifecycle Web Console RSA Announces RSA Authentication Manager 8.9 Patch 3 and Updated Web-Tier Server
Don't see what you're looking for?
