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 goes not responding in vCenter and hostd crashes with error "Panic: Memory exceeds hard limit" (76043)

Last Updated: 2/22/2024Categories: TroubleshootingTotal Views: 12625Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

ESXi hosts goes not responding in vCenter and recovers automatically few minutes later.

In var/log/hostd.log you see the hostd process crashing with panic:

2019-10-29T03:35:29.797Z error hostd[309C2B70] [Originator@6876 sub=UW Memory checker] Current value 1288636 exceeds hard limit 1286881. Shutting down process.
2019-10-29T03:35:29.797Z panic hostd[309C2B70] [Originator@6876 sub=Default]
-->
--> Panic: Memory exceeds hard limit. Panic
--> Backtrace:
--> [backtrace begin] product: VMware ESX, version: 6.5.0, build: build-6765664, tag: hostd, cpu: x86, os: esx, buildType: release
--->

In  var/log/hostd.log you see the below messages referring to a corrupt VMware Tools windows.iso image

Line 16733: 2019-10-29T04:02:20.035Z info hostd[2C297B70] [Originator@6876 sub=Libs] ToolsISO: Selected Tools ISO 'windows.iso' for 'windows7srv-64' guest.
Line 16744: 2019-10-29T04:02:20.059Z info hostd[2C297B70] [Originator@6876 sub=Libs] ToolsISO: Error hash mismatch at offset 0x8000, expected hash [PbIrjdgFyu824nbRIbnFi8+DNkHIO06vZK/AIFcymIo=], but found [kBzqaLCzmb61r+AtU/ft/+kgRiR8V9OgDtOq6QQlQrI=]
Line 16745: 2019-10-29T04:02:20.059Z info hostd[2C297B70] [Originator@6876 sub=Libs] ToolsISO: Invalid data at offset 8000 (bytes 2048)
Line 16746: 2019-10-29T04:02:20.059Z info hostd[2C297B70] [Originator@6876 sub=Libs] Failed to open Tools ISO image.

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

Purpose

To resolve the hostd issue.

Cause

The hash check fails for VMware Tools ISO  and the hostd process fails to open/extract the ISO file. Due to this failure, the allocated hash info is not being cleaned up efficiently, leading to memory leak and the eventual hostd crash.

Impact / Risks

Requires host to be in maintenance mode.

Resolution

VMware vSphere ESXi 6.5 P05, and VMware vSphere ESXi 6.7 P02 has the fix for the issue.

Workaround

To workaround this issue follow the below steps.

Copy the /productLocker/vmtools/ folder and its contents from a working host running the same ESXi version/build and replace them on the affected host.

1. Enter the ESXi host in Maintenance Mode
2. Enable SSH on both the "good" (for e.g. esxi01 ) and the "affected" (esxi02) host.
3. Login as "root" user
4. scp the /productLocker/vmtools/  folder and contents from the "good" host to the "problem" host

$ [esxi01:~]$ scp -rf /productLocker/vmtools/ esxi02:/productLocker/

Note: This will overwrite the vmtools folder on the problem host, hence you could backup this folder locally if you want but it is not mandatory for the purpose of this activity.

5. Verify the MD5SUM of the vmtools folder contents on the good and bad host. These should match after copying.

For e.g.  md5sum /productLocker/vmtools/windows.iso
1f13ee2eb9dfb4eab070c241a1d71cf4  /productLocker/vmtools/windows.iso

Note: Run the md5sum command on all the files under the vmtools folder on both hosts

5. Restart Management Agents
services.sh restart

6. Exit Maintenance Mode

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 6.7 Update 3 へのアップグレード後、ESXi ホストが UEFI モードでの起動に失敗することがある (76159)

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

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant