FOLLOW

On this page

Set the local MemSQL Ops agent to follow the primary MemSQL Ops agent on another host.

The follow command is used for offline installations with limited SSH access between machines. If SSH access is possible between machines in the intended cluster, SingleStore recommends using the MemSQL Ops web UI or the AGENT-DEPLOY command to connect MemSQL Ops.

To follow a primary MemSQL Ops agent that uses an API token other than the default token, you must specify the --api-token <token> argument with the token’s value.

Usage

usage: memsql-ops follow [--settings-file SETTINGS_FILE] -h HOST [-P PORT]
                         [--api-token API_TOKEN]

Connect the local MemSQL Ops agent to the primary agent.

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.
  --api-token API_TOKEN
                        The API token of the primary agent if other than the default.
  -h HOST, --host HOST  The primary agent's host.
  -P PORT, --port PORT  The primary agent's port.
  --api-token API_TOKEN
                        The API token to use when connecting to the specified
                        primary agent.

Last modified: October 31, 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.

(Optional) Run the following command to view the associated signature files.
Shell
```
curl undefined
```
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.
  Shell
```
curl -O undefined
```

After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

Shell

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