# Troubleshooting

This section is built from real operator issues seen in `#fil-curio-help`, with notes tied back to the actual Curio code paths.

Start here if you are:

* stuck during setup/migration,
* seeing task failures in the UI,
* seeing repeated errors/warnings in logs,
* unsure what information to collect before asking for help.

## A simple mental model (helps you debug faster)

Most Curio incidents fall into one of these buckets:

1. Chain / Lotus connectivity

* Curio can’t talk to the full node, or the full node is unhealthy/out of sync.

2. Control plane (DB + scheduler)

* Yugabyte is slow/unhealthy, schema upgrades failed, or tasks are not being scheduled/claimed.

3. Data plane (storage + retrieval)

* the bytes aren’t where the system thinks they are (paths, indexes, URLs, permissions).

If you don’t know where to start: check **DB health** first. A sick DB creates “random” symptoms everywhere.

## Quick links

* [Collect debug info](/troubleshooting/collect-debug-info.md) (copy/paste checklist)
* [Common errors](/troubleshooting/common-errors.md) (error string → meaning → next step)
* [Market / indexing troubleshooting](/curio-market/troubleshooting.md)
* [YugabyteDB troubleshooting](/administration/yugabyte-troubleshooting.md)


---

# 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://docs.curiostorage.org/troubleshooting.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.