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

Full ramdisk '/var' causes /var/log/EMU/mili/mili2d.log to stop logging (65193)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 28286Language:
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:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

Host not responding

Connecting to the host ESXi you see /var or /tmp folder at 100%

The /var/log/EMU/mili/mili2d.log contains these messages:

Wed Nov 28 23:24:32 2018,5537277, ERROR:MILI_enumerate_elxiscsi:Failed to initialize User Init with status = 19
Wed Nov 28 23:24:32 2018,5537277, ERROR:MILI_enumerate_elx_nics:Failed to initialize USer Init with status = 19
Wed Nov 28 23:24:32 2018,5537277, ERROR:could not open device node /vmfs/devices/char/vmkdriver/be_esx_nic
Wed Nov 28 23:24:32 2018,5537277, CRITICAL:backend_init:OneConnect Adapter Not Found.
Wed Nov 28 23:26:31 2018,5537324, ERROR:rename all the configuration files!
Wed Nov 28 23:26:31 2018,5537324, ERROR:MILI_enumerate_elxiscsi:Failed to initialize User Init with status = 19
Wed Nov 28 23:26:31 2018,5537324, ERROR:MILI_enumerate_elx_nics:Failed to initialize USer Init with status = 19
Wed Nov 28 23:26:31 2018,5537324, ERROR:could not open device node /vmfs/devices/char/vmkdriver/be_esx_nic
Wed Nov 28 23:26:31 2018,5537324, CRITICAL:backend_init:OneConnect Adapter Not Found.
Wed Nov 28 23:28:27 2018,5537371, ERROR:rename all the configuration files!
Wed Nov 28 23:28:27 2018,5537371, ERROR:MILI_enumerate_elxiscsi:Failed to initialize User Init with status = 19

In the vmkernel.log, you see:

cpu16:75446085)WARNING: VisorFSRam: 233: Cannot extend visorfs file /tmp/bbFile2.txt because its ramdisk (tmp) is full.
cpu14:75334706)WARNING: VisorFSRam: 233: Cannot extend visorfs file /tmp/hp-bbUsg.txt because its ramdisk (tmp) is full.
cpu14:75334706)WARNING: VisorFSRam: 233: Cannot extend visorfs file /tmp/hp-mem.txt because its ramdisk (tmp) is full.

Connected virtual machine console you see error:

A server error occurred.You have reached the maximum number of connected consoles: 40. Please contact your administrator.
Check the vSphere Web Client server logs for details.

Migrating virtual machine using vMotion fails.

You see this error similar to:

General System Error Occurred.

Note: For issues where the same error occurs, but the AMS data is filling up /tmp, see HPE servers running VMware ESXi version 6.X with Agentless Management Service (AMS) version 11.4.x will become not responding. (78595).

Cause

When /scratch/log/ is unavailable Emulex drivers logs will begin to fill up the /var file system logs.

Emulex drivers might write logs to /var/log/EMU/mili/mili2d.log and fill up the 40 MB /var file system logs of RAM drives. A previous fix changed writes of Emulex drivers to the /scratch/log/ folder instead of to the /var/log/ folder to prevent the issue. When the /scratch/log/ folder is temporarily unavailable, the /var/log/EMU/mili/mili2d.log is still periodically used for logging.

Resolution

This issue is resolved in VMware ESXi 6.7 P01

Download link: https://customerconnect.vmware.com/group/vmware/patch

search for the patch: ESXi670-201912001

Workaround

To workaround this issue：

Remove the mili2d.log from /tmp folder with the command: rm /var/log/EMU/mili/mili2d.log

Restart management agents on the affected host by running the command: services.sh restart

Edit the configuration file: /etc/config/EMU/mili/libmili.conf and set 'MILILogLevel 0' to stop mili log ouput.

Remove the following vibs if not used and reboot host

esxcli software vib remove --vibname elxnet
esxcli software vib remove --vibname elxiscsi
esxcli software vib remove --vibname elx-esx-libelxima.so

Related Information

VMware Skyline Health Diagnostics for vSphere - FAQ

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 7.0.0

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant