ltcluster daemon start — Start the ltclusterd daemon on the local node
This command starts the ltclusterd service on the local node.
By default, ltcluster will wait for up to 15 seconds to confirm that ltclusterd
started. This behaviour can be overridden by specifying a diffent value using the --wait
option, or disabled altogether with the --no-wait option.
The ltcluster.conf parameter ltclusterd_service_start_command
must be set for ltcluster daemon start to work; see section
ltcluster daemon start configuration for details.
--dry-runCheck prerequisites but don't actually attempt to start ltclusterd.
This action will output the command which would be executed.
-w--waitWait for the specified number of seconds to confirm that ltclusterd started successfully.
Note that providing --wait=0 is the equivalent of --no-wait.
--no-waitDon't wait to confirm that ltclusterd started successfully.
This is equivalent to providing --wait=0.
The following parameter in ltcluster.conf is relevant
to ltcluster daemon start:
ltclusterd_service_start_command
ltcluster daemon start will execute the command defined by the
ltclusterd_service_start_command parameter in ltcluster.conf.
This must be set to a shell command which will start ltclusterd;
if ltcluster was installed from a package, this will be the service command defined by the
package.
If ltcluster was installed from a system package, and you do not configure
ltclusterd_service_start_command to an appropriate service command, this may
result in the system becoming confused about the state of the ltclusterd
service; this is particularly the case with systemd.
One of the following exit codes will be emitted by ltcluster daemon start:
SUCCESS (0)
The ltclusterd start command (defined in
ltclusterd_service_start_command) was successfully executed.
If the --wait option was provided, ltcluster will confirm that
ltclusterd has actually started up.
ERR_BAD_CONFIG (1)
ltclusterd_service_start_command is not defined in
ltcluster.conf.
ERR_DB_CONN (6)ltcluster was unable to connect to the local LightDB node.
LightDB must be running before ltclusterd
can be started. Additionally, unless the --no-wait option was
provided, ltcluster needs to be able to connect to the local LightDB node
to determine the state of ltclusterd.
ERR_LTCLUSTERD_SERVICE (27)
The ltclusterd start command (defined in
ltclusterd_service_start_command) was not successfully executed.
This can also mean that ltcluster was unable to confirm whether ltclusterd
successfully started (unless the --no-wait option was provided).