DocumentationAEM 6.5User Guide

Working with Logs working-with-logs

Last update: Wed Dec 06 2023 00:00:00 GMT+0000 (Coordinated Universal Time)

This section includes detailed information on logs available to help you troubleshoot.

NOTE
For further information about logs see:

CRX records detailed logs. After you unpack and start Quickstart, you can find logs in the following locations:

  • crx-quickstart/launchpad/logs
  • crx-quickstart/server/logs
  • crx-quickstart/logs

Activating the DEBUG Log Level activating-the-debug-log-level

The default log level is INFO, that is, DEBUG messages are not logged.

To activate DEBUG log level, use the CRX explorer to set the

/libs/sling/config/org.apache.sling.commons.log.LogManager/org.apache.sling.commons.log.level

property to debug. Do not leave the log at the DEBUG log level longer than necessary, as it generates numerous logs.

A line in the debug file usually starts with DEBUG, and then provides the log level, the installer action and the log message. For example:

DEBUG 3 WebApp Panel: WebApp successfully deployed

The log levels are as follows:

0
Fatal error
The action has failed, and the installer cannot proceed.
1
Error
The action has failed. The installation proceeds, but a part of CRX was not installed correctly and will not work.
2
Warning
The action has succeeded but encountered problems. CRX may or may not work correctly.
3
Information
The action has succeeded.

Verbose Option Used for Troubleshooting verbose-option-used-for-troubleshooting

When you start CRX, you can add the -v (verbose) option to the command line as in:

java -jar crx-<*version*>-<*edition*>.jar -v

Use the verbose option for troubleshooting as this option displays some of the quickstart log output on the console.

recommendation-more-help
19ffd973-7af2-44d0-84b5-d547b0dffee2