posted on January 10th 2017, at 14:42
by lunarg
If your ESX host has lost connection to the vCenter server, but you can still directly access the host's management, and can find nothing else wrong with the vCenter server or its network connection to the host, you may want to the free space on your ESX host.

Logs and other temporary files may have filled up one or more ramdisk partitions (e.g. when you don't have a persistent scratch partition, it gets mounted on /tmp). This can cause any of the following issues:

Connection loss between the ESX host and vCenter server;

Errors when attempting to reconnect or add an ESX host to a vCenter server;

Errors while attempting to activate or configure HA;

Other unexplainable errors...

You can   ...
On October 11th 2017 at 17:30, Ingo wrote:
As a permanent solution for the EQL Logging Problem of MEM1.5, change /etc/cim/dell/ehcmd.conf: MaxLogSizeMB = 50.

On my ESX servers, RAM Disk "root" is 32MB, so I changed the parameter to 10. This also requires a reboot of the ESX server (adviced by Dell/EQL support).
« June 2024»
« Debating Windows vs. Linux vs. Mac is pointless: they all have their merits and flaws, and it ultimately comes to down to personal preference. »