# Troubleshooting Overview

{% hint style="info" %}
This page is focused on system-level development: It is geared toward developers or DBAs trying to diagnose why a specific instance is failing or crashing in a production or testing environment (e.g., interpreting error messages, handling crashes).
{% endhint %}

There are a number of ways MariaDB can result in a fault for you as the user. Getting a good clear understanding of the problem is the perfect way to get a good bug report to developers to allow them to fix your problem.

Like the [MariaDB Community Bug Reporting](https://github.com/mariadb-corporation/mariadb-docs/blob/main/server/reference/community/community/bug-tracking/reporting-bugs.md) says, start by searching for an existing bug. If its not found, or it not 100% clear that it applies to you, gain some additional information an include those in a new or perhaps and existing bug report.

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

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


---

# Agent Instructions: 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:

```
GET https://mariadb.com/docs/server/reference/product-development/mariadb-fault-finding/checking-mariadb.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.