User guide

If a server does not recognize the provided control password, it will respond with a failure
message:
rdbthincontrol> show active servers
Failed to connect <CONTROL>
No Rdb Thin Server connection has been established
Unable to connect to server //localhost:1701/
Failed to connect <CONTROL>
No Rdb Thin Server connection has been established
Unable to connect to server //localhost:1711/
rdbthincontrol>
Contents
6.2 Connecting to Servers
The majority of commands that can be issued from the controller require a valid control
connection to be established with a server. If valid connection information is provided at
the controller invocation (node, port, user and password), the controller will automatically
attempt to connect to the specified server when the controller starts up.
If user and password are provided at the controller invocation, this information will be
maintained for the entire controller session and will be used in subsequent connection
request unless explicitly overridden on the command statement.
Commands will only be carried out on a server if a control connection has been established,
which requires the correct control password to be provided during the connect request. See
Control Password
for more information of this password.
This control connection may be an explicit connection established for the session by using
the Connect command or may be implicitly established if a command is issued to a server
that requires control access to execute successfully. Many controller commands allow
server connection information to be specified, indicating which server to apply the
command. In addition, the connection information may provide a username and password
to use for that server.
Format
<command> <server_connection>
The <server_connection> information is comprised of a server identification string and
optional connection username and control password:
Format
74