This is a known issue affecting VMware Cloud Foundation 2.2. Currently, there is no resolution.Workaround:
To work around this issue, on the SDDC Manager VM, restart HMS.
If the problem persists, increase the memory limit:
- SSH to the SDDC Manager VM and change to the
/opt/vrack/hms
directory. - Check the current memory allocation for HMS.
grep -i "xmx" hms.sh
You should see output similar to:
/bin/su $HMS_USER -c ""$JAVA" -Xmx2048m -XX:MaxPermSize=512m -classpath "$CLASSPATH" Dhms.config.file=$HMS_CONFIG $JETTY_LOGGING_OPT $HMS_LOGGING_CONFIG com.vmware.vrack.hms.HmsApp >> $HMSA_CONSOLE_LOG_FILE 2>&1 &"
In this example, the HMS memory allocation is set to the default, 2048 MB.
- Increase the memory to 4096MB (or higher as needed).
sed -i -e 's/Xmx2048/Xmx4096/g' hms.sh
- Optionally, confirm the new memory configuration.
grep -i "xmx" hms.sh
/bin/su $HMS_USER -c ""$JAVA" -Xmx4096m -XX:MaxPermSize=512m -classpath "$CLASSPATH" -Dhms.config.file=$HMS_CONFIG $JETTY_LOGGING_OPT $HMS_LOGGING_CONFIG com.vmware.vrack.hms.HmsApp >> $HMSA_CONSOLE_LOG_FILE 2>&1 &"
- Restart the HMS by running this command:
systemctl restart hms
- Restart Workflow containing the affected task.