> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-admin/troubleshooting-overview-cp.md).

# Troubleshoot the Pentaho system

As a best practice, your initial approach for troubleshooting components within Pentaho should be to use logging to monitor operations within transformations, jobs, database connections, and the server. You can monitor transformations, jobs, and database connections through [logging in PDI](/pdia-admin/optimize-the-pentaho-system/monitoring-system-performance/pdi-logging.md). For the Pentaho Server, the log file is `pentaho.log`, which is in the `pentaho-server/logs` folder. The contents of this file can help you track down why the server failed to start or work properly.

**Note:** If you used a manual install with your own Tomcat web application server, `pentaho.log` resides under `pentaho-server/tomcat/logs`.

Besides analyzing logs, a number of Pentaho customers and partners have posted problems and solutions they have encountered in the past. The following common categories contain descriptions of these problems and how to resolve them:

* [**General issues**](/pdia-admin/troubleshooting-overview-cp/general-issues.md)

  Common general software issues associated with the Pentaho
* [**Security issues**](/pdia-admin/troubleshooting-overview-cp/security-issues.md)

  Log file output, signs of configuration errors, and possible issues during LDAP configuration
* [**Pentaho Server issues**](/pdia-admin/troubleshooting-overview-cp/pentaho-server-issues.md)

  Common issues associated with the Pentaho Server
* [**Pentaho Repository issues**](/pdia-admin/troubleshooting-overview-cp/pentaho-repository-issues.md)

  Common issues associated with the Pentaho Repository


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/pdia-admin/troubleshooting-overview-cp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.