HMS service fails to start on VR 8.2 with error "Could not resolve placeholder 'hks-threadpool-size' in value"
book
Article ID: 307245
calendar_today
Updated On:
Products
VMware Live RecoveryVMware 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.xmlfile 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 -->