The full /var partition on the ESXI host can trigger host problems. If you keep the /var partition free of space the hosts will be running well in your cluster.
Fixing of the root cause of the runaway log file
When the issue was presented, I wasn't able to connect with any terminal app to hosts so, I had to use the host console. And after a while found that the /var/log/EMU/mili/mili2d.log was continually growing.
In the vsphere syslog found this error:
The ramdisk 'var' is full. As a result, the file `/var/log/EMU/mili/mili2d.log` could not be written.
Then I looked /var/log/EMU/mili/mili2d.log and revealed following errors:
CRITICAL:backend_init:OneConnect Adapter Not Found.
ERROR:rename all the configuration files!
ERROR:MILI_enumerate_elxiscsi:Failed to initialize User Init with status = 19
ERROR:MILI_enumerate_elx_nics:Failed to initialize USer Init with status = 19
ERROR:could not open device node /vmfs/devices/char/vmkdriver/be_esx_nic
What it means ?
Since both servers do not have any Emulex hardware installed, the elxnet drivers are not needed. So I removed them and rebooted hosts. That is it, It solved my problem on the hosts.
esxcli software vib remove --vibname elxnet
esxcli software vib remove --vibname elxiscsi
esxcli software vib remove --vibname elx-esx-libelxima.so
Top comments (0)