repmgr daemon startrepmgrdstartingrepmgr daemon startrepmgr daemon startStart the repmgrd daemonDescription
This command starts the repmgrd daemon on the
local node.
By default, &repmgr; will wait for up to 15 seconds to confirm that repmgrd
started. This behaviour can be overridden by specifying a diffent value using the
option, or disabled altogether with the option.
Configurationrepmgr daemon start will execute the command defined by the
repmgrd_service_start_command parameter in repmgr.conf.
This must be set to a shell command which will start repmgrd;
if &repmgr; was installed from a package, this will be the service command defined by the
package. For more details see Appendix: &repmgr; package details.
If &repmgr; was installed from a system package, and you do not configure
repmgrd_service_start_command to an appropriate service command, this may
result in the system becoming confused about the state of the repmgrd
service; this is particularly the case with systemd.
Options
Check prerequisites but don't actually attempt to start repmgrd.
This action will output the command which would be executed.
Wait for the specified number of seconds to confirm that repmgrd
started successfully.
Note that providing is the equivalent of .
Don't wait to confirm that repmgrd
started successfully.
This is equivalent to providing .
Exit codes
One of the following exit codes will be emitted by repmgr daemon start:
The repmgrd start command (defined in
repmgrd_service_start_command) was successfully executed.
If the option was provided, &repmgr; will confirm that
repmgrd has actually started up.
repmgrd_service_start_command is not defined in
repmgr.conf.
&repmgr; was unable to connect to the local PostgreSQL node.
PostgreSQL must be running before repmgrd
can be started. Additionally, unless the option was
provided, &repmgr; needs to be able to connect to the local PostgreSQL node
to determine the state of repmgrd.
The repmgrd start command (defined in
repmgrd_service_start_command) was not successfully executed.
This can also mean that &repmgr; was unable to confirm whether repmgrd
successfully started (unless the option was provided).
See also, ,