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

VC/hostd/vmx files are out of sync in vSAN (55761)

Last Updated: 7/17/2023Categories: TroubleshootingTotal Views: 5559Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

VMs are being detected out of sync when using vsan.check_state in RVC.

In vsan.check_state log file, you see entries similar to,

2018-05-29 14:41:48 +0000: Step 1: Check for inaccessible vSAN objects
Detected 0 objects to be inaccessible
2018-05-29 14:41:49 +0000: Step 2: Check for invalid/inaccessible VMs
2018-05-29 14:41:49 +0000: Step 3: Check for VMs for which VC/hostd/vmx are out of sync
Find the list of VMs for which VC/hostd/vmx are out of synced.

Purpose

Identify and resolve out of sync VM's in vSAN.

Cause

If VM has migrated from one ESXi host to another, there can be a leftover/ghost process on the original ESXi host, which can lead to the out of sync status in RVC.

Impact / Risks

If killing a process, ensure the command is run on the correct ESXi host, so as not to affect any running VM.

Resolution

For each VM in the list of out of sync VM's from the output of the vsan.check_state command, check in vCenter which ESXi host the VM is actually running on.

On each ESXi host in the vSAN cluster, use the LSOF (list open files) command to search for running processes related to the VM.

# lsof | grep "VM name"

"Process ID"       "Process name"

If a running process is found for the VM, even though the VM is actually running on a different ESXi host, this is the cause of the out of sync state. Kill this ghost process running the command,

kill -9 "Process ID"

Re-run vsan.check_state, and confirm the VM is no longer out of sync.

Note: Ensure the process being killed is the ghost process, and not the actual running process for the VM on the ESXi host the VM is running on.

Related Information

ESXi hosts showing out of sync with distributed switch

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

Take Our Survey

Support Assistant