> For the complete documentation index, see [llms.txt](https://chameleoncloud.gitbook.io/chi-in-a-box/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chameleoncloud.gitbook.io/chi-in-a-box/operations/runbooks/mysqlhostdown.md).

# MySQL Host Down

**Summary**: The MySQL process is no longer reporting metrics. This can mean the process has failed, it no longer has networking, or the monitoring is misconfigured.

**Consequences**: If the MySQL process is indeed down or unreachable, then most of the system will not be operational. If this is the case, other alerts will likely fire around OpenStack APIs being down, amongst others. If no other alerts are firing, it's possible it is only a monitoring misconfiguration. Restoring a down or unreachable MySQL process should be a high-priority item in the event of an outage as most systems rely on it.

#### Possible causes

**The MySQL process has failed**:

1. Log in to the MySQL host and check either the systemd service (`systemctl status mariadb`) or the Docker container `docker inspect mariadb`.
2. If it is down, investigate the logs (`/var/log/mariadb/mariadb.log` or `docker logs mariadb`) for hints. If it is up, check out the other possible causes.

**Routing to MySQL has failed**: It is possible that the service is up, but HAProxy is failing to route traffic.

1. Check HAProxy logs (`/var/log/kolla/haproxy`) for errors.
2. See if MySQL responds to a local IP, but not the VIP assigned by keepalive (the value of `kolla_internal_vip_address`); if that is the case, the issue could be HAProxy; it could be missing configuration instructing it to route traffic to MySQL (this might happen during an upgrade).

**Monitoring has failed**: If everything seems fine, yet the alert is firing, the issue is likely with the monitoring.

1. Check if the `mysqld_exporter` container is running, and if any errors are logged. If the username/password for the monitoring user has changed, or if the bind address changes, the Prometheus exporter will be unable to connect.
2. Re-run the Prometheus playbook `./cc-ansible --playbook playbooks/prometheus.yml` to re-deploy the monitoring infrastructure.


---

# 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://chameleoncloud.gitbook.io/chi-in-a-box/operations/runbooks/mysqlhostdown.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.