Troubleshooting High CPU Utilization Issues on the ProxySG


<< Back to Knowledge Search

Solution

Overview
How do you troubleshoot and resolve high CPU issues on the ProxySG?
 
Cause
Resolution

There are many different reasons why high CPU utilization may occur on the ProxySG platform.  This article provides the steps to troubleshoot utilization issues with links to supporting procedures and common causes of high CPU utilization.

1. Troubleshooting Considerations

To help identify the cause of the high CPU utilization, consider the following questions while progressing through the troubleshooting steps:

  • Is the proxy continuously at high CPU, or does it peak at certain times?
  • Does CPU utilization come down after production hours?
  • Is CPU utilization peaking periodically then going back to “normal”?  If so, can you graph out the peaks, and identify a trend?
  • Has anything changed recently in the environment that may have triggered the issue such as an increase in network traffic, new applications introduced, configuration changes on the ProxySG or associated network devices, etc.

2. Enable CPU Monitor

The first step to troubleshoot the issue is to enable the CPU monitor on the ProxySG and to activate snapshots every 5 mintues to determine which service or services are generating the high utilization.  The CPU monitor can be accessed at:

https://x.x.x.x:8082/Diagnostics/CPU_Monitor/statistics  

For more information on how to setup the CPU monitor, see How to enable the CPU Monitor on the Proxy SG

NOTE: Once you have finished taking snapshots, be sure to turn the CPU monitor off as it places additional CPU load on the system.

3. Review Common Causes for High CPU

Depending on which service or services CPU Monitor identifies as the source of the high CPU, click on the associated articles below to review the most common causes and resolutions for high CPU utilization for that service:

Object StoreProxySG CPU monitor showing high CPU in Object Store
HTTP and FTPProxySG CPU monitor showing high CPU in HTTP
MiscellaneousProxySG CPU monitor showing high CPU in Miscellaneous
TCPIPProxySG CPU monitor showing high CPU in TCPIP
Policy evaluation - HTTPProxySG CPU monitor showing high CPU in Policy
SSL and CryptographyProxySG CPU utilization at 100% when intercepting SSL traffic troubleshooting guide
LSAProxySG CPU monitor showing high CPU in LSA

4. Known Issues Causing High CPU

If the above articles did not help resolve the high CPU utilization issue, the following articles also document defects or configurations that can cause this issue:
 

Issue TypeFixed ReleaseArticle
DefectSGOS 6.5.7.6CPU monitor showing high CPU in Policy on ProxySG running SGOS 6.5 after installing a policy
ConfigurationN/AWhy is CPU utilization of policy evaluation in SGOS 6.5 much greater than in 6.2?
ConfigurationN/AProxySG Experiencing High CPU Utilization and Input Errors on TCP Interface
ConfigurationN/AProxySG Event Log reports "TCP in Livelock" during periods of high CPU utilization

5. Contact Blue Coat Support

If you are still unable to resolve the high CPU utilization issue, you will need to open a ticket with Blue Coat Support.  In addition to the details from the CPU Monitor, you may also be asked to provide the following:
a) Sysinfo_stats Snapshots
The snapshots should be configured to happen every 5 minutes (default is 60) and run for at least 15 to 20 minutes during the CPU spike.

For detailed instructions on creating the snapshots, please refer to: How do I create low interval snapshot stats on the ProxySG?

b) Sysinfo
The Sysinfo information should be captured after the CPU utilization has returned to normal or after 15 to 20 minutes of high utilization for a persistent utilization spike.

This information can be uploaded via the management console Maintenance tab or captured using the url:
 
https://<proxy_ip>:8082/Sysinfo 

c) Event Log
The Event Log should be captured after the CPU utilization has returned to normal or after 15 to 20 minutes of high utilization for a persistent utilization spike.

This information can be uploaded via the management console Maintenance tab or captured using the url: 
 
https://<proxy_ip>:8082/Eventlog/Statistics

c) TCP Users
While the CPU is experiencing the high utilization, copy the output from the following url:

https://<proxy_ip>/TCP/Users

d) Full Core (Optional)
Depending on the nature and symptoms of the high utilization issue, you may be asked to provide a full core dump of the ProxySG.

For instructions on capturing a full core dump, please refer to: How do I force or create a manual memory dump on the ProxySG?
Workaround
Additional Information
This article contains information previously documented in articles 000014453 and 000015607.
 
Bug Number
InQuira Doc IdKB3894
Attachment

Article Feedback

Hide Properties
First Published      10/01/2014
Last Modified      09/13/2016
Last Published      09/13/2016
Article Audience
Product      ProxySG
Topic      Application Delivery Network, Authentication, Content Filtering, Debugging, Networking
Article Number      000014477
Summary      This article provides a detailed process to follow to troubleshoot high CPU utilization on the ProxySG with links to common causes and resolutions.
Was this helpful?
Comments:
 
Previous MonthNext Month
SunMonTueWedThuFriSat