Understanding "CPU Starvation Detected" Messages in Symantec Directory ALARM Logs

Products

• CA Directory
• CA Identity Manager
• CA Identity Portal
• CA Identity Suite
• SITEMINDER

Issue/Introduction

This article explains the meaning of the "CPU starvation detected" message found in the Symantec Directory ALARM logs and describes how to interpret the associated STATS logs.

Environment

Directory 14.1

Cause

CPU starvation occurs when the operating system does not allocate sufficient CPU time to the DXserver process. The cpu-starvation-threshold parameter triggers an alarm when the server's CPU usage falls below the defined threshold.

Resolution

To analyze the CPU starvation alarm, perform the following:

1. Review ALARM Log: Identify the threshold value from the message: DSA_E3730 CPU Seconds [Actual] has fallen below threshold [Threshold], CPU starvation detected
2. Review STATS Log: Locate the corresponding entry to see the CPU Seconds usage.
   • The format is CPU Seconds [Used]/[Total].
   • The ideal value is 60/60 (60 seconds of CPU time allocated over 60 seconds).
   • A value of 13/60 indicates only 13 seconds were allocated to DXserver in the last 60 seconds.
3. Configure Threshold: Use the set cpu-starvation-threshold command to adjust sensitivity.
   • The default threshold is 5.
   • The ALARM log threshold is calculated as: 60 - cpu-starvation-threshold.
   • Example: If cpu-starvation-threshold is 5, the alarm triggers at 55 (60 - 5).

Additional Information

For further information, see the documentation Understanding CPU Starvation Errors and set cpu-starvation-threshold Command

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.