START

On this page

Start the MemSQL Ops agent running on the local machine.

This command starts the MemSQL Ops agent. It includes additional arguments that allow users to customize attributes such as the agent port. For example, this command changes the agent port of the local MemSQL Ops instance.

memsql-ops start --port 8000

Usage

usage: memsql-ops start [--settings-file SETTINGS_FILE] [-f]
                        [-i INTERFACE | -h HOST | --use-hostname] [-P PORT]
                        [--ssl-port SSL_PORT] [-u USER] [--async]
                        [--ignore-root-error]

Start the MemSQL Ops 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.
  -f, --foreground      Run the agent in the foreground.
  -i INTERFACE, --interface INTERFACE
                        Bind the agent to the specified network interface.
                        Default is the first non-loopback interface.
  -h HOST, --host HOST  Bind the agent to the specified host. This overrides
                        other methods such as interface and automated
                        guessing.
  --use-hostname        If true, we will bind this agent to the machine's
                        hostname.
  -P PORT, --port PORT  Bind the agent to the specified port. By default we
                        will use port 9000.
  --ssl-port SSL_PORT   Bind the HTTPS web UI to the specified port (if an SSL
                        certificate has been added). By default we will use
                        port 9001.
  -u USER, --user USER  Run the agent as the specified user.
  --async               If true, we will return immediately without waiting
                        for the agent to be fully started. This has no effect
                        if --foreground is specified.
  --ignore-root-error   If set, MemSQL Ops will start even if we previously
                        started it with root privileges and it is now being
                        started by a non-root user.

Last modified: April 25, 2023

Was this article helpful?