Log File Location
Types of Log Files
The CloudCenter platform generates log files for each major component to help troubleshoot problems and error. CloudCenter log files are generated through the log4J library and follows the log4j format.
|Component||Log File Name||Log File Location||Description|
CloudCenter maintains 10 revisions of these log files. Be sure the send the latest log file revision.
Logs generated by theserver.
|/usr/local/cliqr/logs/config-server.log||Config logs generated by the server.|
|cliqr-cis.log||/usr/local/cliqr/logs/cliqr-cis.log||Deprecated in CloudCenter 4.9.0|
|capacity-collector.log||/usr/local/cliqr/logs/capacity-collector.log||Specific to VMware and OpenStack cloud environments – if Capacity Management is enabled.|
|cloudblade.log||/usr/local/cliqr/logs/cloudblade.log||Available effective CloudCenter 4.9.0 – The logs generated for the interaction between the cloud provider and the CloudCenter platform. See Component-Specific Processes > CCO Processes for additional details.|
|/usr/local/cliqr/logs/container-blade.log||Available effective CloudCenter 4.9.0 – The logs generated for the interaction between the container and the CloudCenter platform. See Component-Specific Processes > CCO Processes for additional details.|
CloudCenter maintains 10 revisions of these logs. Be sure the send the latest log file revision.
The logs generated by the Admin for theserver.
|config-server.log||/usr/local/cliqr/logs/config-server.log||Config logs generated by the server.|
|hazelcast-server.log||/usr/local/cliqr/logs/hazelcast-server.log||Hazelcast logs generated by the CCM server.|
|mgmtserver.log||/usr/local/cliqr/logs/mgmtserver.log||Database logs generated by the CCM server.|
|/usr/local/cliqr/logs/notification-server.log||Notification logs for CloudCenter configuration changes.|
|capacity-manager.log||/usr/local/cliqr/logs/capacity-manager.log||Specific to VMware and OpenStack cloud environments – if Capacity Management is enabled.|
The logs generated by the database server.
See PostgreSQL Troubleshooting > HA-Specific Database Log Files for additional files that are only used in HA environments.
The logs generated by the AMQP server. CloudCenter uses RabbitMQ as the open source message broker to implement AMQP
|Linux Application VM||cliqr-agent.log||/usr/local/c3agent/jetty/logs/cliqr-agent.log||The logs generated by the management agent server.|
|The logs generated for application VMs with mid-tier services like Tomcat, Apache, and so forth. If those services are present, CloudCenter generates a separate log file with messages specific to the orchestration of that service.|
|Windows Application VM||node-metadata.log||C:\opt\jetty\logs|
The logs generated for the node metadata.
The logs generated by the management agent.
|service.log||C:\Program Files\osmosix\logs||The logs generated for application VMs with mid-tier services like Tomcat, Apache, and so forth. If those services are present, CloudCenter generates a separate log file with messages specific to the orchestration of that service.|
Environment Variables for Callout Scripts
|timestamp is the file name||/usr/local/osmosix/callout/<module_name>/logs/<timestamp>|
A full list on input variables is available in the callout script log.
For detailed logging, CloudCenter offers multiple levels to control the granularity of information printed in the log files. CloudCenter provides standard logging levels. Out-of-the box the logging level is set to default.
- Description: The log level for this file.
Enumeration Description ALL All levels of logging DEBUG Detailed information on the system flow and are generally written to logs. ERROR Other runtime errors or unexpected conditions and are generally visible on the CCM UI. FATAL Severe errors that cause premature termination and are generally visible on th CCM UI. INFO Startup or shut down runtime events and are are generally visible on the CCM UI.
so be conservative and keep to a minimum.
TRACE Detailed log information and are generally written to logs. WARN Use of deprecated APIs, poor use of API, other runtime situations that are undesirable or unexpected and area generally visible on the CCM UI TRACE_INT Detailed log information and are generally written to logs. OFF Turns off logging.
Retrieve a Log File
To retrieve any log file, follow this procedure:
Change to the required log file directory. For example, if you are retrieving thelog file:
Download the log file.
If you are forwarding this log file to CloudCenter Support, attach this file to your support ticket.
The Log Collector
- No labels