The
aveksa_watchdog service known as the
ACM Watchdog checks that the database is running when RSA Identity Governance & Lifecycle is started. If the database is not running, it will watch for the database to start before continuing with the RSA Identity Governance & Lifecycle startup. Once the
ACM Watchdog detects the database is running, it will resume the RSA Identity Governance & Lifecycle startup. The W
atchdog may be monitored by looking at /tmp/ACMWatchdog.log.
An example of the contents from the /tmp/ACMWatchdog.log file is shown below:
Thu Aug 1 07:35:02 EDT 2019 Waiting for database instance
Thu Aug 1 07:35:18 EDT 2019 Waiting for database instance
Thu Aug 1 07:35:35 EDT 2019 Waiting for database instance
Thu Aug 1 07:35:51 EDT 2019 Waiting for database instance
Thu Aug 1 07:36:08 EDT 2019 Waiting for database instance
Thu Aug 1 07:36:25 EDT 2019 Waiting for database instance
Thu Aug 1 07:36:45 EDT 2019 Start RSA Identity Governance and Lifecycle
The
ACM Watchdog service is enabled by default during the RSA Identity Governance & Lifecycle installation using the
/etc/init.d/aveksa_watchdogscript and is started in run levels 3 and 5. To see if the
Watchdog is enabled, execute
ps -ef | grep Watchdog as the
oracle user.
If the
Watchdog is enabled, you will see:
$ ps -ef | grep Watchdog
root 19779 1 0 05:17 ? 00:00:00 /bin/bash /usr/bin/ACMWatchdog.sh
The
ACM Watchdog may be stopped and started with the following commands executed as the
oracle user:
$ sudo service aveksa_watchdog stop
$ sudo service aveksa_watchdog start
Use the
chkconfig command to change the run-level for the script. For more information on modifying the run level and/or disabling the
Watchdog upon system startup, please refer to
KB-1388 How to disable the automatic starting of ACM on system boot.
