HMS service fails to start on VR 8.2 with error "Could not resolve placeholder 'hks-threadpool-size' in value"

Products

• VMware Live Recovery
• VMware vSphere ESXi

Issue/Introduction

Symptoms:
HMS service does not start and 'Bad Exit Code' is reported on VAMI page when trying to register VR with vCenter

Environment

VMware vSphere Replication 8.x

Cause

This is caused due to missing values in hms-configuration.xml file which may have not gotten updated correctly during an upgrade

Resolution

- Open /opt/vmware/hms/conf/hms-configuration.xml file and validate if the below entries are present:

<!--
Max EventLog counts - note that if there are more then the specified event logs they will potentially
be cleaned (if processsed) even if their age
-->

<hms-eventlog-max-in-count>100000</hms-eventlog-max-in-count>
<hms-eventlog-max-out-count>2600000</hms-eventlog-max-out-count>

<hks-retry-millis>30000</hks-retry-millis>
<hks-threadpool-size>10</hks-threadpool-size>
<hks-default-timeout-seconds>180</hks-default-timeout-seconds>

<!-- use bigger delay to enable batching -->
<hks-sync-delay-millis>20</hks-sync-delay-millis>

<!-- VSAN DP resume protection max retries -->
<vsandp-resume-protection-max-retries>20</vsandp-resume-protection-max-retries>

- Edit the file and make the required changes if values do not match OR add the values if not present in the configuration file