# Troubleshooting

## Introduction

This guide can be used to troubleshoot system, node, or general query performance issues. Each page is a step with a “Next Steps” section at the end, which provides recommendations for what the reader can do next based on the information they uncover in their current step. Overall, generating and checking a cluster report is the best place to start your troubleshooting journey.

## Collecting and Checking the Cluster Report

1. Using [sdb-report collect](https://docs.singlestore.com/db/v9.1/reference/singlestore-tools-reference/sdb-report-commands/collect.md), collect a report and write it to a tar file on the host you execute the command from.
   ```shell
   sdb-report collect

   ```
   ```output

   Toolbox will perform the following actions:
     · Execute 74 collectors
   ✓ Collected report for host 127.0.0.1
   Report written to report-2021-01-08T021531.tar.gz
   ```

2. Use [sdb-report check](https://docs.singlestore.com/db/v9.1/reference/singlestore-tools-reference/sdb-report-commands/check.md) to check the output for issues. Look at all `FAIL` output, such as this example:
   ```shell
   sdb-report check --report-path your_report_path.tar.gz

   ```
   ```output

   ✘ transparentHugepage ........................... [FAIL]
   FAIL /sys/kernel/mm/transparent_hugepage/enabled is [always] on 172.17.0.2
   NOTE https://docs.memsql.com/memsql-report-redir/transparent-hugepage
   ✘ leavesNotOnline ........................ [FAIL]
   FAIL leaf node on host 127.0.0.1 and port 3308 is offline
   Some checks failed: 1 FAIL, 1 PASS, 1 UNAVAILABLE
   ```

## Next Steps

* If the cluster report does not uncover any `FAIL` output, move onto [Step 1](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/troubleshooting/1-identifying-expensive-queries.md) and be sure to take note of any `WARNINGS` in the `check --report` output for future

## In this section

* [1. Identifying Expensive Queries](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/troubleshooting/1-identifying-expensive-queries.md)
* [2. Investigating Expensive Queries](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/troubleshooting/2-investigating-expensive-queries.md)
* [3. Are any queries waiting on something?](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/troubleshooting/3-are-any-queries-waiting-on-something.md)
* [4. Are key resources being overused?](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/troubleshooting/4-are-key-resources-being-overused.md)
* [5. Are there other ongoing operational activities?](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/troubleshooting/5-are-there-other-ongoing-operational-activities.md)
* [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.md)
* [7. Checking Partition Number and Data Skew](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/troubleshooting/7-checking-partition-number-and-data-skew.md)
* [8. Checking for System Changes and Log Hints](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/troubleshooting/8-checking-for-system-changes-and-log-hints.md)

***

Modified at: July 29, 2024

Source: [/db/v9.1/user-and-cluster-administration/troubleshooting/](https://docs.singlestore.com/db/v9.1/user-and-cluster-administration/troubleshooting/)

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