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:
1The 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:
1CRITICAL:backend_init:OneConnect Adapter Not Found. 2ERROR:rename all the configuration files! 3ERROR:MILI_enumerate_elxiscsi:Failed to initialize User Init with status = 19 4ERROR:MILI_enumerate_elx_nics:Failed to initialize USer Init with status = 19 5ERROR: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.
1esxcli software vib remove --vibname elxnet 2esxcli software vib remove --vibname elxiscsi 3esxcli software vib remove --vibname elx-esx-libelxima.so