Server Ab-end with a CPU Hog Detected
Articles and Tips: qna
01 Aug 2001
Q.
Dear Ab-end: My NetWare 5.x server Abended with a CPU Hog detected by Timer Abend. The currently running process is NDPSM.NLM, with the code path running through WS2_32.NLM. The code gets stuck in a loop and eventually causes the CPU Hog to Abend. What can I do to get my server back to serving? -- Stuck with a Slumped Server
A.
Dear Stuck: Your server is experiencing this Abend directly from the endless loop the server is executing. Endless loops in NLMs typically cause the NetWare server to Abend, since the loop uses too many server cycles. This Abend will be isolated to the offending NLM, allowing your server to continue to run.
To fix this problem, load WSOCK2A.EXE (or later) AFTER applying NetWare 5.1 Service Pack 2 (NW51SP2A.EXE). WSOCK2A.EXE has dependencies that are available in Service Pack 2, but do not ship with NetWare 5.1. (FYI, these same fixes will be included in NetWare 5.1 Service Pack 3, when it becomes available.)
* Originally published in Novell AppNotes
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.