Suddenly somehow we got a virtual machine which couldn’t be powered on, or ESXi 5.x host becomes unresponsive after attempting to migrate a virtual machine from VMware vCenter Server or configuration change fails.
- VMware ESXi 5.x host becomes unresponsive after attempting to migrate a virtual machine from VMware vCenter Server;
- Making a configuration change to the ESXi host renders the host unresponsive;
- Migration fails at 13%;
- Some of the virtual machines in the inventory become invalid;
- vpxa fails to start;
- You are unable to power on a virtual machine.
- Connect to the ESXi host using SSH.
- Check if SNMP is creating too many .trp files in the /var/spool/snmp directory on the ESXi host by running the command:
ls /var/spool/snmp | wc -l
Note: If the output indicates that the value is 2000 or more, this may be causing the full inodes.
To be sure check che disk root usage running this command
If the available space is less than 3-4Mb (or usage ‘USE’ over 90%), it could be a problem.
- Delete the .trp files in the /var/spool/snmp/ directory by running the commands:
# cd /var/spool/snmp
# for i in $(ls | grep trp); do rm -f $i;done