Error "configure-vcd script failed to complete" while trying to add a new standby cell in VMware Cloud Director.

Products

• VMware Cloud Director

Issue/Introduction

• While adding a new standby cell, the below error is thrown in the UI.

  Invoking setupvcd script.
  setupvcd script failed to execute.
  For more details, check /opt/vmware/var/log/vcd/configure-vcd.log.
  An error occurred during configuration, running cleanup...
  Starting cleanup script.
  Attempting cleanup on standby appliance.
  standby unregister not required, based upon error code provided.
  Resetting remaining repmgr and vpostgres configuration back to initial state.
  returncode:15

 

• In /opt/vmware/var/log/vcd/configure-vcd.log contains you see the entries regarding the timeout while connecting to the primary cell DB IP:

  YYYY-MM-DD HH:MM:SS | configure-repmgr.sh | Writing /opt/vmware/vpostgres/current/etc/repmgr.conf 
  Cloning primary database (PrimaryCell_DB_IP) to standby using repmgr. This may take a long time, depending on database size. 
  YYYY-MM-DD HH:MM:SS | setup-repmgr-standby.sh | Cloning primary database (PrimaryCell_DB_IP) to standby using repmgr.
  This may take a long time, depending on database size. 
  NOTICE: destination directory "/var/vmware/vpostgres/current/pgdata" provided 
  INFO: connecting to source node 
  DETAIL: connection string is: user=repmgr host=PrimaryCell_DB_IP gssencmode=disable 
  ERROR: connection to database failed 
  DETAIL: connection to server at "PrimaryCell_DB_IP", port 5432 failed: timeout expired 
  
  Error creating clone of primary node to this standy server using repmgr 
  YYYY-MM-DD HH:MM:SS | setup-repmgr-standby.sh | [ERROR] Error creating clone of primary node to this standby server using repmgr

Environment

VMware Cloud Director 10.6

Cause

The /opt/vmware/var/log/vcd/configure-vcd.log file shows a connection timeout to the old cell IP address instead of the current primary cell database IP:

connection to server at "<Incorrect Primary DB IP>", port 5432 failed: timeout expired

 

The old cell IP is still referenced in the file: /opt/vmware/vcloud-director/data/transfer/responses.properties. This file lists incorrect primary cell which no longer exists in database.jdbcUrl field.  The old IP belonged to a cell that was previously the primary but has been unregistered from the cluster.

 

Resolution

• Review the file /opt/vmware/vcloud-director/etc/responses.properties on the primary cell to confirm the correct primary Database IP address is present in database.jdbcUrl field.

• Back up the /opt/vmware/vcloud-director/data/transfer/responses.properties file:

  cp /opt/vmware/vcloud-director/data/transfer/responses.properties /opt/vmware/vcloud-director/data/transfer/responses.properties.backup

• Copy the responses.properties file from the primary appliance to the transfer share file, which has the correct primary cell IP address.

  cp /opt/vmware/vcloud-director/etc/responses.properties /opt/vmware/vcloud-director/data/transfer/responses.properties

• Re-submit the NFS mount point to join the standby cell in VCD cluster.

 

Additional Information

Refer: Configure Your VMware Cloud Director Standby and Application Cells