After running OK for 18 months our server just stopped with no abend log and apparently everything loaded but hungRebooted and it cam up nicely but fell over again next dayIt has two pools SYS & NSS with all the data
NSS does not mount so no volumes visiblePoolactivate does not recover the situationAfter several reboots I finally managed to retrieve an abend log belowHealth logs etc did not reveal anything other than there had been an abendDoes anyone have any idea what's up (or down I suppose I should say !)
ThanksSplash
Novell Open Enterprise Server, NetWare 6.5PVER: 6.50.07
Server MNR-SERVER halted Saturday, 23 August 2008 6:07:22.754 am
Abend 2 on P01: Server-5.70.07-1937: CPU Hog Detected by Timer
Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0023 SS = 0010
EAX = FBF17BA3 EBX = 87DA95E0 ECX = 87DE7018 EDX = 00000000
ESI = 87E42748 EDI = 0003C128 EBP = 87954F54 ESP = 87954F40
EIP = 00000000 FLAGS = 00000046

Running process: Interrupt service routine (nested count 0)
Interrupted process: Processor 1: IDLE Thread Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 87954FB8
OS Stack limit: 87953000
CPU 1 (Thread 879524A0) is in a NO SLEEP state
Scheduling priority: 67371008
Wait state: 3031111 Intermedidate Goto READY
Stack: --FBF17BA3 ?
87AE317B (LIBNSS.NLM|nssSpinLock+B)
87D99122 (NSS.NLM|NSSMPK_LockNss+62)
-87DE7018 (NSS.NLM|NSSMPK_spinlock+0)
87DA95E0 (NSS.NLM|fireAlarm+0)
--87954F70 ?
87DA95EE (NSS.NLM|fireAlarm+E)
0010B0C2 (LOADER.NLM|kTimer1Interrupt+11)
--FE15A280 ?
--0003C128 (LOADER.NLM|NestedInterruptCount+28)
-87E42748 (NSS.NLM|AlarmWorkToDo+0)
87DA95E0 (NSS.NLM|fireAlarm+0)
-87E42748 (NSS.NLM|AlarmWorkToDo+0)
003622D8 (SERVER.NLM|kDoFastWorkToDo+28)
-87E42748 (NSS.NLM|AlarmWorkToDo+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--0003C128 (LOADER.NLM|NestedInterruptCount+28)
-87E42748 (NSS.NLM|AlarmWorkToDo+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
-87E42748 (NSS.NLM|AlarmWorkToDo+0)
0022575C (SERVER.NLM|kWorkToDoCheckAllRunFast+A4)
-87E42748 (NSS.NLM|AlarmWorkToDo+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--010F1319 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000007 (LOADER.NLM|KernelAddressSpace+7)
00225ED8 (SERVER.NLM|MpkSystemWork+68)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--010F1319 ?
0021B0B5 (SERVER.NLM|SchedProcessorIdleLoop+4B9)
--10000001 ?
--FE15A280 ?
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000100 (LOADER.NLM|KernelAddressSpace+100)
00209577 (SERVER.NLM|kAddNewProcessor+397)
--01020800 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
878EE72D (ACPIDRV.PSM|PSMProcessorEntryPoint+23)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
0010FB43 (LOADER.NLM|Start+CA)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
" " " " " " " " " " " " " " " " " " " " " " " " " " many times
--00000000 (LOADER.NLM|KernelAddressSpace+0)
Additional Information:
The NetWare OS detected a problem with the system while executing a process owned by SERVER.NLM. It may be the source of the problem or there may have been a memory corruption.