Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

VPXD is crashing and creating core dump if there are hosts in not responding state in the SDRS enabled cluster (76132)

Last Updated: 8/6/2020Categories: TroubleshootingTotal Views: 6927Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

VPXD service crashes frequently if there are hosts in not responding state in the Storage DRS enabled (SDRS) cluster

vpxd.log

<YYYY-MM-DDTHH:MM:SS> info vpxd[61318] [Originator@6876 sub=drmLogger opID=lro-4-409434ca-0a] Ignoring host [vim.HostSystem:host-<Host ID>,<Host FQDN>]: host Config information is nullptr
<YYYY-MM-DDTHH:MM:SS> info vpxd[61318] [Originator@6876 sub=drmLogger opID=lro-4-409434ca-0a] Ignoring host [vim.HostSystem:host-<Host ID>,<Host FQDN>]: host Config information is nullptr
<YYYY-MM-DDTHH:MM:SS> info vpxd[61318] [Originator@6876 sub=drmLogger opID=lro-4-409434ca-0a] Ignoring host [vim.HostSystem:host-<Host ID>,<Host FQDN>]: host Config information is nullptr
<YYYY-MM-DDTHH:MM:SS> info vpxd[61318] [Originator@6876 sub=drmLogger opID=lro-4-409434ca-0a] Ignoring host [vim.HostSystem:host-<Host ID>,<Host FQDN>]: host Config information is nullptr

Cause

The issue is seen if there is a stale entry for ESXi hosts de-commissioned from the inventory and listed as 'Not Responding'

Resolution

The entries should be isolated from the vpxd logs and removed manually. VMware engineering is already aware and the fix would be included with a future release of vSphere.

Workaround

Caution: This procedure modifies the database. Ensure to take a full backup of your existing vCenter Server  before proceeding with this workaround.

Log in to the vCenter server appliance via ssh

Navigate to the vpxd log location (/var/log/vmware/vpxd)

Execute the below command:

Command: grep -irns "No heartbeats received from host" vpxd.log | awk -F ' ' '{print $16}' | sort -u

Check for the status of the hosts and remove the host(s) in case of decommissioned servers. For further information, refer to Manually removing an ESX\ESXi host from the vCenter Server database

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
ESXi Hyperbus 停滞在 MISS_VERSION_HANDSHAKE 状态 (76131)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
仮想マシン ハードウェアの変更後または vMotion の後、DFW ルールが想定どおりに機能しない (76111)

KB
•
在同一 Edge 上的两个第 1 层之间无法建立 IKEv1 会话 (76177)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

Take Our Survey

Support Assistant