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, collect a report and write it to a tar file on the host you execute the command from.

    sdb-report collect
    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 to check the output for issues. Look at all FAIL output, such as this example:

    sdb-report check --report-path your_report_path.tar.gz
    ✘ 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 and be sure to take note of any WARNINGS in the check --report output for future

In this section

Last modified: July 29, 2024

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined
  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined
  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
    --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
    --bundle undefined \
    --new-bundle-format -
    Verified OK