VMWARE Probe stops monitoring intermittently

Document ID : KB000007403
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

vmware probe stops monitoring intermittently and it works for sometime whenever we restart the probe.

The following are the errors shown in the vmware log files.

Jul 07 10:01:16:303 [attach_socket, vmware] (120) Callback error, Exception in callback for protected void com.nimsoft.nimbus.NimProbeBase.cbStatus(com.nimsoft.nimbus.NimSession,int) throws com.nimsoft.nimbus.NimException: GC overhead limit exceeded: GC overhead limit exceeded 

Jul 07 18:31:58:810 [Data Collector - , vmware] Unexpected fatal error occurred during data collection against DataCollector for  Jul 07 18:31:58:811 [Data Collector - , vmware] java.lang.OutOfMemoryError: Java heap space 

at java.util.Formatter.parse(Unknown Source) 

Environment:
VMware probe runs on Windows 2012 r2 machine. Primary Hub : Cent OS.VMware probe version : 6.72UIM: 8.4.7, 8.5 and 8.5.1ESXi version - 5.5Vcenter version - 6.0
Cause:

Most of the times it would happen because of memory issues with the probe. So allocating proper intial and maximum memory for the probe would resolve the issue.

 

Resolution:

Increasing the startup parameters for vmware probe would resolve the issue. 

1. Open the vmware probe in Raw Configure option. 

2. Go to "Startup" options to increase the initial and max memory settings. 

              java_mem_max = -Xmx4096m 

        java_mem_init = -Xms1024m 

        max_perm_size = -XX:MaxPermSize=512m

3. Change the existing values for options key with below. 

             options = -Xms1024m -Xmx4096m -Duser.language=en -Duser.country=US 

4. Cold start (Deactivate and Activate) the probe.

Additional Information:

https://docops.ca.com/ca-unified-infrastructure-management-probes/ga/en/alphabetical-probe-articles/vmware-vmware-monitoring/vmware-vmware-monitoring-release-notes