Troubleshooting guide for RPM

In the event of an OpenIAM installation failure, users can troubleshoot and identify potential issues by collecting and examining logs. Below is a general guide on how to collect logs for failed installations and individual service failures, which is the first step in troubleshooting.

Collecting OpenIAM installation logs

If the OpenIAM installation fails, retrieve the init.log file from the following directory.

cd /usr/local/openiam
[root@rhel9 openiam]# ls -lrth | grep init
-rw-r--r--.  1 root    root    222K Jan 29 13:54 init.log

Collecting logs for individual failed services

To collect logs for individual services, navigate to the logs directory and list the available log files.

cd /usr/local/openiam/logs
[root@rhel9 logs]# ls -lrth

Example log files are the following.

-rwxrwxrwx. 1 root    root       0 Jan 29 13:49 vault.out
-rw-r--r--. 1 openiam openiam  41K Feb  2 10:19 business-rule-manager.log
-rw-r--r--. 1 openiam openiam  41K Feb  2 10:19 reconciliation.log
-rw-r--r--. 1 openiam openiam  41K Feb  2 10:19 synchronization.log
-rw-r--r--. 1 openiam openiam  41K Feb  2 10:19 groovy-manager.log
-rw-r--r--. 1 openiam openiam  53K Feb  2 10:19 workflow.log
-rw-r--r--. 1 openiam openiam  43K Feb  2 10:19 device-manager.log
-rw-r--r--. 1 openiam openiam  86K Feb  2 10:21 idm.log
-rw-r--r--. 1 openiam openiam  61K Feb  2 10:21 email-manager.log
-rw-r--r--. 1 openiam openiam  61K Feb  2 10:21 auth-manager.log
-rw-r--r--. 1 openiam openiam 168K Feb  2 10:51 openiam-esb.log

Collecting OpenIAM UI logs

To retrieve catalina.out log for the OpenIAM UI, navigate to the following directory.

cd /usr/local/openiam/ui/logs

To list Catalina logs use the following.

[root@rhel9 logs]# ls -lrth | grep catalina
-rw-r-----. 1 openiam openiam 927K Jan 29 18:50 catalina.2025-01-29.log
-rw-r-----. 1 openiam openiam 309K Jan 30 05:56 catalina.2025-01-30.log
-rw-r-----. 1 openiam openiam 1.8M Feb  2 10:23 catalina.out
-rw-r-----. 1 openiam openiam 272K Feb  2 10:23 catalina.2025-02-02.log

OpenIAM CLI commands for individual service logs

To check logs for specific services, use the following OpenIAM CLI commands.

openiam-cli log openiam-esb
openiam-cli log idm
openiam-cli log openiam-ui
openiam-cli log workflow
openiam-cli log auth-manager
openiam-cli log device-manager
openiam-cli log reconciliation
openiam-cli log synchronization
openiam-cli log groovy-manager
openiam-cli log email-manager

Checking `Journalctl` logs for individual services

To check service logs using journalctl, use the following commands.

journalctl -u openiam-esb
journalctl -u idm
journalctl -u openiam-ui
journalctl -u workflow
journalctl -u auth-manager
journalctl -u device-manager
journalctl -u reconciliation
journalctl -u synchronization
journalctl -u groovy-manager
journalctl -u email-manager

Note: The UI log file should be analyzed last since UI depends on the health of the ESB. The analysis should follow this order:
1. First level: Start by analyzing the ESB logs.
2. Second level: If no issues are found in ESB, proceed to analyze logs for services such as IDM, Workflow, Authentication, Synchronization, Reconciliation, Email, etc.
3. Final step: Only if no issues are found in the first two levels, then check the UI log.

Failed dependencies