ClusterControl consists of a number of components that write to their own log file. These files reside on the ClusterControl node. By default, CMON and ClusterControl UI run without the debug option enabled. Please refer to Reporting and Debugging section on how to get the run in debug mode.
If you encounter any problems with ClusterControl, it is highly recommended to examine the related log files.
| Log Type | Default Location | |
|---|---|---|
| RedHat/CentOS | Debian/Ubuntu | |
| CMON process log | /var/log/cmon.log or /var/log/cmon_[cluster_id].log |
/var/log/cmon.log or /var/log/cmon_[cluster_id].log |
| CMON cloud log | /var/log/cmon-cloud.log |
/var/log/cmon-cloud.log |
| CMON events log | /var/log/cmon-events.log |
/var/log/cmon-events.log |
| ClusterControl UI error log | /var/www/html/clustercontrol/app/tmp/logs/error.log |
/var/www/clustercontrol/app/tmp/logs/debug.log |
| ClusterControl UI debug log | /var/www/html/clustercontrol/app/tmp/logs/debug.log |
/var/www/clustercontrol/app/tmp/logs/debug.log |
| ClusterControl LDAP log | /var/www/html/clustercontrol/app/log/cc-ldap.log |
/var/www/clustercontrol/app/log/cc-ldap.log |
| Apache error log |
|
/var/log/apache2/error.log |
| Apache access log |
|
|
The output of CMON process log per cluster is also accessible directly from ClusterControl → pick a cluster → Logs → CMON Logs.