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

# InnoDB Troubleshooting Overview

As with most errors, first take a look at the contents of the [MariaDB error log](/docs/server/server-management/server-monitoring-logs/error-log.md). If dealing with a deadlock, setting the [innodb\_print\_all\_deadlocks](/docs/server/server-usage/storage-engines/innodb/innodb-system-variables.md) option (off by default) will output details of all deadlocks to the error log.

It can also help to enable the various [InnoDB Monitors](/docs/server/server-usage/storage-engines/innodb/innodb-monitors.md) relating to the problem you are experiencing. There are four types: the standard InnoDB monitor, the InnoDB Lock Monitor, InnoDB Tablespace Monitor and the InnoDB Table Monitor.

Running [CHECK TABLE](/docs/server/reference/sql-statements/table-statements/check-table.md) will help determine whether there are errors in the table.

For problems with the InnoDB Data Dictionary, see [InnoDB Data Dictionary Troubleshooting](/docs/server/server-usage/storage-engines/innodb/innodb-troubleshooting/innodb-data-dictionary-troubleshooting.md).

## See Also

* [InnoDB Data Dictionary Troubleshooting](/docs/server/server-usage/storage-engines/innodb/innodb-troubleshooting/innodb-data-dictionary-troubleshooting.md)
* [InnoDB Recovery Modes](/docs/server/server-usage/storage-engines/innodb/innodb-troubleshooting/innodb-recovery-modes.md)
* [Error Codes](/docs/server/reference/error-codes.md)

<sub>*This page is licensed: CC BY-SA / Gnu FDL*</sub>

{% @marketo/form formId="4316" %}


---

# 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://mariadb.com/docs/server/server-usage/storage-engines/innodb/innodb-troubleshooting/innodb-troubleshooting-overview.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.