I tested that all equipment at the production site was powered off momentarily, and then restarted.
But after the vSphere Replication Server 8.4 device is started, the HMS service cannot work normally.
The log is shown as follows:
root@vrs01-a [ ~ ]# tail -f /opt/vmware/logs/hms/hms.log | grep fail
java.lang.RuntimeException: HMS Server failed to start successfully:
java.lang.RuntimeException: HMS Server failed to start successfully:
java.lang.RuntimeException: HMS Server failed to start successfully:
java.lang.RuntimeException: HMS Server failed to start successfully:
root@vrs01-a [ ~ ]# systemctl status hms
* hms.service - vSphere Replication Management Server
Loaded: loaded (/lib/systemd/system/hms.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2021-03-14 04:09:45 UTC; 9s ago
Process: 6461 ExecStartPre=/opt/vmware/hms/bin/checkHmsConfigured.sh (code=exited, status=0/SUCCESS)
Process: 6434 ExecStartPre=/opt/vmware/hms/bin/checkHmsAppliance.sh (code=exited, status=0/SUCCESS)
Main PID: 6464 (java)
Tasks: 35 (limit: 8191)
Memory: 901.8M
CGroup: /system.slice/hms.service
`-6464 /usr/java/default/bin/java -Dfile.encoding=UTF-8 -XX:MetaspaceSize=128m -Xloggc:/opt/vmware/hms/logs/hms-gc.log -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCCause -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFi>
Mar 14 04:09:45 vrs01-a.corp.local systemd[1]: Starting vSphere Replication Management Server...
Mar 14 04:09:45 vrs01-a.corp.local systemd[1]: Started vSphere Replication Management Server.
lines 1-13/13 (END)
I think it might be a bug？
VRS 8.3.1 encountered a similar situation before, and it didn’t happen after upgrading to 8.3.1.2.
