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

ESXi host is non-responsive and disconnected in vCenter (56450)

Last Updated: 1/22/2021Categories: TroubleshootingTotal Views: 21275Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

Hostd is non-responsive and is disconnected in vCenter

Host status in vCenter Server is not responding

In the vmkernel.log file, you see entries similar to:

2017-07-23T19:10:39.467Z info hostd[DF80B70] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 727 :  Lost access to volume 595a73d1-1e8d8173-6a8f-a0369f2eef38 (DX100#02_SSD-01) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.
2017-07-23T19:10:39.468Z info hostd[D3C2B70] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 728 : Lost access to volume 595ab527-f3df823e-f747-a0369f2eef38 (DX100#02_SAS-02) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.

In the Hostd.log file, you see entries similar to:

hostd.0
==================
2017-08-02T18:55:49.026Z info hostd[BA81B70] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 526 : Lost access to volume 597991cd-2ae53f79-db0f-b49691017b10 (DX100#02_SAS-02) due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly.
2017-08-02T18:55:49.026Z info hostd[BA81B70] [Originator@6876 sub=Hostsvc.VmkVprobSource] VmkVprobSource::Post event: (vim.event.EventEx) {
--> key = 0,
--> chainId = 0,
--> createdTime = "1970-01-01T00:00:00Z",
--> userName = "",
--> datacenter = (vim.event.DatacenterEventArgument) null,
--> computeResource = (vim.event.ComputeResourceEventArgument) null,
--> host = (vim.event.HostEventArgument) {
--> name = "bhsesx01",
--> host = 'vim.HostSystem:ha-host'

In the vobd.log file, you see entries similar to:

==================
2017-07-30T02:24:58.236Z: [scsiCorrelator] 420484207165us: [esx.problem.storage.redundancy.lost] Lost path redundancy to storage device naa.600000e00d29000000291e5b00000000. Path vmhba1:C0:T0:L0 is down. Affected datastores: "DX100#01_SSD-01".

There are other issues which can cause a hostd to go unresponsive

The scope of this document is only to troubleshoot hostd unresponsivesness.

Purpose

To troubleshoot the hostd service.

Cause

This situation is usually due to certain services on the host that are not running properly. While there can be other reasons ,unresponsive host services are frequently caused by the host running out of available resources . An ESXi host will shut down resource-intensive services like ‘hostd’ rather than take from what is allocated to running VMs, if they need it.

The vCenter cannot communicate with the host both due to lack of these services as well as general difficulty with a lagging host that doesn’t have enough available resources to function properly. The result is a host that fails to respond to vCenter and is normally slow and difficult to access or manage in other ways. In these cases, the host’s storage is still fully functional within the datastore and its VMs will usually continue running almost normally for a period of time.

Resolution

The scope of this document is only to troubleshoot hostd unresponsivesness.

Workaround

Detect the non-responsive hostd:

Check hostd detected to be non-responsive alert message in the vmkernel* log.

Check host-probe* logs and locate timeout messages or hostd log not getting updated.

NOTE: Restarting the management agents may impact any tasks that are running on the ESXi host at the time of the restart
Check for any storage issues before restarting the Host deamon hostd service or services.sh

Refer to Restarting the Management agents in ESXi (1003490)
2.    Stop hostd using service or hostd command. For more information, see:

hostd is not responding and cannot be killed by the kill -9 command (1007261)

Service mgmt-vmware restart may not restart hostd in ESX/ESXi (1005566)

3. Alternatively VM shutdown method if you have command line available through Putty or DCUI shell to the host and can’t access the VMs directly for some reason. See Unable to Power off a Virtual Machine in an ESXi host

Command to see if a VM is running on a ESXi host and get the World ID: # localcli vm process list

Command to shut a VM down: # localcli vm process kill -t soft -w <worldID>

*Using 'soft', as above, is the most graceful shutdown. If that doesn't work, use 'hard' instead to perform an immediate shutdown. The option 'force' should be used as a last resort.

NOTE: It is important that any underlying storage issue is if fixed for hostd service to respond properly.

Related Information

For more information, see:

VMware Skyline Health Diagnostics for vSphere - FAQ

Troubleshooting an ESXi host in non responding state (1003409)

Understanding the difference between Not Responding and Disconnected ESXi hosts in VMware vCenter Server (2121031)

ESXi hosts do not respond and is grayed out (1019082)

For more information on avoiding common storage related issues, see

Permanent Device Loss (PDL) and All-Paths-Down (APD) in vSphere 5.x and 6.x (2004684)

How to unmount a LUN or detach a datastore device from ESXi hosts (2004605)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

Take Our Survey

Support Assistant