Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VMware Cloud Foundation HMS or LCM components may fail to backup or upgrade (52395)

Last Updated: 9/6/2021Categories: TroubleshootingTotal Views: 3311Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

LCM fails to upgrade HMS or LCM agent or components

The ownership of the /opt/vrack/hms or /home/vrack/lcm directory and/or files under it on the SDDC Manager Controller virtual machine is something other than vrack:vfabric

In the /home/vrack/vrm/logs/hms-upgrade.log file, you see messages similar to:

2018-01-07 23:06:58.906 ERROR [main] [com.vmware.vrack.hms.common.util.FileUtil]       Failed to move directory '/opt/vrack/hms' as '/home/vrack/VMware/vRack/nfs-           mount/lcm/repo/hms/upgrade/cf9157c7-75d1-4d49-8304-aa782e6b3387/hms'.
java.io.FileNotFoundException: /opt/vrack/hms/hms.sh.orig (Permission denied)

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Resolution

To resolve this issue, ensure that the /opt/vrack/hms or /home/vrack/lcm/lcm-app/conf folder and files are all owned by the vrack user.

SSH as the root user to the SDDC Manager Controller virtual machine.

Run this command to check permissions on HMS folder and files:

​ls -lah /opt/vrack/hms

Note: You see output similar to:

drwxr-xr-x 8 vrack vfabric 4.0K Jan 12 21:32 .
drwxr-xr-x 3 vrack vfabric 4.0K Nov 27 14:08 ..
drwxr-xr-x 2 vrack vfabric 4.0K Nov 27 14:08 certmgmt
drwxr-xr-x 2 vrack vfabric 4.0K Nov 27 14:08 config
-rw-r--r-- 1 root  root       5 Jan 12 21:32 hms-agent.pid
-rwxr-xr-x 1 vrack vfabric  314 Nov 27 13:48 hms.service
-rwxr-xr-x 1 vrack vfabric 6.3K Nov 27 13:48 hms.sh
-rwxr-xr-x 1 vrack vfabric 6.3K Nov 27 13:48 hms.orig.sh
drwxr-xr-x 2 vrack vfabric  12K Nov 27 14:08 lib
drwxr-xr-x 2 vrack vfabric 4.0K Jan 12 21:32 logs
drwxr-xr-x 2 vrack vfabric 4.0K Nov 27 14:08 plugin-jars
drwxr-xr-x 2 vrack vfabric 4.0K Nov 27 14:08 upgrade-config

3. Change to the  /opt/vrack/hms directory:cd /opt/vrack/hms

4. Run the following command to change ownership and permissions on the HMS folder and files except the hms-agent.pid file:

chown -R vrack:vfabric `ls | grep -v .pid`
chmod -R 755 `ls | grep -v .pid`

5.Run this command to check permissions on LCM configuration folder and files:

ls -lah /home/vrack/lcm/lcm-app/conf

​Note: You see output similar to:

drwx------ 2 vrack vfabric 4.0K Mar 16 20:50 .
drwx------ 5 vrack vfabric 4.0K Jan  7 20:46 ..
-rw------- 1 vrack vfabric 1.1K Jan  6 18:45 VersionAlias.yml
-rw------- 1 vrack vfabric 5.8K Feb 11 00:46 application-evo.properties
-rw------- 1 vrack vfabric  405 Jan  6 18:45 cassandra-evo.properties
-rw------- 1 vrack vfabric   12 Jan  6 18:45 keystore.cred
-rw------- 1 vrack vfabric 1.4K Jan  6 18:45 lcm_bundle_trusted_sig.cert
-rw------- 1 vrack vfabric 2.6K Jan  6 18:45 lcm_default_keystore.p12
-rw------- 1 vrack vfabric  397 Jan  6 18:45 lcm_known_hosts
-rw------- 1 vrack vfabric 3.5K Jan  6 18:45 logback-evo.xml
-rw------- 1 vrack vfabric  134 Jan  6 18:45 logback.xml
-rw------- 1 vrack vfabric   70 Jan  6 18:45 zk-evo.properties

6. Change to the  /home/vrack/lcm/lcm-app/conf directory:

cd /home/vrack/lcm/lcm-app/conf

7.Run the following commands to change ownership and permissions on the LCM configuration folder and files:

chown vrack:vfabric *
chmod 600 *

8.Run the following commands to restart HMS and LCM services:
systemctl restart hms
systemctl restart lcm

9.Wait approximately 15 mins before reattempting the upgrade and then reattempt the upgrade in the UI.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
将 VMware Cloud Foundation 升级到版本 2.3 后，“VDI 工作流：配置 Horizon View Cloud Pod 架构”的任务挂起 (52397)

KB
•
如何从 VMware Cloud Foundation LCM 清单中移除对 ESXi 6.5 EP5 的引用 (52402)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

Take Our Survey

Support Assistant