Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Host not respondingConnecting 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 = 19Wed Nov 28 23:24:32 2018,5537277, ERROR:MILI_enumerate_elx_nics:Failed to initialize USer Init with status = 19Wed Nov 28 23:24:32 2018,5537277, ERROR:could not open device node /vmfs/devices/char/vmkdriver/be_esx_nicWed 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 = 19Wed Nov 28 23:26:31 2018,5537324, ERROR:MILI_enumerate_elx_nics:Failed to initialize USer Init with status = 19Wed Nov 28 23:26:31 2018,5537324, ERROR:could not open device node /vmfs/devices/char/vmkdriver/be_esx_nicWed 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).
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.
This issue is resolved in VMware ESXi 6.7 P01Download link: https://customerconnect.vmware.com/group/vmware/patchsearch for the patch: ESXi670-201912001
To workaround this issue： Remove the mili2d.log from /tmp folder with the command: rm /var/log/EMU/mili/mili2d.logRestart management agents on the affected host by running the command: services.sh restartEdit 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 elxnetesxcli software vib remove --vibname elxiscsiesxcli software vib remove --vibname elx-esx-libelxima.so
VMware Skyline Health Diagnostics for vSphere - FAQ