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

Hardware health status monitoring is unstable and not displayed (53460)

Last Updated: 11/28/2018Categories: InformationalTotal Views: 11456Language:
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:

Symptoms

Hardware health status monitoring is unstable and not displayed.

Resetting the sensors and event log does not resolve the issue.

In the syslog.log, you see the entries similar to:

2017-12-03T20:30:37Z sfcb-vmware_base[1038465]: TIMEOUT DOING SHARED SOCKET RECV RESULT (1038465)
2017-12-03T20:30:37Z sfcb-vmware_base[1038465]: Timeout (or other socket error) waiting for response from provider
2017-12-03T20:30:37Z sfcb-vmware_base[1038465]: Header Id (380439) Request to provider 141 in process 5 failed. Error:Timeout (or other socket error) waiting for response from provider
2017-12-03T20:30:37Z sfcb-vmware_base[1038465]: Dropped response operation details -- nameSpace: root/cimv2, className: OMC_RawIpmiSensor, Type: 0

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

Cause

This issue occurs because the sfcb-vmware_base is waiting for response from other provider and crashing due to timeout.

Resolution

This is a known issue affecting VMware ESXi 6.0.

Currently, there is no resolution.

Workaround

To work around this issue, increase the memory pool size for the process running out of memory.

Stop the sfcbd service by running this command:

/etc/init.d/sfcbd-watchdog stop

Update the memory allocation by running this command:

vsish -e set /sched/groups/<groupid>/memAllocationInMB minLimit=0 shares=1000 max=200

Note: Provide the groupid of sfcb_aux and sfcb in the command.

Start the sfcbd service by running this command:

/etc/init.d/sfcbd-watchdog start

Note: This change is not persistent and the configuration will be back to default after host reboot.

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.0

Take Our Survey

Support Assistant