Working with Logs working-with-logs

AEM 6.4 has reached the end of extended support and this documentation is no longer updated. For further details, see our technical support periods. Find the supported versions here.

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

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


property to debug. Do not leave the log at the DEBUG log level longer than necessary, as it generates a lot of 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:

Fatal error
The action has failed, and the installer cannot proceed.
The action has failed. The installation proceeds, but a part of CRX was not installed correctly and will not work.
The action has succeeded but encountered problems. CRX may or may not work correctly.
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.