All the disaster recovery framework components produce messages that are stored in log files.
Information about the loading, running, and stopping disaster recovery framework components in the common agent container is recorded in the following log files. The most recently logged messages are in file 0, then 1, and 2.
/var/cacao/instances/default/logs/cacao.0
/var/cacao/instances/default/logs/cacao.1
/var/cacao/instances/default/logs/cacao.2
System log messages are stored in the /var/adm/messages log file.
Each cluster node keeps separate copies of the previous log files. The combined log files on all cluster nodes form a complete snapshot of the currently logged information. The log messages of the disaster recovery framework modules are updated on the node where the disaster recovery framework is currently active. The data replication control-log messages are updated on the node where the data replication resource is currently Online.
For data replication modules that are based on script-based plug-ins, you can set the DEBUG property to TRUE for more verbose messages to aid in troubleshooting.
cacao log settings help in debugging the disaster recovery framework core framework and the replication modules. The geocontrol, geoutilities and notifier are disaster recovery framework sub modules. geocontrol corresponds to core and replication modules, geoutilities applies to all utility related API's, and notifier applies to event notification processing.
Debugging must be enabled on all the nodes of the cluster and the nodes of the partners of interest.
To turn on debug so that it does not persists across cacao restarts, type:
# cacaoadm set-filter com.sun.cluster.agent.geoutilities=FINEST # cacaoadm set-filter com.sun.cluster.agent.geocontrol=FINEST # cacaoadm set-filter com.sun.cluster.agent.notifier=FINEST
To turn on debug so that it persists across cacao restarts, type:
# cacaoadm set-filter -p com.sun.cluster.agent.geoutilities=FINEST # cacaoadm set-filter -p com.sun.cluster.agent.geocontrol=FINEST # cacaoadm set-filter -p com.sun.cluster.agent.notifier=FINEST
When debugging is turned on, the number of messages sent to /var/cacao/instances/default/logs/cacao.0 greatly increases. If needed, increase the limit allowed in the log file by updating the log-file-limit parameter. Updating this parameter requires a cacao stop. Stopping cacao on a node running geo-failovercontrol causes this resource to restart. To avoid this, you can update log-file-limit on nodes that are not running geo-failovercontrol, then switch geo-infrastructure rg to a node where log-file-limit has been updated, then update the node where geo-infrastructure was running.
To update log-file-limit, type:
# cacaoadm stop # cacaoadm set-param log-file-limit=<new-value-desired> # cacaoadm start