UIM Probe consuming High CPU

Document ID : KB000124801
Last Modified Date : 31/01/2019
Show Technical Document Details
UIM Probe consuming High CPU
Few of the possible causes are:
(1) Old Java/Probe release
(2) Hot-fix available
(3) Configuration issues like:
(a) Insufficient probe memory
(b) issues with existing configuration / setup
(4) Additional Probe specific issues:
(a) logmon probe - use of general expressions
(b) nas probe - replication failure
(c) snmpcollector probe
(d) database monitoring probes like Oracle, sqlserver - checkpoint timeout errors
1. Identify the probe responsible for High CPU, refer the Additional Information section on identifying the same

2. Older Java/Probe release:
  • It could be possible a probe has been running for quite sometime and over this period, the java release it was designed upon has become obsolete (or) is no longer the latest one (or) newer release of probe is available
  • Refer the probe release notes to find if a newer release is available and compatible, if yes, upgrade the probe to the latest release. You could refer the probe release notes clicking here
3. Hot-fix available:
  • It would a good idea to refer the hot-fix index to find if there is a hot fix created for the probe, if yes, check the pre-requisite, refer the readme before upgrading the probe to the hot-fix level. The link to the hot-fix index could be found here 
4. Configuration issue(s):
(a) Insufficient probe memory:
One of the possible causes could be insufficient probe memory, if there is enough free memory available, try increasing the probe's initial and maximum memory (found in the Probe configuration startup -> opt section)

(b) Issues with existing configuration / setup:
You could try to take backup and delete the existing probe (please be aware there could be data loss, if unsure about the consequences, reach out to Support), remove the probe folder manually, deploy the same (or) newer release of probe if available (provided you have read the Probe release notes)

4. Additional Probe specific issue(s):
(a) logmon probe - use of general expressions:
This is specific to logmon probe, using general syntax like * as match pattern would increase the CPU load, try using more specific expressions to meet your requirement. The below links could be very handy when using Regex expressions:

Regex Basics
Including / Excluding Expressions using Regex

(b) nas probe - replication failure:
This is specific to nas probe, in a multiple nas environment with Replication enabled, Replication failures could cause the probe to consume High CPU, check the nas probes on the respective robots are activated, running error free, on the same latest updated release 

(c) snmpcollector probe:
This is specific to snmpcollector probe, check if any profile is not getting activated.
  • Probably a lot of load on the end Server, refer the below link to identify if too many metrics are created:
  • Check if the end device is certified, refer the below link for device support list:
  • It would also be good to refer the below link discussing on snmpcollector probe known issues:

(d) database monitoring probes like Oracle, sqlserver - checkpoint timeout errors:
This is specific to database monitoring probes like Oracle, sqlserver probes, check if there are checkpoint timeout errors in the probe log files (check the log files with debug enabled, click here to get understanding on how to enable debugging), click here for further understanding
If the issue continues to exist and/or if the above mentioned points are not applicable, please open a ticket with CA Support
Additional Information:
Procedure to identify the probe responsible for High CPU:
  • Note down the PID (stands for Process identifier) for the identified High CPU consuming process:
Windows environment:
Launch Task Manager -> Under Processes tab -> sort by CPU (descending order) to identify the process -> enable PID column -> note down the PID 

Linux/UNIX environment:

Find out the PID for the process consuming High CPU using the utilities like top, ps -ef to identify the offender, you may need to work with the respective System Administrator to get the information
  • From the Infrastructure Manager (or) Admin console, map the PID identified from the above procedure to find out the responsible probe