# 6. Checking Node, Partition, and Overall Database Health

The next step in troubleshooting your cluster is checking its overall health.

1. Go to the Studio Hosts and/or Nodes page(s) to ensure nodes are online. 

   * Run [show-leaves](https://docs.singlestore.com/db/v9.1/reference/singlestore-tools-reference/sdb-admin-commands/show-leaves.md) to get the `id` of any offline node. `sdb-admin show-leaves`
   * Then, bring the node(s) online with [start-node](https://docs.singlestore.com/db/v9.1/reference/singlestore-tools-reference/sdb-admin-commands/start-node.md). `sdb-admin start-node <node-id>`

2. Go to the Databases page, and examine the suspect database.

   * Click on the database, check the Partitions tab, and make sure everything is online and attached.

3. If there are offline or detached partitions, investigate the health of the nodes housing those partitions in Studio.

   ![Health Status of the partitions in the Database page.](https://images.contentstack.io/v3/assets/bltac01ee6daa3a1e14/blt52c9bc49415ddcdc/6a2c42fedc0899738a2f23e1/16083b57976854-ElDBrY.png)

## Next Steps

* If all nodes, partitions, and databases are healthy: continue to [Step 7](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/troubleshooting/7-checking-partition-number-and-data-skew.md).

***

Modified at: July 17, 2024

Source: [/db/v9.1/user-and-cluster-administration/troubleshooting/6-checking-node-partition-and-overall-database-health/](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/troubleshooting/6-checking-node-partition-and-overall-database-health/)

(An index of the documentation is available at /llms.txt)