CipherUser
asked on
VMware - Cannot reconnect ESXi Host in Vcenter
This morning I came in to find that one of my ESXi hosts is disconnected in vCenter. Attempting to reconnect gives the following error:
Cannot contact the specified host. The host may not be available on the network, a network configuration problem may exist or the management services on this host may not be responding.
Following the VMware KB procedures in " Restarting the Management agents on an ESXi or ESX host (1003490)" i tried restarting the management agents via the DCUI. I pressed F2 and received a login prompt. I enter the root credentials and pressed Enter. The screen went back to the default splash screen and now hitting F2 does nothing (nor does hitting F12).
Continuing to follow the same KB article, I tried restart the management agents via SSH and received errors about "no space left on device" (See attached Image). There is 1.5TB free on the VMFS-5 volume.
Can anyone suggest how to proceed with regaining connectivity of the host to vCenter or the viClient?
ESXi-Host-Failure.jpg
Cannot contact the specified host. The host may not be available on the network, a network configuration problem may exist or the management services on this host may not be responding.
Following the VMware KB procedures in " Restarting the Management agents on an ESXi or ESX host (1003490)" i tried restarting the management agents via the DCUI. I pressed F2 and received a login prompt. I enter the root credentials and pressed Enter. The screen went back to the default splash screen and now hitting F2 does nothing (nor does hitting F12).
Continuing to follow the same KB article, I tried restart the management agents via SSH and received errors about "no space left on device" (See attached Image). There is 1.5TB free on the VMFS-5 volume.
Can anyone suggest how to proceed with regaining connectivity of the host to vCenter or the viClient?
ESXi-Host-Failure.jpg
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
/var/logs
and you can remove all the tar balls or copy them off via SCP.
you may need to reboot, if the services have hung1
and you can remove all the tar balls or copy them off via SCP.
you may need to reboot, if the services have hung1
ASKER
Andrew,
There doesn't seem to be any space to recover in the /var/log directory (See 1st image).
Also, I found out that I'm out of inodes using VMware KB article: ESXi/ESX error: No free space left on device (1007638). I ran the command they suggested to find large files to delete, but none of them look like good candidates (See 2nd Image).
You are dead on that I need to delete files, but deleting anything in the /var/log directory doesn't look like it will free up more than a few KBs.
Do you have any other suggestions on how to free up some space after seeing the images I posted?
Thanks in advance for your help!!
var-log-Directory.jpg
28634766OutOfinodes.jpg
There doesn't seem to be any space to recover in the /var/log directory (See 1st image).
Also, I found out that I'm out of inodes using VMware KB article: ESXi/ESX error: No free space left on device (1007638). I ran the command they suggested to find large files to delete, but none of them look like good candidates (See 2nd Image).
You are dead on that I need to delete files, but deleting anything in the /var/log directory doesn't look like it will free up more than a few KBs.
Do you have any other suggestions on how to free up some space after seeing the images I posted?
Thanks in advance for your help!!
var-log-Directory.jpg
28634766OutOfinodes.jpg
do you have any third party VIBS or management installed ?
ASKER
No third party VIBs or managament installed. I do use Veeam Backup and Recovery, but it's installed on a separate physical server.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Andrew was correct in determining that the ESX partition was full thus the awarding him all the points. My last comment with the KB link was the actual fix that allowed the ESX server to be reconnected. Selected it as the Best Solution so that others would benefit from it as well as I did.
ASKER
That's a great idea! Could you please point me to the location of the logs that can be safely deleted?
Thanks!