repmgr cluster show indicates all nodes are running.The standby cell is unable to replicate the database from the primary cell, resulting in a broken replication state.
Gracefully shut down all cells and take a full backup or snapshot of all VCD appliances before making database modifications.
Establish an SSH session to the primary cell as root and obtain the node ID of the failed standby cell:
sudo -i -u postgres repmgr cluster show
Unregister the failed standby cell from the repmgr cluster:
sudo -i -u postgres repmgr standby unregister -f /opt/vmware/vpostgres/current/etc/repmgr.conf --node-id=#####
Establish an SSH session to the failed standby cell, stop the VCD service, and stop the database service:
service vmware-vcd stop
systemctl stop vpostgres.service
Remove the corrupted PostgreSQL database files on the failed standby cell:
rm -rf /var/vmware/vpostgres/current/pgdata
Re-clone the database from the primary cell to the failed standby cell:
sudo -i -u postgres repmgr -h ##### -U repmgr -d repmgr -f /opt/vmware/vpostgres/current/etc/repmgr.conf standby clone
Start the database service on the standby cell:
systemctl start vpostgres.service
Register the standby cell back into the repmgr cluster:
sudo -i -u postgres repmgr -h ##### -U repmgr -d repmgr -f /opt/vmware/vpostgres/current/etc/repmgr.conf standby register --force
Verify that replication is healthy and node status errors are resolved:
sudo -i -u postgres repmgr cluster show
sudo -i -u postgres repmgr node status
Start the VCD service on the standby cell:
service vmware-vcd start
For complex database synchronization issues, contact Broadcom Support.