Error: "Error creating clone of primary node to this standby server using repmgr"

Products

• VMware Cloud Director

Issue/Introduction

• Deploying a Standby cell results in the following error message located in /opt/vmware/var/log/vcd/configure-vcd.log
  
  

  Creating repmgr standby configuration. 
setup-repmgr-standby.sh | systemd[l]: Started VMware Postgres database server. 
setup-repmgr-standby.sh | Stopping vpostgres service

  Creating repmgr standby configuration
setup-repmqr-standby.sh | Creating repmgr standby configuration.
configure-repmgr.sh | Creating repmgr-node-id
configure-repmgr.sh | Writing /opt/vmware/vpostgres/current/etc/repmgr.conf 

  Cloning primary database to standby using repmgr. This may take a long time, depending on database size. 
setup-repmqr-standby.sh I Cloning primary database to standby using repmqr. This may take a long time, depending on database size. 
The following command line errors were encountered: 
unknown repmgr action 'repmgr standby' 
too many command-line arguments (first extra is "clone") 
Try -repmgr --help" for more information. 

  Error creating clone of primary node to this standy server using repmgr 
setup-repmgr-standby.sh | [ERROR] Error creating clone of primary node to this standy server using repmgr 
setupvcd.sh | [ERROR] Failed to configure repmgr on this standby. Check /opt/vmware/var/log/vcd/configure-vcd.log for additional information. Aborting.
configure-vcd.sh | [ERROR] setupvcd script failed to execute. 
cleanup-vcd.sh | Starting cleanup script. 
cleanup-vcd.sh | The following error code was provided as argument to script: 15 
cleanup-vcd.sh | Attempting cleanup on standby appliance. 
cleanup-vcd.sh | Executing configure_vcd base cleanup. 
cleanup-vcd.sh | Executing repmgr standby cleanup. 
cleanup-vcd.sh | standby unregister not required, based upon error code provided. 
cleanup-vcd.sh | Resetting remaining repmgr and vpostgres configuration back to initial state. 
cleanup-vcd.sh | Unmounting NFS share and cleaning up letc/fstab. 
cleanup-vcd.sh | Executing clear ovfenv params. 

Environment

• 10.x
• 10.3.3
• 10.5

Cause

This can be caused by missing database connection properties in the responses.properties file located on the transfer director /opt/vmware/vcloud-director/data/transfer/. 

Resolution

1. Copy the correctly formed responses.properties file from the Primary cell located in /opt/vmware/vcloud-director/etc/responses.properties to the transfer directory located in /opt/vmware/vcloud-director/data/transfer
2. Re-attempt the Standby configuration phase in the VMware Cloud Director appliance management user interface. See Configure Your VMware Cloud Director Standby and Application Cells

Additional Information

In a working environment you can see the "connection string" line in the /opt/vmware/var/log/vcd/configure-vcd.log... 

Creating repmgr standby configuration. 
setup-repmqr-standby.sh | systemd[l]: Started VMware Postgres database server. 
setup-repmgr-standby.sh | Stopping vpostgres service 

Creating repmgr standby configuration.
setup-repmqr-standby.sh | Creating repmgr standby configuration. 
configure-repmgr.sh | Creating repmgr-node-id 
configure-repmgr.sh | Writing /opt/vmware/vpostgres/current/etc/repmgr.conf 

Cloning primary database to standby using repngr. This may take a long time, depending on database size. 
setup-repmgr-standby.sh | Cloning primary database to standby using repmgr. This may take a long time, 
depending on database size. 
NOTICE: destination directory " /var/vrnwdre/vpostgres/current/pgddtd" provided 
INFO: connecting to source node 
DETAIL: connection string is: host=X.X.X.X user=repmgr 
DETAIL : current installation size ts 323 MB 
NOTICE: checking for available walsenders on the source node (2 required) 
NOTICE: checking replication connections can be made to the source server (2 required) 
WARNING: directory '/var/vmware/vpostgres/current/pgdata" exists but is not empty 
NOTICE: -F/--force provided - deleting existing data directory "/var/vmware/vpostgres/current/pgdata" 
NOTICE: starting backup (using pg_basebackup).. 
HINT: this nay take some time; consider using the -cl.-fast-checkpoint option 
INFO: executing: 
/opt/vmware/vpostgres/current/bin/pg basebackup -I "repmgr base backup" 
-D /var/vmware/vpostgres/current/pgdata 
NOTICE: standby clone (using pg basebackup) complete 
NOTICE: you can now start your PostgreSQL server