Novell NETWARE 6-DOCUMENTATION Manual page 2436

4
Finding CPU Hogs
Troubleshooting Server Problems
You can use NetWare
problems. This chapter includes methods for doing the following:
Finding CPU Hogs (page 63)
Finding High Memory Users (page 64)
Tracing Abend Sources (page 65)
Locating Server Process Hogs (page 66)
Locating Disk Space Hogs (page 66)
Seeing Who Is Using a File (page 67)
A CPU hog could be an NLM
become corrupted and, as a result, is using up so much of the server's CPU
cycles that other NLM programs are not able to run properly.
CPU hog problems are indicated on the Server Health Monitoring page by a
suspect or bad status for the CPU Utilization-x indicator.
To track down a CPU hog using NetWare Remote Manager, do the following:
1
Under the Diagnose Server heading, click the Profile/Debug link.
2
Identify the offending thread and Parent NLM.
2a
In the Execution Profile Data by Thread table, note the thread and the
Parent NLM that is taking the longest execution time.
2b
To see which tasks the thread is trying to perform, do one of the
following:
Click the execution time link.
®
Remote Manager to troubleshoot some server
program that is poorly designed or has
TM
Troubleshooting Server Problems
63