---
title: Troubleshoot installations
description: AM can capture information in debug log files that are useful when troubleshooting AM problems. Debug logging describes how to enable debug logging after AM has been started.
component: pingam
version: 7.4
page_id: pingam:installation:install-troubleshooting
canonical_url: https://docs.pingidentity.com/pingam/8.1/installation/install-troubleshooting.html
llms_txt: https://docs.pingidentity.com/pingam/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
keywords: ["Install", "Troubleshooting"]
page_aliases: ["install-guide:install-troubleshooting.adoc"]
superseded_by: https://docs.pingidentity.com/pingam/8.1/installation/install-troubleshooting.html
---

# Troubleshoot installations

AM can capture information in debug log files that are useful when troubleshooting AM problems. [Debug logging](../maintenance/debug-logging.html) describes how to enable debug logging after AM has been started.

It is also possible to capture debug logs while installing AM. This can be useful if you need to troubleshoot an installation problem.

Follow these steps to capture debug logs while installing AM on Tomcat:

1. If Tomcat is already started, stop it.

2. Specify the `-Dcom.iplanet.services.debug.level=message` option in the `CATALINA_OPTS` environment variable:

   ```
   $ export CATALINA_OPTS=-Dcom.iplanet.services.debug.level=message
   ```

   There are several ways that you can specify the `CATALINA_OPTS` environment variable. You can set the variable:

   * In the `/path/to/tomcat/bin/setenv.sh` file

   * In the login shell of the user who runs Tomcat

3. Run the AM installation. Debug log files containing troubleshooting information appear in the `/path/to/openam/var/debug` directory.

4. When you have completed AM installation and no longer need to capture debug logs, stop Tomcat, revert the debug logging options, and restart Tomcat.