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

Error [403] The maximum number of sessions has been exceeded in the H5 client during login or logout

  Symptoms In virgo log, you see messages similar to: [2020-05-19T07:25:45.285Z] [ERROR] http-nio-5090-exec-130 72026859 142953 501051 com.vmware.vise.security.spring.DefaultAuthenticationProvider logout failed for sessionId 142953, clientId 501051 java.lang.IllegalStateException: The specified cardinality of 1..1 for osgi:reference implementing com.vmware.vcenter.apigw.api.ApiGatewaySessionManager in bundle com.vmware.h5ngc requires that exactly one OSGI service satisfies the filtering criteria but no such service was found.         at com.vmware.o6jia.context.ExternalServiceTargetSource.getTarget(ExternalServiceTargetSource.java:99)         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:192)         at com.sun.proxy.$Proxy159.logout(Unknown Source)         at com.vmware.vise.security.spring.DefaultAuthenticationProvider.logoutInternal(DefaultAuthenticationProvider.java:548)         at c

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 the error: Error connecting to <path><virtual machin

"Performance data is currently not available for this entity" viewing the performance tab

  Symptoms While accessing the performance tab and navigating to Overview, you see: No data available   The data for Real time, but fails to retrieve it for past 1 day, week, month or year.  While selecting the advance parameter in performance tab, you see: Performance data is currently not available for this entity Cause This issue is caused by the vCenter Server database (Postgress) containing a stale/future time stamp reference for the ESXi host when the data was collected. For vCenter Servers using SQL, see  "Performance data is currently not available for this entity" error after updating rollup in vSphere Resolution Backup the vCenter database. For more info