VR fails to upgrade from 8.2 to 8.3 or 8.4

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:
2020-12-29 20:33:20.381 WARN com.mchange.v2.resourcepool.BasicResourcePool [C3P0PooledConnectionPoolManager[identityToken->z8kfltae1cw1n1l1rrgwos|11963225]-HelperThread-#1] (..log.slf4j.Slf4jMLog$Slf4jMLogger$WarnLogger) [] | com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@373800dd -- Acquisition
 Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception:
org.postgresql.util.PSQLException: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
    at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:280) ~[postgresql-jdbc-driver-8.3.0.jar:42.2.5]

Bad exit code 1. 

Cause

The version of vpostgres has been set in the /opt/vmware/hms/conf/embedded_db.cfg

Resolution

Revert  snapshot, change the EMB_DB_INSTALL_DIR to /opt/vmware/vpostgres/current and upgraded to 8.X

This was caused by the following. 

 

The updatecli.log shows the /opt/vmware/hms/conf/embedded_db.cfg as below.

+ '[' -r /opt/vmware/hms/conf/embedded_db.cfg ']'

+ source /opt/vmware/hms/conf/embedded_db.cfg

++ EMB_DB_INSTALL_DIR=/opt/vmware/vpostgres/9.5

++ EMB_DB_INSTANCE=vrmsdb

++ EMB_DB_VCTA_INSTANCE=vctadb

++ EMB_DB_USER=vrmsdb

++ EMB_DB_PASSWORD=unused

++ EMB_DB_STORAGE=/var/lib/vrmsdb

++ EMB_DB_MAX_CONNECTIONS=150


The correct value is 
 

The updatecli.log shows the embedded_db.cfg as below.

+ '[' -r /opt/vmware/hms/conf/embedded_db.cfg ']'

+ source /opt/vmware/hms/conf/embedded_db.cfg

++ EMB_DB_INSTALL_DIR=/opt/vmware/vpostgres/current

++ EMB_DB_INSTANCE=vrmsdb

++ EMB_DB_VCTA_INSTANCE=vctadb

++ EMB_DB_USER=vrmsdb

++ EMB_DB_PASSWORD=unused

++ EMB_DB_STORAGE=/var/lib/vrmsdb

++ EMB_DB_MAX_CONNECTIONS=150

Additional Information

Impact/Risks:
Ensure not to increase the VMDK of the appliance until the upgrade is successful as increasing the VMDK size requires snapshots to be removed.