AFX Connectors remain in a Deployed state and 'Could not locate data file kahadb/db-XXX.log' error in RSA Identity Governance & Lifecycle
2 years ago
Originally Published: 2015-04-19
Article Number
000055978
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 6.9.x, 7.x
 
Issue
The AFX Server is in a Running state but all previously working RSA Identity Governance & Lifecycle AFX Connectors are stuck in a Deployed state and do not progress to a Running state. For example,
 
User-added image

A restart of AFX, RSA Identity Governance & Lifecycle, and even a system reboot does not fix the problem.
  
The $AFX_HOME/activemq/data/activemq.log has an error similar to this:


ERROR | Looking for key 284 but not found in fileMap: {307=db-307.log number = 307 , length = 1951190} 
| org.apache.kahadb.journal.Journal | main 
2014-12-22 11:09:33,857 | ERROR | Failed to start ActiveMQ JMS Message Broker. 
Reason: java.io.IOException: Could not locate data file /home/oracle/AFX/activemq/data/kahadb/db-284.log
Cause
The key message in the $AFX_HOME/activemq/data/activemq.log is this message (Note the AFX user is oracle in this case):

Could not locate data file /home/oracle/AFX/activemq/data/kahadb/db-284.log 

KahaDB is a file-based persistence database used by ActiveMQ. In this case, ActiveMQ is unable to find the persistence database (db-XXX.log). This means the KahaDB database is corrupt.

We have seen the KahaDB database become corrupted on a system that ran out of disk space while AFX was actively being used.
 
Resolution
To resolve this issue, add more disk space and/or free up existing disk space. Once a suitable amount of disk space is available, create a blank persistence file with the same name and restart AFX.
  1. Clean up disk space. Please see  RSA Knowledge Base Article 000027944 -- How to check local file system disk space usage for RSA Identity Governance & Lifecycle and/or contact RSA Identity Governance & Lifecycle Support for assistance on disk space cleanup.
  2. Login as the AFX user.
  3. Stop AFX.
  4. Navigate to the directory where the ActiveMQ KahaDB database exists.
  5. Touch the db-XXX.log, where XXX is the number of the file that is missing; in this case db-284.log.
  6. List the directory contents to make sure the file permissions for the file are correct.
  7. Start AFX.
afx stop
cd $AFX_HOME/activemq/data/kahadb/
touch db-XXX.log
ls -la
-rw-rw-r-- 1 oracle oinstall 0 May 13 2019 db-XXX.log
afx start
  1. If this does not resolve your issue, recreate the persistence database as described in RSA Knowledge Base Article 000038511 -- How to create a new ActiveMQ KahaDB for use with AFX in RSA Identity Governance & Lifecycle.
  2. If recreating the persistence database does not resolve your issue, the next step would be to download and install the AFX Server Archive. For instructions on how to do this, please see RSA Knowledge Base Article 000037993 - How to download and install the AFX Server Archive in RSA Identity Governance & Lifecycle.
  3. If downloading and installing the AFX Server Archive does not resolve your issue, please see RSA Knowledge Base Articles 000038029 -- Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle and 000038030 -- Troubleshooting AFX Server issues in RSA Identity Governance & Lifecycle for additional articles on resolving AFX issues.
If none of the above resolves your issue, please contact RSA Identity Governance & Lifecycle Support for further assistance.
 

Related Articles

Trending Articles

Don't see what you're looking for?