8-184
Cisco IOS XR Troubleshooting Guide for the Cisco CRS-1 Router
OL-21483-02
Chapter 8 Process Monitoring and Troubleshooting
Monitoring CPU Usage and Using Syslog Messages
When wdsysmon detects a CPU-hog condition a syslog message is generated. Follow the recommended
action for the following syslog messages:
Message: %HA-HA_WD-6-CPU_HOG_1 CPU hog: cpu [dec]'s sched count is [dec].
RP/0/RP0/CPU0:Dec 22 16:16:34.791 : wdsysmon[331]: %HA-HA_WD-6-CPU_HOG_1 : CPU hog: cpu
1's sched count is 0.
Wdsysmon has detected a CPU starvation situation. This is a potentially high priority process spinning
in a tight loop. The ‘sched count’ is the number of times the wdsysmon ticker thread has been scheduled
since the last time the wdsysmon watcher thread ran.
Check the system status, including the saved log for evidence of a high priority CPU hog. See the
“Troubleshooting High CPU Utilization and Process Timeouts” section on page 8-185 for information
on checking system status.
Message: %HA-HA_WD-6-CPU_HOG_2 CPU hog: cpu [dec]'s ticker last ran [dec].[dec] seconds ago.
RP/0/RP0/CPU0:Dec 22 16:16:34.791 : wdsysmon[331]: %HA-HA_WD-6-CPU_HOG_2 : CPU hog: cpu
1's ticker last ran 3.965 seconds ago.
Wdsysmon has detected a CPU starvation situation. This is a potentially high priority process spinning
in a tight loop.
Check the system status, including the saved log for evidence of a high priority CPU hog. See the
“Troubleshooting High CPU Utilization and Process Timeouts” section on page 8-185 for information
on checking system status.
Message: %HA-HA_WD-6-CPU_HOG_3 Rolling average of scheduling times: [dec].[dec].
RP/0/RP0/CPU0:Dec 22 16:16:34.791 : wdsysmon[331]: %HA-HA_WD-6-CPU_HOG_3 : Rolling average
of scheduling times: 0.201.
Wdsysmon has detected a CPU starvation situation. This is a potentially high priority process spinning
in a tight loop. A high value for the rolling average indicates that a periodic process is not being
scheduled.
Check the system status, including the saved log for evidence of a high priority CPU hog. See the
“Troubleshooting High CPU Utilization and Process Timeouts” section on page 8-185 for information
on checking system status.
Message: %HA-HA_WD-6-CPU_HOG_4 Process [chars] pid [dec] tid [dec] prio [dec] using [dec]% is the top user
of CPU
RP/0/RP0/CPU0:Dec 22 16:16:35.813 : wdsysmon[331]: %HA-HA_WD-6-CPU_HOG_4 : Process wd_test
pid 409794 tid 2 prio 14 using 99% is the top user of CPU.
This message is displayed after the CPU hog detector trips. It shows the percentage of CPU used by the
busiest thread in the top user of CPU. See the “Troubleshooting High CPU Utilization and Process
Timeouts” section on page 8-185 for information on checking system status.
The show watchdog trace command displays additional information about the potential CPU hog. If
there is a persistent CPU hog (a hog that lasts for more than 30 seconds) the node will be reset. There
will be a log such as the following just before the reset:
RP/0/RP0/CPU0:Dec 20 10:36:08.990 : wdsysmon[367]: %HA-HA_WD-1-CURRENT_STATE : Persistent
Hog detected for more than 30 seconds