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

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

book

Article ID: 369418

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • Standby cell deployment fails while trying to start vpostgres service
  • Following entries are seen under /opt/vmware/var/log/vcd/configure-vcd.log

    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.

Environment

VMware Cloud Director

Cause

vpostgres service fails to start when the sizing (CPU and memory) on newly deployed standby cell does not match with the primary cell. 

 

Resolution

All database cells in the cluster must be deployed with identical sizing (CPU and memory). Please refer these docs for more information:
VMware Cloud Director Appliance Sizing Options 10.4 
VMware Cloud Director Appliance Sizing Options 10.5 
VMware Cloud Director Appliance Sizing Options 10.6


Additional Information