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

ESXi host is disconnected from vCenterServer and it is in an unresponsive state (66932)

Last Updated: 2/6/2019Categories: TroubleshootingTotal Views: 19704Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

ESXi host is disconnected from vCenterSever and it gets no response.

- SSH and DCUI can connect to ESXi host
- PING response has no problem
- ESXi host reconnection fails
- No direct connection from vSphereClient to ESXi host
- Restarting the service of vpxa / hostd / rhttpproxy will not be resolved
- Restarting service.sh is not resolved
- Restarting the ESXi host will not resolve it

A situation where the Hostd service repeatedly crashes from the log of the ESXi host.

In the situation before the crash occurred, "The file specified is not a virtual disk" is logged in the hostd log.

In the virtual machine's .vmx file, "scsix: x.fileName" is set to NULL.

The vmdk file exists in the directory of the virtual machine.

Virtual machine configuration information (. vmx):

scsix:x.deviceType = "scsi-hardDisk"
scsix:x.fileName = ""

hostd log：

2018-12-20T03:51:02.732Z info hostd[79E44B70] [Originator@6876 sub=DiskLib opID=62557529-1-ec11 user=vpxuser:XXXXX-VSPHERE.LOCAL\XXXXXXXXXXXXXX] DISKLIB-LIB : Failed to open '/vmfs/volumes/578de40f-0d70dfc2-e746-0025b591010f/XXXXXXX' with flags 0x110015 The file specified is not a virtual disk (15).
2018-12-20T03:51:02.732Z info hostd[79E44B70] [Originator@6876 sub=DiskLib opID=62557529-1-ec11 user=vpxuser:XXXXX-VSPHERE.LOCAL\XXXXXXXXXXXXXX] DISKLIB-LIB_MISC : DiskLibEnumExtents: failed to open '/vmfs/volumes/578de40f-0d70dfc2-e746-0025b591010f/XXXXXXX': The file specified is not a virtual disk (15).
2018-12-20T03:51:02.732Z error hostd[79E44B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/578de40f-0d70dfc2-e746-0025b591010f/XXXXX/XXXXX.vmx opID=62557529-1-ec11 user=vpxuser:XXXXX-VSPHERE.LOCAL\XXXXXXXXXXXXXX] Failed to enumerate disk [XXXXXXX] XXXXXXX, The file specified is not a virtual disk
2018-12-20T03:51:02.739Z warning hostd[79E44B70] [Originator@6876 sub=Default opID=62557529-1-ec11 user=vpxuser:XXXXX-VSPHERE.LOCAL\XXXXXXXXXXXXXX] FileLayoutExToFileLayout: While populating disk layoutSkipping empty diskLayout configuration for VM [XXXXXXX] XXXXXXX/XXXXXXX.vmx, key 2000
2018-12-20T03:51:02.740Z info hostd[796CDB70] [Originator@6876 sub=Snmpsvc] VmConfigListener: vm state change received, queueing reload request

2018-12-20T03:51:02.741Z info hostd[79E44B70] [Originator@6876 sub=Libs opID=62557529-1-ec11 user=vpxuser:XXXXX-VSPHERE.LOCAL\XXXXXXXXXXXXXX] Error getting extended config name from config file.
2018-12-20T03:51:02.741Z info hostd[79E44B70] [Originator@6876 sub=Libs opID=62557529-1-ec11 user=vpxuser:XXXXX-VSPHERE.LOCAL\XXXXXXXXXXXXXX] Error getting extended config file path.
2018-12-20T03:57:06.018Z Section for VMware ESX, pid=19965294, version=6.0.0, build=6921384, option=Release
2018-12-20T03:57:06.018Z verbose hostd[FFF24B20] [Originator@6876 sub=Default] Dumping early logs:

vpxa log：

2018-12-20T03:57:05.217Z error vpxa[7DDBBB70] [Originator@6876 sub=vpxaInvtHostCnx opID=WFU-1f0c1d49] [VpxaInvtHost] Can't connect to hostd/serverd. Shutting down...
2018-12-20T03:57:05.217Z error vpxa[7DF1EB70] [Originator@6876 sub=hostdstats] [PollCurrentStats] Failed to fetch current stats.  Fault:
2018-12-20T03:57:05.217Z info vpxa[7DDBBB70] [Originator@6876 sub=Default opID=WFU-1f0c1d49] [Vpxa] Shutting down now

vmkernel log：

2018-12-20T03:51:02.746Z cpu42:35335 opID=8d848a42)User: 3820: hostd-worker: wantCoreDump:hostd-worker signal:6 exitCode:0 coredump:enabled
2018-12-20T03:51:02.883Z cpu42:35335 opID=8d848a42)UserDump: 2074: hostd-worker: Dumping cartel 34536 (from world 35335) to file /var/core/hostd-worker-zdump.000 ...
2018-12-20T03:57:05.201Z cpu12:35335 opID=8d848a42)UserDump: 2194: hostd-worker: Userworld coredump complete.

vobd log：

2018-12-20T03:57:05.201Z: [UserWorldCorrelator] 28682044986303us: [vob.uw.core.dumped] /bin/hostd(34536) /var/core/hostd-worker-zdump.000
2018-12-20T03:57:05.201Z: [UserWorldCorrelator] 28682457971729us: [esx.problem.hostd.core.dumped] /bin/hostd crashed (1 time(s) so far) and a core file may have been created at /var/core/hostd-worker-zdump.000. This may have caused connections to the host to be dropped.
2018-12-20T03:57:05.202Z: An event (esx.problem.hostd.core.dumped) could not be sent immediately to hostd; queueing for retry.

Cause

This is a known issue that occurs because the vmdk file name is not set to "scsix: x.fileName" of the virtual machine's .vmx file.

Resolution

Issue has been resolved in ESXi 6.0 Patch 07.

VMware ESXi 6.0, Patch Release ESXi600-201807401-BG - Updates esx-base, vsan and vsanhealth VIBs (53629)
VMware ESXi 6.0, Patch Release ESXi600-201807401-BG

Workaround

It is possible to avoid it by setting the vmdk file name to "scsix: x.fileName" of the virtual machine's .vmx file

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)

KB
•
Download and Install VMware Fusion (2014097)

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 vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.0

Take Our Survey

Support Assistant