To resolve this issue, you must restart vmkernel logging.
To restart vmkernel logging:
- Run this command to verify if there is sufficient free space available for logging:
#df -h
- Run this command to verify if the syslog service is running:
#service syslog status
- Run this command to restart the syslog service:
#service syslog restart
- Run this command to verify if the vmklogger and vmklogger watchdog processes are running:
#ps -aux | grep vmklogger
If these services are running, you must see an output similar to:
/bin/sh /usr/bin/vmware-watchdog -s vmklogger /usr/sbin/vmklogger
/usr/sbin/vmklogger
- If the vmklogger watchdog process is not running, run this command to start it:
#/usr/bin/vmware-watchdog -s vmklogger /usr/sbin/vmklogger &
- If the vmklogger watchdog process is running, run this command to restart the vmklogger process:
#killall -HUP vmklogger
- Check if the /var partition is full, it will show 100% used. You can find out the top 30 consumers of the space on this /var partition by giving the command
du -a /var | sort -n -r | head -n 30
If you find the files such as "nnn.core" in the /var/core/ partition, that can be deleted to release sufficient space to make the ESX host responsive again
- After the space has been released, restart the management service.
service mgmt-vmware restart