CPU usage is shown at maximum when no jobs appear to be running on the vSphere Data Protection (VDP) appliance
search cancel

CPU usage is shown at maximum when no jobs appear to be running on the vSphere Data Protection (VDP) appliance

book

Article ID: 343062

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • The vSphere Data Protection (VDP) appliance shows CPU usage at maximum when no jobs appear to be running.
  • Running the top command on the VDP appliance shows a single Java PID consistently using 100% or more CPU.
  • In the vSphere Web Client, the Monitor tab for the VDP appliance shows constant CPU usage over 75%, and a very high ready rate.
  • In the /usr/local/avamar/var/vdr/server_logs/vdr-server.log file, you may see messages similar to:

    ERROR [http-8543-exec-9]-services.ApplianceInfoServiceWS: Unable to get the total Capacity of vdp: null

    This message indicates that an infinite loop is occurring.

  • Also in the vdr-server.log file, you may see these messages:

    • Unable to determine the local server time: <variable> : Retry‚Ķ
    • Retry to get the server object


Environment

VMware vSphere Data Protection 5.8.x
VMware vSphere Data Protection 5.1.x
VMware vSphere Data Protection 5.5.x

Cause

This issue occurs due to a known issue involving the MCS Service connection in the vSphere Data Protection (VDP) appliance.

Resolution

This issue is resolved in VMware vSphere Data Protection (VDP) version 6.0.1, available at VMware Downloads. For more information, see the 6.0.1 Release Notes.

To work around this issue, you must restart the Tomcat instance running both the VDP and the VDP configuration applications.

To restart the Tomcat instance, perform a soft restart of the VDP appliance, using the VMware vCenter Server.

For more information, see VMware VirtualCenter Server memory usage grows when VMware vSphere Data Protection 5.8 is in use (2094879).

Additional Information



VMware VirtualCenter Server memory usage grows when VMware vSphere Data Protection 5.8 is in use