CloudCenter 4.8 has reached End of Life (EOL) as of November 14, 2018. See End of Support Notices for additional context.

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.


ComponentLog File NameLog File LocationDescription

CCO

CloudCenter maintains 10 revisions of these log files. Be sure the send the latest log file revision.


gateway.log

/usr/local/cliqr/logs/gateway.log

Logs generated by the CCO server.

config-server.log

/usr/local/cliqr/logs/config-server.logConfig logs generated by the CCO server.
cliqr-cis.log/usr/local/cliqr/logs/cliqr-cis.logDeprecated in CloudCenter 4.9.0
capacity-collector.log/usr/local/cliqr/logs/capacity-collector.logSpecific to VMware and OpenStack cloud environments – if Capacity Management is enabled.
cloudblade.log /usr/local/cliqr/logs/cloudblade.logAvailable 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.

container-blade.log

/usr/local/cliqr/logs/container-blade.logAvailable 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.

CCM

CloudCenter maintains 10 revisions of these logs. Be sure the send the latest log file revision.


cliqr-admin.log

/usr/local/cliqr/logs/cliqr-admin.log

The logs generated by the Admin for the CCM server.

config-server.log/usr/local/cliqr/logs/config-server.logConfig logs generated by the CCM server.
hazelcast-server.log/usr/local/cliqr/logs/hazelcast-server.logHazelcast logs generated by the CCM server.
mgmtserver.log/usr/local/cliqr/logs/mgmtserver.logDatabase logs generated by the CCM server.

notification-server.log

/usr/local/cliqr/logs/notification-server.logNotification logs for CloudCenter configuration changes.
capacity-manager.log/usr/local/cliqr/logs/capacity-manager.logSpecific to VMware and OpenStack cloud environments – if Capacity Management is enabled.
PostgreSQL

Postgres-<DayofWeek>.log

/var/lib/pgsql/9.6/data/pg_log/Postgres-<DayofWeek>.log

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.

AMQP
  • amqp.log
  • startup_log
/var/log/rabbitmq

The logs generated by the AMQP server. CloudCenter uses RabbitMQ as the open source message broker to implement AMQP

Linux Application VMcliqr-agent.log/usr/local/c3agent/jetty/logs/cliqr-agent.logThe logs generated by the management agent server.
service.log

/usr/local/osmosix/logs/service.log 

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 VMnode-metadata.logC:\opt\jetty\logs

The logs generated for the node metadata.

cliqr-agent.logC:\opt\jetty\logs

The logs generated by the management agent.

service.logC:\Program Files\osmosix\logsThe 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.


Logging Levels

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.

level
  • Description: The log level for this file.
  • Type: Enumeration

    EnumerationDescription
    ALLAll levels of logging
    DEBUGDetailed information on the system flow and are generally written to logs.
    ERROROther runtime errors or unexpected conditions and are generally visible on the CCM UI.
    FATALSevere errors that cause premature termination and are generally visible on th CCM UI.
    INFOStartup or shut down runtime events and are are generally visible on the CCM UI.
    so be conservative and keep to a minimum.
    TRACEDetailed log information and are generally written to logs.
    WARNUse 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.
    OFFTurns off logging.

Retrieve a Log File

To retrieve any log file, follow this procedure:

  1. Change to the required log file directory. For example, if you are retrieving the CCO log file:

    cd /usr/local/cliqr/logs

  2. Download the log file.

  3. If you are forwarding this log file to CloudCenter Support, attach this file to your support ticket.

The Log Collector

See Log Collector (Required) and Download Log File for additional context

  • No labels
© 2017-2019 Cisco Systems, Inc. All rights reserved