|
Question : w2k3 server locking up
|
|
We have a server that is running AD, DHCP, DNS and File services and we are having issues with it locking up. We did a performance log and were told to take a look at these areas. Can anyone what i should do or where to begin. I will include the entire perf log at the bottom.
\Memory\Pages/sec
[Min: 0.142, Max: 3,199.902, Avg: 254.855]
- High values (~500) may be fine if disk subsystem is fast.
- Review % Idle Time and Avg. Disk sec/Transfer for I/O rates.
\Process(_Total)\Handle Count
[Min: 15,819, Max: 19,491, Avg: 16,384]
- This may be a normal amount on Terminal Servers in Application Mode.
- Investigate individual applications using > 1,500 handles.
LOG-----------------------------------------------------------------
Performance Monitor Log Summary
===============================
Log Filename : PERFWIZ - 120 SECOND INTERVAL_08160901.BLG
Server Name : Server
Start Date & Time : 08/16/2009 09:01:47 (Uptime was: 0d 21h 2m 21s)
End Date & Time : 08/16/2009 12:27:47 (Uptime was: 1d 0h 28m 22s)
Log Duration : 0d 3h 26m 0s
Total Samples : 104
Sample Interval : 0d 0h 2m 0s
Memory utilization on the server during the monitoring time. These are the Different memory counters which were active at the time and the data which they posses.
Memory Minimum Maximum Average
=========================================================================
Available Bytes : 2,133MB | 2,367MB | 2,339MB
Pool Paged Bytes : 42MB | 121MB | 47MB
Pool NonPaged Bytes : 27MB | 44MB | 27MB
Free System PTEs : 187,343 | 187,365 | 187,362
Handle Count : 15,819 | 19,491 | 16,384
Thread Count : 758 | 907 | 786
Private Bytes : 367MB | 533MB | 383MB
Virtual Bytes : 2,951MB | 3,779MB | 3,083MB
Working Set : 1,050MB | 1,493MB | 1,102MB
Cache Bytes : 103MB | 181MB | 117MB
Committed Bytes : 462MB | 657MB | 484MB
Commit Limit : 4,457MB | 4,457MB | 4,457MB
% Committed Bytes Used : 10% | 15% | 11%
Pages/sec : 0.142 | 3,199.902 | 254.855
Processor which were running at the time of monitoring and the different processor counters which were active at the time
Processor Minimum Maximum Average
Processor Queue Length : 2 | 13 | 4
% Processor Time : 0.45% | 100% | 7.13%
Processor: 0 : 0.45% | 100% | 7.13%
% DPC Time : 0% | 0.49% | 0.06%
Processor: 0 : 0% | 0.49% | 0.06%
% Interrupt Time : 0% | 1.78% | 0.2%
Processor: 0 : 0% | 1.78% | 0.2%
Physical disk utilization on the Server Name : PLI1PDC
Physical Disk Minimum Maximum Average
===============================================================
% Idle Time : 56.74% | 100.21% | 94.2%
Disk: 0 C: D: : 13.21% | 100.16% | 89.1%
Disk: 1 G: : 100.21% | 100.27% | 99.3%
Avg. Disk sec/Transfer : 0 | 0.016 | 0.001
Disk: 0 C: D: : 0 | 0.007 | 0.001
Disk: 1 G: : 0 | 0.031 | 0
Disk Bytes/sec : 21KB | 14,444KB | 1,111KB
Disk: 0 C: D: : 21KB | 14,444KB | 1,110KB
Disk: 1 G: : 0KB | 119KB | 1KB
Avg. Disk Queue Length : 0.001 | 1.956 | 0.135
Disk: 0 C: D: : 0.001 | 1.956 | 0.135
Disk: 1 G: : 0 | 0.001 | 0
Split IO/Sec : 0.033 | 56.327 | 1.683
Disk: 0 C: D: : 0.033 | 56.327 | 1.683
Disk: 1 G: : 0 | 0 | 0
Disk Transfers/Sec : 2.967 | 484.392 | 50.78
Disk: 0 C: D: : 2.967 | 484.392 | 50.759
Disk: 1 G: : 0 | 1.886 | 0.02
Network card Usage on the Server Name : PLI1PDC
Network Interface Minimum Maximum Average
=========================================================================
Bytes Total/sec
Intel[R] PRO_1000 CT Network Con: 1KB | 306KB | 14KB
MS TCP Loopback interface : 0KB | 18KB | 1KB
Current Bandwidth
Intel[R] PRO_1000 CT Network Con: 1,000Mbit | 1,000Mbit | 1,000Mbit
MS TCP Loopback interface : 10Mbit | 10Mbit | 10Mbit
Output Queue Length
Intel[R] PRO_1000 CT Network Con: 0 | 0 | 0
MS TCP Loopback interface : 0 | 0 | 0
Packets/sec
Intel[R] PRO_1000 CT Network Con: 5 | 817 | 26
MS TCP Loopback interface : 1 | 53 | 5
Packets Received Discarded
Intel[R] PRO_1000 CT Network Con: 0 | 0 | 0
MS TCP Loopback interface : 0 | 0 | 0
Packets Received Errors
Intel[R] PRO_1000 CT Network Con: 0 | 0 | 0
MS TCP Loopback interface : 0 | 0 | 0
We also were monitoring the top ten applications on the server by the 10 different counters.
The first one is the Handle counts. In the user interface, an interface added to an object that facilitates moving, sizing, reshaping, or other functions pertaining to an object. In programming, a pointer to a pointer, that is, a token that lets a program access an identified resource.
TOP 10: Handle Count Minimum Maximum Average
=========================================================================
1. System : 3,376 | 3,444 | 3,388
2. svchost#4 : 1,343 | 1,503 | 1,380
3. lsass : 1,000 | 1,109 | 1,028
4. csrss : 885 | 1,082 | 920
5. iexplore : 699 | 732 | 716
6. winlogon : 584 | 650 | 603
7. EnterpriseService : 581 | 594 | 583
8. explorer : 430 | 519 | 494
9. LogMeIn : 334 | 444 | 370
10. services : 427 | 439 | 430
The second one is the Thread counts. the number of threads running in a process associated with the each application.
TOP 10: Thread Count Minimum Maximum Average
=========================================================================
1. System : 77 | 81 | 78
2. svchost#4 : 47 | 69 | 51
3. w3dbsmgr : 63 | 63 | 63
4. lsass : 56 | 61 | 58
5. EnterpriseService : 30 | 32 | 30
6. LogMeIn : 18 | 30 | 20
7. winlogon : 20 | 26 | 22
8. iexplore : 19 | 26 | 22
9. dlpsp : 25 | 26 | 25
10. spoolsv : 22 | 25 | 23
The third one is Private bytes The current size, in bytes, of the committed memory owned by this process. Memory leaks are identified by a consistent and prolonged increase in Private Bytes. This is the best performance counter for detecting memory leaks.
TOP 10: Private Bytes Minimum Maximum Average
=========================================================================
1. SBAMSvc : 18MB | 121MB | 20MB
2. EnterpriseService : 51MB | 53MB | 52MB
3. w3dbsmgr : 46MB | 46MB | 46MB
4. lsass : 32MB | 33MB | 32MB
5. iexplore : 28MB | 29MB | 29MB
6. LogMeIn#1 : 25MB | 26MB | 25MB
7. LogMeIn : 24MB | 25MB | 24MB
8. svchost#4 : 13MB | 21MB | 13MB
9. cidaemon : 18MB | 18MB | 18MB
10. explorer : 11MB | 15MB | 14MB
The fourth one is virtual bytes. The current size, in bytes, of the virtual address space for this process. The virtual address space limit of a user mode process is 2 GB, unless 3 GB address space is enabled by using the /3GB switch in boot.ini. Performance degrades as this limit is approached, and typically results in a process or system crash.
TOP 10: Virtual Bytes Minimum Maximum Average
=========================================================================
1. EnterpriseService : 296MB | 298MB | 296MB
2. SBAMSvc : 88MB | 204MB | 96MB
3. services : 172MB | 173MB | 173MB
4. cidaemon : 152MB | 152MB | 152MB
5. iexplore : 142MB | 150MB | 146MB
6. w3dbsmgr : 143MB | 143MB | 143MB
7. svchost#4 : 93MB | 139MB | 97MB
8. lsass : 133MB | 135MB | 133MB
9. ShadowProtectSvc#1 : 111MB | 113MB | 111MB
10. cisvc : 112MB | 112MB | 112MB
The fifth one is the Working set. the amount of physical memory assigned to a process by the operating system.
TOP 10: Working Set Minimum Maximum Average
=========================================================================
1. services : 155MB | 157MB | 155MB
2. SBAMSvc : 16MB | 150MB | 23MB
3. LogMeIn : 57MB | 61MB | 58MB
4. svchost#4 : 56MB | 60MB | 57MB
5. EnterpriseService : 11MB | 58MB | 16MB
6. lsass : 44MB | 55MB | 52MB
7. cidaemon : 2MB | 49MB | 8MB
8. pdmwService : 45MB | 45MB | 45MB
9. ShadowProtectSvc#1 : 11MB | 41MB | 15MB
10. inetinfo : 37MB | 37MB | 37MB
The sixth one is the % processor time the Processor time is a measure of the time that a job or task controls the processor.
TOP 10: % Processor Time Minimum Maximum Average
=========================================================================
1. SBAMSvc : 0% | 45.95% | 3.67%
2. explorer : 0% | 3.74% | 0.91%
3. System : 0% | 7.14% | 0.55%
4. LogMeIn#1 : 0.02% | 1.19% | 0.45%
5. EnterpriseService : 0.07% | 0.73% | 0.14%
6. sw_d : 0.04% | 0.13% | 0.08%
7. services : 0% | 0.77% | 0.07%
8. SBAMTray : 0% | 0.12% | 0.07%
9. lsass : 0% | 0.74% | 0.07%
10. ShadowProtectSvc#1 : 0% | 1.59% | 0.05%
The seventh one is the IO data bytes.It Shows the rate that the process is reading and writing bytes in I/O operations. It counts all I/O activity generated by the process to include file, network, and device I/Os.
TOP 10: IO Data Bytes Minimum Maximum Average
=========================================================================
1. SBAMSvc : 0KB | 8,666KB | 402KB
2. System : 2KB | 10,326KB | 105KB
3. EnterpriseService : 17KB | 194KB | 32KB
4. lsass : 0KB | 211KB | 3KB
5. LogMeIn : 0KB | 225KB | 3KB
6. svchost#4 : 0KB | 57KB | 1KB
7. SAAZWatchDog : 0KB | 3KB | 1KB
8. ntfrs : 0KB | 51KB | 1KB
9. LogMeIn#1 : 0KB | 5KB | 1KB
10. explorer : 0KB | 8KB | 1KB
|
Answer : w2k3 server locking up
|
|
it can be the memory. try replacing the sticks or switching slots
|
|
|
|
|
