ClusterControl Frontend - UI
Log Files
On Redhat variants:
- /var/www/html/clustercontrol/app/tmp/logs/error.log
- /var/www/html/clustercontrol/app/tmp/logs/debug.log
Apache logs:
- /var/log/httpd/error_log
- /var/log/httpd/access_log
- /var/log/httpd/ssl_error_log
- /var/log/httpd/ssl_access_log
On Debian variants:
- /var/www/clustercontrol/app/tmp/logs/error.log
- /var/www/clustercontrol/app/tmp/logs/debug.log
Apache logs:
- /var/log/apache2/error.log
- /var/log/apache2/access.log
- /var/log/apache2/ssl_access.log
Enable Debug
Edit
- /var/www/html/clustercontrol/app/Config/core.php
Change
Configure::write('debug', 0);
- 1: Errors and warnings shown, model caches refreshed, flash messages halted.
- 2: As in 1, but also with full debug messages and SQL output.
ClusterControl Backend - CMON
Log Files
On both Controller node and agents.
- /var/log/cmon.log
Enable Debug
$ export CMON_DEBUG=1
$ service cmon restart
Comments
1 comment
ClusterControl logs and enabling debug mode provide essential guidance for users who want to troubleshoot geometry dash deadlocked issues and optimize their database management. By understanding this you can interpret the logs administrators can effectively diagnose problems and improve system performance.
Please sign in to leave a comment.