"Memory exceeds hard limit" error on ESXi 5.5 P09 and P10
search cancel

"Memory exceeds hard limit" error on ESXi 5.5 P09 and P10

book

Article ID: 317927

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • The ESXi host is running 5.5 P09 (build 4345813) or P10 (build 4722766)
  • In the /var/log/hostd.log file, there are entries similar to:

    2017-02-01T16:34:39.613Z [29340B70 error 'UW Memory checker'] Current value 780292 exceeds hard limit 780185. Shutting down process.
    2017-02-01T16:34:39.613Z [29340B70 panic 'Default']
    -->
    --> Panic: Memory exceeds hard limit. Panic
    --> Backtrace:


    And

    [...]Failed to read advanced option subtree UserVars.HostClient.SessionTimeout: vim.fault.InvalidName
    [...]Failed to read advanced option subtree UserVars.HostClient.EnableVisualEffects: vim.fault.InvalidName
    [...]Failed to read advanced option subtree UserVars.HostClient.EnableMOTDNotification: vim.fault.InvalidName
    [...]Failed to read advanced option subtree UserVars.HostClient.CEIPOptIn: vim.fault.InvalidName
    [...]Failed to read advanced option subtree UserVars.HostClient.ShowOnlyRecentObjects: vim.fault.InvalidName
    [...]Failed to read advanced option subtree UserVars.HostClient.DefaultConsole: vim.fault.InvalidName
    [...]Failed to read advanced option subtree UserVars.HostClient.WelcomeMessage: vim.fault.InvalidName

    Note: This log excerpt is an example. Date, time, and environmental variables may vary depending on your environment.


Environment

VMware vSphere ESXi 5.5

Cause

A memory leak has been identified in the ESXi Host Client (esx-ui) interface released as part of ESXi 5.5 P09 (build 4345813) and P10 (build 4722766).
 
Note: This issue is not seen on ESXi 6.x.

Resolution

This is a known issue affecting ESXi 5.5 P09 (build 4345813) or P10 (build 4722766).
 
To resolve this issue, install the updated ESXi Host Client VIB.
  1. Download the 2149879_esxui-signed-5064950.zip file attached to this Knowledge Base article.
  2. Extract and transfer the esxui-signed-5064950.vib file to the ESXi host with WinSCP.
  3. Install the esxui-signed-5064950.vib on the ESXi host. For more information on installing VIBs, see Installing async drivers in ESXi 5.x and 6.x using esxcli and async driver VIB file (2137854)
 
To work around this issue if you are unable to install the VIB, uninstall the ESXi Host Client from the ESXi host.
  1. Log in as root to the ESXi console through SSH or iLO/DRAC with root credentials.
  2. Remove the ESXi Host Client with these commands:

    esxcli software remove -n esx-ui
    esxcfg-advcfg -L "HostClient.SessionTimeout"
    esxcfg-advcfg -L "HostClient.EnableVisualEffects"
    esxcfg-advcfg -L "HostClient.EnableMOTDNotification"
    esxcfg-advcfg -L "HostClient.CEIPOptIn"
    esxcfg-advcfg -L "HostClient.ShowOnlyRecentObjects"
    esxcfg-advcfg -L "HostClient.DefaultConsole"
    esxcfg-advcfg -L "HostClient.WelcomeMessage"

     
  3. Restart the ESXi hostd management agent:

    /etc/init.d/hostd restart


Additional Information

Attachments

2148979_esxui-signed-5064950.zip get_app