repmgr daemon stop — Stop the repmgrd daemon
This command stops the repmgrd daemon on the local node.
By default, repmgr will wait for up to 15 seconds to confirm that repmgrd
stopped. This behaviour can be overridden by specifying a diffent value using the --wait
option, or disabled altogether with the --no-wait option.
If PostgreSQL is not running on the local node, under some circumstances repmgr may not be able to confirm if repmgrd has actually stopped.
The repmgr.conf parameter repmgrd_service_stop_command
must be set for repmgr daemon stop to work; see section
repmgr daemon stop configuration for details.
repmgr daemon stop will execute the command defined by the
repmgrd_service_stop_command parameter in repmgr.conf.
This must be set to a shell command which will stop 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_stop_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.
--dry-runCheck prerequisites but don't actually attempt to stop repmgrd.
This action will output the command which would be executed.
-w--waitWait for the specified number of seconds to confirm that repmgrd stopped successfully.
Note that providing --wait=0 is the equivalent of --no-wait.
--no-waitDon't wait to confirm that repmgrd stopped successfully.
This is equivalent to providing --wait=0.
The following parameter in repmgr.conf is relevant
to repmgr daemon stop:
repmgrd_service_stop_command
repmgr daemon stop will execute the command defined by the
repmgrd_service_stop_command parameter in repmgr.conf.
This must be set to a shell command which will stop 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_stop_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.
One of the following exit codes will be emitted by repmgr daemon stop:
SUCCESS (0)repmgrd could be stopped.
ERR_BAD_CONFIG (1)
repmgrd_service_stop_command is not defined in
repmgr.conf.
ERR_REPMGRD_SERVICE (27)repmgrd could not be stopped.