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 hosts disconnect from Active Directory domain randomly (78968)

Last Updated: 2/22/2024Categories: TroubleshootingTotal Views: 35108Language:
Chinese (Simplified)JapaneseEnglish

17 like this article

Subscribe to get an email
newsletter with new updates

17 people found this helpful Please provide article feedback:

Symptoms

ESXi hosts randomly disconnect from the Active Directory domain or sometime disconnects from the vCenter Server.

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

2019-11-12T22:52:10.902Z cpu5:2924874)MemSched: 14642: uw.2924860 (14074759) extraMin/extraFromParent: 256/256, likewise (790) childEmin/eMinLimit: 99871/100096
2019-11-12T22:52:10.902Z cpu5:2924874)MemSched: 14635: Admission failure in path: likewise/lwsmd.2924860/uw.2924860
2019-11-12T22:52:10.903Z cpu5:2924874)MemSched: 14642: uw.2924860 (14074759) extraMin/extraFromParent: 256/256, likewise (790) childEmin/eMinLimit: 99871/100096
2019-11-12T22:52:10.903Z cpu5:2924874)MemSched: 14635: Admission failure in path: likewise/lwsmd.2924860/uw.2924860

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

Cause

The issue occurs due to exhaustion of Likewise memory because of existing memory leaks in Active Directory operations and related libraries.

When smart card authentication is enabled and configured on the ESXi hosts, Likewise memory leaks are also observed.

Resolution

This issue is partially resolved in VMware vSphere ESXi 6.5 Patch ESXi650-202007001 and  vSphere ESXi 6.7 Patch ESXi670-202008001  and vSphere  ESXi 7.0 U1. To download the patch, go to  Customer Connect Patch Downloads page.

To download vSphere ESXi 7.0 U1 go to Customer Connect Downloads

Workaround

To work around this issue non-persistently:

1. Download the lwis-mem-check-2.zip file attached to this Knowledge Base article.
2. Unzip lwis-mem-check-2.zip and copy the lwis-mem-check-2.sh script in /tmp directory.
3. Verify if the script is executable. If the script is not executable, run  the command:

chmod +x /tmp/lwis-mem-check-2.sh

4. Run the script using the command:

setsid /tmp/lwis-mem-check-2.sh >/dev/null 2>&1 < /dev/null &

The script monitors the likewise memory usage generating lwis-oom-stats file in /tmp directory with Likewise memory stats when Likewise runs out of memory and remediates the issue.

Note: The above workaround is only temporary and will not persist if the ESXi host is rebooted.

To work around this issue persistently:

Important: Please ensure you have a ESXi host configuration backup

You can always contact VMware support to assist with the below steps, if you are not familiar in making the below changes.

Note: You will need a shared datastore path where you can place the lwis-mem-check.sh script that can be retrieved during startup.

1. SSH to the ESXi host
2. Backup the file:

cp /etc/rc.local.d/local.sh /root/local.sh

3. Edit the file:

vi /etc/rc.local.d/local.sh

4. Add the following lines before “exit 0”:

cp /vmfs/volumes/<Datastore>/<script>/lwis-mem-check-2.sh /tmp/
chmod +x /tmp/lwis-mem-check-2.sh
setsid /tmp/lwis-mem-check-2.sh >/dev/null 2>&1 < /dev/null &

Note: <Datastore>/<script> should be replaced with the correct datastore directory path where the script is located.

5. Save the changes
6. To ensure the local.sh file will save during a reboot operation run:

auto-backup.sh

Note: This is only a temporary workaround and not a permanent fix. The above steps should be reverted once the issue has been identified and resolved fully.

If smart card authentication is enabled, disabling this will help stop any Likewise memory leaks created by the smart card authentication.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

lwis-mem-check-2.sh

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

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant