Logs and diagnostic information

Each service maintains its own set of logs. By default, the logs are maintained in the install_path/log folder on each instance in the system. During installation, you can configure each service to store its logs in a different, non-default location.

You can manage any of the log files yourself, deleting or archiving them as necessary.

System logs are managed automatically in these ways:

• All log files are periodically added to a compressed file and moved to install_path/retired/. This occurs at least one time a day, but can also occur:
  • Whenever you run the log_download script.
  • Hourly, if the system instance's disk space is more than 60% full.
• When a log file grows larger than 10MB in size, the system stops writing to that file, renames it, and begins writing to a new file. For example, if the file exampleService.log.0 grows too large, it is renamed to exampleService.log.1 and the system creates a new file named exampleService.log.0 to write to.

The tool log_download lets you easily retrieve logs and diagnostic information from all instances in the system. This tool is located at this path on each instance:

install_path/bin/log_download

For information about running the tool, use this command:

install_path/bin/log_download -h

By default, each service stores its logs in its own folder at this path:

install_path/log

This table shows the default log folder names for each service. Depending on how your system was configured when first deployed, your system's logs might not be stored in these directories.