'AFX server is not running' message printed in logs every minute for each unused (Disabled, Not running, or deleted) AFX Server in RSA Governance & Lifecycle
Last Modified: 2025-05-01
Article Number
Applies To
This is a known behavior in the following versions:
- RSA Governance & Lifecycle 8.0.0 P03
Issue
Log messages like the following repeat every minute for each unused (Disabled, Not running, or deleted) AFX Server in aveksaServer.log file:
07/25/2024 15:48:00.008 INFO (ThreadPool-2) [SystemOut] AFX server is not running.
07/25/2024 15:48:00.008 INFO (ThreadPool-2) [SystemOut] Threshold = 30000
07/25/2024 15:48:00.008 INFO (ThreadPool-2) [SystemOut] startDate = 1721906318000
07/25/2024 15:48:00.008 INFO (ThreadPool-2) [SystemOut] endDate = 1721915280000
07/25/2024 15:48:00.008 INFO (ThreadPool-2) [SystemOut] intervalThresholdMultiplier = 6 Cause
Log statements were added in RSA Governance & Lifecycle 8.0.0 P03 to print in aveksaServer.log file to capture instances when an AFX Server is down.
Resolution
This issue is resolved in the following versions:
- RSA Governance & Lifecycle 8.0.0 P04
Related Articles
Apply error 'ORA-01403: no data found' occurring on all clusters every 15 minutes 120Number of Views New Change Requests become stuck at every Approval Node regardless of Approval status in RSA Identity Governance & Lifecycle 162Number of Views How to get RSA Data Loss Prevention Endpoint logs for all components 76Number of Views AFX Connector Stays in Stopped state 20Number of Views How to resolve the issue of logging proxy server IP address for every request 13Number of Views
Trending Articles
Artifacts to gather in RSA Identity Governance & Lifecycle How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle RSA MFA Agent for UNIX Platform Support Matrix
Don't see what you're looking for?