Differences

This shows you the differences between two versions of the page.

--- resolution_area:watchdog_resolutions:res-w9301 [2021/06/25 10:09] – external edit 127.0.0.1
+++ resolution_area:watchdog_resolutions:res-w9301 [2021/07/05 20:28] (current) – 10.91.120.28
@@ Line 1: / Line 1: @@
 =====HighCPU=====
-**Level:** __Critical__
+**Level:** __Critical__ FIXME
-**Purpose:**
+**Purpose:** Alert Errigal engineers to excessive CPU usage on an application server. Excessive CPU usage over a period of time is indicative of an underlying problem that should be investigated.
-**Scenario:**
+**Scenario:** CPU usage over period of time has been very high.
-**Resolution:**
+**Resolution:** Log onto the server in question, run a top command to determine process using the most CPU. This will identify which application is eating all the CPU. This could be anything from alarmCache, EMS/Snmp Manager to a long running query in the database.
 **Manual Action Steps:**
+<code>
+Run the below command on the server:
+top
-**Auto Clear:**
+Check number of CPUs
+ egrep 'core id|physical id' /proc/cpuinfo | tr -d "\n" | sed s/physical/\\nphysical/g | grep -v '^$' | sort | uniq | wc -l
+</code>
+Examine the process with the highest CPU usage, also the load averages at the top. Please note the number of cores matters when using the load averages. It's possible especially if end-user performance is impacted, that the offending application may need to be restarted.
+**Auto Clear:** Yes

Internal Errigal Collaboration Wiki