Manta Node CLI

Here’s the command to start the Manta Node:

$ manta_node --help
usage: manta_node [-h] [--version] [--m_host M_HOST] [--m_port M_PORT] [--ls_host LS_HOST] [--ls_port LS_PORT] [--data_folder DATA_FOLDER] [--log_filename LOG_FILENAME] [--secured_token SECURED_TOKEN] [--ca_port CA_PORT] [--alias ALIAS] [--random_id] [--debug] [--verbose]

Manta Node CLI

optional arguments:
<...>

Explanation of the options

Flag

Description

--m_host

Hostname or IP address of the Manta Manager. This must be accessible by the Manta Node.

--m_port

Port on which the Manta Manager is running. The default gRPC port is typically 50051.

--ls_host

Hostname or IP address of the Light Server. Defaults to localhost.

--ls_port

Port for the Light Server. Defaults to 50052.

--data_folder

Folder containing the data to be processed by the tasks running in the Docker containers.

--log_filename

Path to the log file where Manta Node will write its logs.

--secured_token

Token provided by the Manta Manager in secured mode for the first connection.

--ca_port

Port for the Certification Authority. Defaults to 50050.

--alias

Alias name for convenient selections

--random_id

Make Node ID as a random ID

--debug

Debug mode - All logs are printed and saved into a file.

-v

Increases the verbosity of logs. Use -v, -vv, or -vvv to increase the verbosity level.

Warning

The combination -vvv with --debug allows you to print all logs (INFO, DEBUG, ERROR) and also store these logs in an embedded database (file: .manta/traces.db). By removing --debug, you will only store logs in the embedded database even if they are not printed. If you change -vvv to -v, only ERROR will be saved.