vSphere Replication disconnected and "Failed to Register VRMS"

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:
1. Unable to edit Protection Groups in SRM.

2. SRM reconfigures successfully but shows 'Inaccessible' errors on the vCenter interface

3. Attempting to reconfigure vSphere Replication through the VAMI interface on port 5480 fails with "Failed to Register VRMS"

4. The services hms-vpostgres and hms are stopped

5. Logging shown below:

/var/log/vmware/dr/drconfig.log
2025-05-21T17:41:45.758Z error drconfig[00961] [SRM@6876 sub=ConfigureVrmsOp opID=6f3b202b-3723-487b-xxxxxxxx-configure:4466] command:
--> /usr/bin/python /opt/vmware/share/htdocs/service/hms/cgi/hms-dr.py --cmd saveembeddedconf --ls https://vCenter.domain.local:443/lookupservice/sdk --lsthumbprint xxxxxxxxx --ssoadmin [email protected] --vcip vCenter.domain.local --vcport
80 --vcthumbprint xxxxxxxxx  --servername vCenter.domain.local --hmshost xx.xx.xx.xx
.20 --hmsport 8043 --self-moid vm-xxxx--adminmail [email protected] --secmail [email protected] --strict-certs 1
--> stdout:
--> {"error": "Bad exit code: 1"}
-->
--> stderr:
--> psql.bin: could not connect to server: No such file or directory
-->     Is the server running locally and accepting
-->     connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

Environment

vSphere Replication (All Versions)

Cause

hms-vpostgres and hms services are stopped

Resolution

1. Reconfigure VRMS via the VAMI interface on port 5480
Reconfigure vSphere Replication

2. Start the hms-vpostgres service
Use the VAMI interface on port 5480 -> Services tab, or the command service hms-vpostgres restart

3. Start the hms service
Use the VAMI interface on port 5480 -> Services tab, or the command service hms restart