Our first VMware Scare
Today, all of a sudden one of my VMware ESX Server hosts went awol. It didn't completely disappear, as the VMs running on it were all operational and the host itself was responsive to SSH connections. The problem was that the my VI3 client listed the host as unresponsive and direct connections to the host from the VI3 client was unsuccessful as well. As I was able to SSH to the host in question, and given the fact that all the VMs were operational, I quickly ruled out network connectivity issues between the VI and the host. Inspection of the logs gave me no real clues either, but I had a sneaking suspicion that the problem was related to problems with the management agents on the host. A quick "service mgmt-vmware restart" later the host was back in business as usual and all things were good in VMware land yet again.3 Responses to Our first VMware Scare:
1 Pingbacks to Our first VMware Scare:
-
May 23, 2007 1:22pm[…] Original post by h0bbel […]
May 23, 2007 1:22pm
[…] Original post by h0bbel […]
May 25, 2007 3:24am
Congrats on weathering your first…hopefully this is just the first of very very few! We’vd had some issues over here, but mostly it’s because of growing pains, too many VMs, not enough space, and quick deployments of “bigger iron” storage/blades/networking, without a lot of training in how to use them effectively. I still swear by VMWare, though!
service mgmt-vmware restart is a good one to keep in the cookbook!
May 31, 2007 9:01am
VMware VI3 is doing a great job here, this is really the first issue we have seen that hasn’t been related to operator error or similar and restarting the service daemons worked perfectly.