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 6.5/6.7 hangs during certain tasks like maintenance mode, connecting to vCenter, or after a reboot. (74966)

Last Updated: 2/23/2024Categories: TroubleshootingTotal Views: 38073Language:
Chinese (Simplified)JapaneseEnglish

24 like this article

Subscribe to get an email
newsletter with new updates

24 people found this helpful Please provide article feedback:

Symptoms

Certain tasks which involve the hostd service cause the ESXi host to hang for up to 20 minutes.

Entering/Exiting Maintenance mode

Connecting to vCenter

Rebooting ESXi after installing NSX vibs

esxcli commands hang, but localcli commands do not.

A host with the problem may take 5 to 10 minutes to connect to vCenter from the time the ESXi DCUI login screen fully loads.

ESXi host randomly disconnects from vCenter server.

HA/DRS task getting stuck and vMotion may time out.

ESXi hosts might experience a Memory admission control issue for sfcb-hhrc.

ESXi hosts become unresponsive.

ESXi console is not responding.

Messages similar to these are seen in /var/log/syslog.log

2019-07-24T18:43:48Z sfcb-hhrc[69008]: TIMEOUT DOING SHARED SOCKET RECV RESULT (69008)
2019-07-24T18:43:48Z sfcb-hhrc[69008]: Timeout (or other socket error) waiting for response from provider
2019-07-24T18:43:48Z sfcb-hhrc[69008]: Header Id (93) Request to provider 127 in process 5 failed. Error:Timeout (or other socket error) waiting for response from provider
2019-07-24T18:43:48Z sfcb-hhrc[69008]: Dropped response operation details -- nameSpace: root/cimv2, className: OMC_UnitaryComputerSystem, Type: 0
2019-07-24T18:43:48Z sfcb-hhrc[69008]: InitSystemInfo: no instance found. rc -2
2019-07-24T18:43:48Z sfcb-hhrc[69008]: Cannot get system info, rc -100

Messages similar to these are seen in /var/log/hostd.log

2019-07-24T18:50:53.182Z warning hostd[11607B70] [Originator@6876 sub=PropertyProvider opID=930b9d3a] It took 903762150 microseconds to get property summary for vim.HostSystem:ha-host

Messages similar to these are seen in /var/log/vmkernel.log

2020-09-20T14:44:20.202Z cpu47:1179240)MemSched: 14642: uw.1179234 (3525969) extraMin/extraFromParent: 47/47, hhrc (10681) childEmin/eMinLimit: 17906/17920
2020-09-20T14:44:20.202Z cpu47:1179240)MemSched: 14635: Admission failure in path: hhrc/sfcb-ProviderMa.1179234/uw.1179234
2020-09-20T14:44:20.202Z cpu47:1179240)MemSched: 14642: uw.1179234 (3525969) extraMin/extraFromParent: 256/256, hhrc (10681) childEmin/eMinLimit: 17906/17920
2020-09-20T14:44:20.202Z cpu47:1179240)MemSched: 14635: Admission failure in path: hhrc/sfcb-ProviderMa.1179234/uw.1179234

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

Cause

This issue happens when CIMSVC is enabled and it tries to periodically refresh sensor data. This effectively causes other hostd threads to wait for the refresh data to complete, resulting in the hang.

Impact / Risks

Turning cimsvc off will stop cimsvc plugin from polling ipmi and reporting hardware health information.

Resolution

This issue has been fixed in VMware ESXi 6.5 Patch release ESXi650-201910001  and  VMware ESXi 6.7, Patch Release ESXi670-201912001.

Workaround

To workaround this issue, disable vmw_hhrcwrapper. This CIM provider (HHRC) is a storage CIM provider

Workaround 1

localcli system wbem provider set -e 0 -n vmw_hhrcwrapper

/etc/init.d/sfcbd-watchdog restart

/etc/init.d/hostd restart

Workaround 2

/etc/init.d/hostd stop

edit the /etc/vmware/hostd/config.xml file

<cimsvc>
<path>libcimsvc.so</path>
<enabled>true</enabled>
</cimsvc>

to
<cimsvc>
<path>libcimsvc.so</path>
<enabled>false</enabled>
</cimsvc>

/etc/init.d/hostd start

Related Information

On ESXi hosts having Host Hardware Raid Controller (HHRC), running VMware ESXi 6.5 U2 the sfcb-hhrc process fails. When this occurs, the SFCB HHRC Provider causes the ESXi host to become unresponsive. This issue is cause by the SFCB HHRC Providers running out of available memory due to memory leaks

The sfcb-hhrc process manages third-party Host Hardware RAID Controller (HHRC) CIM providers and provides hardware health monitoring

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
•
vSAN 健全性サービス - オンライン健全性 – 使用中の vSAN v1 ディスク (75045)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

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

Take Our Survey

Support Assistant