Skip to main content

(resolved) - Panic: Memory exceeds hard limit


Panic: Memory exceeds hard limit

Error:
 
2019-10-29T03:35:29.797Z panic hostd[309C2B70] [Originator@6876 sub=Default]
-->
--> Panic: Memory exceeds hard limit. Panic
--> Backtrace:
--> [backtrace begin] product: VMware ESX, version: 6.5.0, build: build-6765664, tag: hostd, cpu: x86, os: esx, buildType: release
--->


Fix :

NOTE : Put the host in Maintenance mode. 

To be on a safe side, Copy the /productLocker/vmtools/ folder and its contents from a working host running the same ESXi version/build and replace them on the affected host.

1. take SSH on one working host and the affected host, let us take
esxi0A is working and
esxi0B is affected.

2. Login as "root" user
3. scp the /productLocker/vmtools/  folder and contents from the "good" host to the "problem" host

$ [esxi0A:~]$ scp -rf /productLocker/vmtools/ esxi0B:/productLocker/

COAUTION: This will overwrite the vmtools folder on the problem host, hence you could backup this folder locally if you want but it is not mandatory for the purpose of this activity.
4. Verify the MD5SUM of the vmtools folder contents on the good and bad host. These should match after copying.

For e.g.  md5sum /productLocker/vmtools/windows.iso
1f13ee2eb9dfb4eab070c241a1d71cf4  /productLocker/vmtools/windows.iso


Note: Run the md5sum command on all the files under the vmtools folder on both hosts

5. Restart Management Agents
   services.sh restart

6. Exit Maintenance Mode 

Comments

Popular posts from this blog

Increasing the disk space for the VMware vCenter Server Appliance in vSphere 6.5, 6.7 and 7.0

  Purpose This article provides steps to increase the disk space of a specific VMDK for the vCenter Server Appliance 6.5, 6.7 and 7.0. With the introduction of Logical Volume Management (LVM) in vSphere 6.0 and continued support with vSphere 6.5, 6.7 and 7.0, the vCenter Server disks can be dynamically increased. List of VMDKs for a vCenter Server Appliance 6.5 - Size Mount point and Purpose Note : Resizing the root partition (VMDK1 listed in the KB above) is not supported on 6.5. Please see the vSphere 6.5 Release Notes for more information. Resizing root partition has been added to 6.7 and 7.0. List of VMDKs/Partitions for a vCenter Server Appliance 6.7 - Size Mount point and Purpose   List of VMDKs/Partitions for a vCenter Server 7.0 - Size Mount point and Purpose Note : This KB can be used for the situation like SEAT partition full or any other vCenter appliance partition full. ...

Cloning and converting virtual machine disks with vmkfstools

 Purpose This article provides information and instructions on the use of the vmkfstools command to convert virtual machine disks from one type to another. Resolution The vmkfstools command offers the ability to clone virtual machine content and also convert from one virtual machine disk ( .vmdk ) format into another. Note : The host operating system chosen to perform the conversion may not necessarily support running of virtual machines via the output format defined. vmkfstools maintains the possibility of exporting virtual disks for use in other VMware products which support alternative disk formats. To convert a virtual machine disk from one type to another: Shut down the virtual machine. Virtual machine disk files are locked while in-use by a running virtual machine. Log in to the VMware vSphere Management Assistant (v...

Investigating virtual machine file locks on ESXi

      Details Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails.                 Failed to add disk scsi0:1. Failed to power on scsi0:1   Powering on the virtual machine results in the power on task remaining at 95% indefinitely. Cannot power on the virtual machine after deploying it from a template. Powering on a virtual machine fails with an error: Unable to open Swap File Unable to access a file since it is locked Unable to access a file <filename> since it is locked Unable to access Virtual machine configuration In the /var/log/vmkernel log file, you see entries similar to: WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path>   When opening a console to the virtual machine, you may receive ...