MEMSQL-MONITOR

On this page

Starts monitoring an existing SingleStore node running on local or remote hosts.

Usage

usage: memsql-ops memsql-monitor [--settings-file SETTINGS_FILE] [--async]
                                 [-h HOST] [-P PORT] [-u USER] [-p [PASSWORD]]
                                 [--single-box]

Start monitoring a SingleStore node in MemSQL Ops.

optional arguments:
  --settings-file SETTINGS_FILE
                        A path to a MemSQL Ops settings.conf file. If not set,
                        we will use the file in the same directory as the
                        MemSQL Ops binary.
  --async               If this option is true, we will exit without waiting
                        for MemSQL Ops to monitor the node.
  -h HOST, --host HOST  The host for the SingleStore node. If this is not
                        specified, we will use the local host.
  -P PORT, --port PORT  The port for the SingleStore node.
  -u USER, --user USER  The user to use for the SingleStore node.
  -p [PASSWORD], --password [PASSWORD]
                        The password to use for the SingleStore node. Leave blank
                        to read the MEMSQL_PASSWORD environment variable, or
                        have a password prompt if MEMSQL_PASSWORD is not set.
  --single-box          If this is true, we will not attempt to attach this
                        SingleStore node to the rest of the cluster.

Last modified: April 25, 2023

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