We have a BorderManager 3.8SP5 server running on Netware 6.5SP7. We have applied all Post SP7 Netware patches at this point.

Our Bordermanager is merely a non-transparent proxy server, with six 5GB volumes for caching and our clients are not using client-access. There are few if any rules implemented. This server holds no other roles, except perhaps that it hold a replica of our tree.

Every so often, at no regular interval, the server will abend due to PROXY.NLM, become unresponsive and/or performance will suffer greatly. A reboot and cache clean seems to do the trick most of the time. Just today, all communication to the server stopped, and the console showed a black screen, and we were forced to cold boot it. Nothing in the abend logs stands out to me here. Below are some snippets from them.

Right this second, the server is stalling every few seconds, and not just network connectivity, the IPKVM attached console does the same thing.

Here is the most common entry:
***********************
************************************************** *******
Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.07

Server BM-IS3 halted Tuesday, April 8, 2008 9:22:09.119 am
Abend 1 on P00: Server-5.70.07: Page Fault Processor Exception (Error code 00000000)

Registers:
CS = 0008 DS = 0023 ES = 0023 FS = 0023 GS = 0023 SS = 0010
EAX = 00000008 EBX = 3199EAAC ECX = 00000000 EDX = 35393132
ESI = 00000007 EDI = 000002DF EBP = 00000000 ESP = 8FA06E08
EIP = 96BB690F FLAGS = 00010202
96BB690F 8B6E50 MOV EBP, [ESI+50]=?
EIP in PROXY.NLM at code start +0005190Fh
Access Location: 0x00000057

The violation occurred while processing the following instruction:
96BB690F 8B6E50 MOV EBP, [ESI+50]
96BB6912 39EB CMP EBX, EBP
96BB6914 7512 JNZ 96BB6928
96BB6916 F686C000000004 TEST byte ptr [ESI+000000C0], 04
96BB691D 7409 JZ 96BB6928
96BB691F 55 PUSH EBP
96BB6920 E83B8DFBFF CALL PROXY.NLM|UndoReceiveTimeOut
96BB6925 83C404 ADD ESP, 00000004
96BB6928 31C0 XOR EAX, EAX
96BB692A 8A4329 MOV AL, [EBX+29]



Running process: Server 21 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 8FA06F7C
OS Stack limit: 8F9FF040
Scheduling priority: 67371008
Wait state: 50500F0 Waiting for work
Stack: --3199EAAC ?
--000002DF (LOADER.NLM|KernelAddressSpace+2DF)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--3199EAAC ?
96BC8B48 (PROXY.NLM|ErrorResult+58)
--3199EAAC ?
--0000015C (LOADER.NLM|KernelAddressSpace+15C)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
88727CE3 (NWSA.NSS|ZH_WriteFile+33)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--3199EBB4 ?
--7947AF64 ?
96BA5895 (PROXY.NLM|FileCreate+A5)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00047A08 (LOADER.NLM|PSD_LibraryErrno+69F8)
--0000015C (LOADER.NLM|KernelAddressSpace+15C)
--3199EAAC ?
--000002DF (LOADER.NLM|KernelAddressSpace+2DF)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
96BA8A37 (PROXY.NLM|oc_requestStart+937)
--3199EAAC ?
-96D1F2F8 (PROXY.NLM|status504Description+0)
-96D1127F ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
887DC9BF (FILESYS.NLM|WriteFile+35)
--3199EF24 ?
-96D67AA0 (PROXY.NLM|DataArrivedStateNotImpl_Eskom+4)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8FA06EA8 ?
88727CD9 (NWSA.NSS|ZH_WriteFile+29)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00047F05 (LOADER.NLM|PSD_LibraryErrno+6EF5)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
-96D67AA0 (PROXY.NLM|DataArrivedStateNotImpl_Eskom+4)
--3199EBB4 ?
--7C6B4700 ?
--F2FA7FAA ?
--000002DE (LOADER.NLM|KernelAddressSpace+2DE)
--00047F05 (LOADER.NLM|PSD_LibraryErrno+6EF5)
--3199EAAC ?
96BA7CB8 (PROXY.NLM|oc_finishWrite+548)
--3199EAAC ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--0EE39004 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
00001372 (LOADER.NLM|SetFlags+7)
--00000010 (LOADER.NLM|KernelAddressSpace+10)
--676E654C ?
--0F27E004 ?
96B6D982 (PROXY.NLM|EntityDataFinished+62)
--3199EF24 ?
--746E6F43 ?
--2D746E65 ?
--676E654C ?
--203A6874 ?
--38373934 ?
--0FEA1A00 ?
96B734E3 (PROXY.NLM|FreeReceiveECBs+F3)
--3199EF24 ?
--87013AB6 ?
--FFFFFFFE ?
--0F27E004 ?
96B6D785 (PROXY.NLM|WriteEntityDataToCache+1F5)
--0F27E004 ?
--87013AB6 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00031C56 ?
--0F27E004 ?
--0F27E004 ?
96B6D241 (PROXY.NLM|ProcessReplyBody+351)
--0F27E004 ?
--0F27E004 ?
--0F27E004 ?
96B90B2E (PROXY.NLM|ProcessHTTPReplyHeaders+7E)
--0F27E004 ?
--00031C56 ?
--87089733 ?
--8708967E ?
96B6C94C (PROXY.NLM|ClientReplyHandler+BC)
--0F27E004 ?
--8708967A ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
96BC9260 (PROXY.NLM|CallrsCallBacks+0)
96BC92B4 (PROXY.NLM|CallrsCallBacks+54)
--0F27E004 ?
00369BC2 (SERVER.NLM|StartWorkToDo+23)
--0F27E004 ?
--00031C56 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--7C931180 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
00219392 (SERVER.NLM|WorkerThread+50E)
--0F27E004 ?
--2E3B944B ?

Additional Information:
The CPU encountered a problem executing code in PROXY.NLM. The problem may be in that module or in data passed to that module by a process owned by SERVER.NLM.