VCD standby cell deployment fails with error "The following error code was provided as argument to script: 16"

Products

• VMware Cloud Director

Issue/Introduction

VCD standby cell deployment or adding a new cell fails

Environment

vCloud Director 10.4.x

Cause

vPostgres Service fails to start with expection 'The following error code was provided as argument to script: 16'

 

Resolution

Need to check the sizing guidelines of the cells in the cluster.

All the cells should be of same configuration

..>Matching configuration on all the cells should resolve the issue 

Cloud Director Appliance Sizing Guidelines :
https://docs.vmware.com/en/VMware-Cloud-Director/10.0/com.vmware.vcloud.install.doc/GUID-80E5D617-7266-4301-935B-19B96E395549.htmlAs per the guidelines, all cells should have the same configuration (vCPU, RAM, etc..).

Additional Information

Configure-vcd.log indicates below:

INFO: executing:
 /opt/vmware/vpostgres/current/bin/pg_basebackup -l "repmgr base backup" -D /var/vmware/vpostgres/current/pgdata -h 10.xx.xx.xx -p 5432 -U repmgr -X stream
NOTICE: standby clone (using pg_basebackup) complete.
NOTICE: you can now start your PostgreSQL server.
HINT: for example: sudo /usr/bin/systemctl start vpostgres
HINT: after starting the server, you need to register this standby with "repmgr standby register"
Manually invoking vpostgres-reconfigure.py script
2022-03-23 07:38:51 | setup-repmgr-standby.sh | Manually invoking vpostgres-reconfigure.py script.
Invoking appliance-sync.sh again to refresh postgresql.conf file.
2022-03-23 07:38:51 | setup-repmgr-standby.sh | Invoking appliance-sync.sh again to refresh postgresql.conf file.
Starting and enabling vpostgres service.
2022-03-23 07:39:02 | setup-repmgr-standby.sh | Starting and enabling vpostgres service.
Job for vpostgres.service failed because the control process exited with error code.
See "systemctl status vpostgres.service" and "journalctl -xe" for details.
vpostgres was not enabled or started successfully.
2022-03-23 07:39:03 | setup-repmgr-standby.sh | [ERROR] vpostgres was not enabled or started successfully.
2022-03-23 07:39:03 | setupvcd.sh | [ERROR] Failed to configure repmgr on this standby. Check /opt/vmware/var/log/vcd/configure-vcd.log for additional information. Aborting.
2022-03-23 07:39:03 | configure-vcd.sh | [ERROR] setupvcd script failed to execute.
2022-03-23 07:39:03 | configure-vcd.sh | [ERROR] FATAL error: vpostgres service failed to start after standby clone. Check postgresql logs for more details.
2022-03-23 07:39:03 | configure-vcd.sh | [ERROR] postgresql log location: /var/vmware/vpostgres/current/pgdata/log/.
2022-03-23 07:39:03 | configure-vcd.sh | [ERROR] Resolve that FAILURE before retrying standby appliance configuration.
2022-03-23 07:39:03 | cleanup-vcd.sh | Starting cleanup script.
2022-03-23 07:39:03 | cleanup-vcd.sh | The following error code was provided as argument to script: 16
2022-03-23 07:39:03 | cleanup-vcd.sh | Attempting cleanup on standby appliance.
2022-03-23 07:39:03 | cleanup-vcd.sh | Executing configure_vcd_base_cleanup.
2022-03-23 07:39:03 | cleanup-vcd.sh | Executing repmgr_standby_cleanup.
2022-03-23 07:39:03 | cleanup-vcd.sh | standby unregister not required, based upon error code provided.
2022-03-23 07:39:03 | cleanup-vcd.sh | Resetting remaining repmgr and vpostgres configuration back to initial state.
2022-03-23 07:39:03 | cleanup-vcd.sh | Unmounting NFS share and cleaning up /etc/fstab.
2022-03-23 07:39:03 | cleanup-vcd.sh | Executing clear_ovfenv_params.