VMware vCenter 6 Web Console doesn’t load or very slow


Update (05 Sept 2017):

After changing the value to 512MB we continued to have this issues on and off, contacted VMware Support yet again and now they have advised to increase the MaxPermMB from 512 to 1024 (which is apparently the max value this can go to). We will continue to monitor to see if there is any improvement.

Environment

VMware vCenter 6.0.0 Build 4541948 (Update 2a) – could effect other vCenter versions also.

Issue:

After a period of a week or more the vCenter Web Console slows down dramatically to the point where the website doesn’t load anymore and the browser times out.

Looking into the /var/log/vmware/vsphere-client/logs/vsphere-client-virgo.log file you it displays the following Out Of Memory error:

Run: less vsphere-client-virgo.log

vmware_outofmemory

“[2017-03-15T13:59:07.853+13:00] [ERROR] ing.timer.TimerFactoryBean#0 o.s.scheduling.timer.MethodInvokingTimerTaskFactoryBean Invocation of method ‘update’ on target class [class com.vmware.vise.vim.cm.healthstatus. HealthStatusUpdater] failed java.lang.OutOfMemoryError: PermGen space”

Solution:

  1. (Workaround) Reboot the vCenter, according to VMware Support you should reboot it often to ensure the vCenter doesn’t run out of memory.
  2. (Permanent fix) Increase the memory size for vspherewebclientsvc in the service-layout.mfx file from 256 to 1024.
    1. Use WinSCP to connect to vCenter Server
    2. Browse to and edit: /etc/vmware/service-layout.mfx
    3. Find the line with the firstboot_name ngc_firstboot
    4. Under the column ‘MaxPermMB’ change the value from 256 to 1024
    5. Save service-layout.mfx file
    6. SSH to vCenter Server
    7. Run: /etc/init.d/service vsphere-client restart
Advertisements

Deploy ESXi 6.0 upgrade to Update 2 Fails


Issue:

When attempting to remediate an ESXi host with 6.0 Update 2, the following error displays in Update Manager:

“The host returns esxupdate error code:14. There is an error when resolving dependencies. Check the Update Manager log files and esxupdate log files for more details.”

In /var/log/esxupdate.log

esxupdate: ERROR: DependencyError: VIB VMware_bootbank_vsanhealth_6.0.0-3000000.3.0.2.43.4064824 requires esx-base >= 6.0.0-2.43, but the requirement cannot be satisfied within the ImageProfile.

Solution:

There is a dependency for Update 2 that needs installing first,  weirdly enough the dependency is included in Update 2.

Resolution:

  • Enable ESXi Shell and SSH on ESXi host
  • Download Update 2 from VMware Patches
  • Copy zip file to /vmfs/volumes/datastore (file is too large to copy to /var/tmp)
  • Use Putty to connect to ESXi host
  • Run: esxcli software vib install -n esx-base -n vsan -n vsanhealth -d /vmfs/volumes/datastore1/update-from-esxi6.0 6.0_update02.zip

-n = Specifies VIBs from a depot, using one of the following forms: name, name:version, vendor:name, or vendor:name:version.

-d = Specifies full remote URLs of the depot index.xml or server file path pointing to an offline bundle .zip file.

esxi_vib_install

  • Reboot the ESXi host.
  • To confirm the components installed correctly run: esxcli software vib list
  • These are the dependencies and versions installed:

esxi_components

  • Once the server is back online now use Update Manager to remediate Update 2 (and any additional patches) onto ESXi host.