Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 25 AUG 2005 04:58:57PM Matt Sorrell wrote:

Our server suffered an abend this morning and it was traced to the LH.NLM running. In 6+ years of running the NLM on this server, this is the first abend I am aware of in either LH.NLM or LHIPXSER.NLM.

I have been asked to see if we can track down what might have caused the problem. I have included most of the relevant information from the abend.log file, as forwarded to me by our server admins.

Has anyone seen this before or have any ideas?

Server halted Thursday, August 25, 2005 3:09:38.894 am

Abend 1 on P00: Server-5.00k: Page Fault Processor Exception (Error code 00000000)

Registers:

  CS=0008 DS=0010 ES=0010 FS=0010 GS=0010 SS=0010
  EAX=00000000 EBX=4E495845 ECX=4E495845 EDX=08F7CA7D
  ESI=C9C48210 EDI=00000000 EBP=C9E1D0D0 ESP=C9E271C8
  EIP=C9C1C4D3 FLAGS=00014202 
  C9C1C4D3 8B4304         MOV     EAX,EBX+04=?
  EIP in LH.NLM at code start +000094D3h
  Access Location: 0x4E495849

The violation occurred while processing the following instruction:

C9C1C4D3 8B4304 MOV EAX,EBX+04

C9C1C4D6 3B4504 CMP EAX,EBP+04

C9C1C4D9 0F858F000000 JNZ C9C1C56E

C9C1C4DF A1C8F0C1C9 MOV EAX,LH.NLM|ulGroupUnlockResumeThreads=0000000

                      6

C9C1C4E4 8B4B08 MOV ECX,EBX+08

C9C1C4E7 40 INC EAX

C9C1C4E8 85C9 TEST ECX,ECX

C9C1C4EA 7442 JZ C9C1C52E

C9C1C4EC 85FF TEST EDI,EDI

C9C1C4EE 0F8584000000 JNZ C9C1C578

Running process: Rev. Server 1 Process

Created by: NetWare Application

Thread Owned by NLM: LHIPXSER.NLM

Stack pointer: C9E26CAC

OS Stack limit: C9E23300

Scheduling priority: 67371008

Wait state: 5050090 (Wait for interrupt)

Stack: –C9E1F800 ?

  1. -C9D06920 ?
  1. -C9C48210 ?
  1. -C9E1D0C0 ?
     C9C1D0A9  (LH.NLM|LHCloseFile+20D)
  1. -00000000 ?
  1. -C9E271F0 ?
  1. -00000000 ?
  1. -00000006 ?
  1. -01080F00 ?
  1. -0000000E ?
  1. -C9E2723C ?
  1. -000000C7 ?
  1. -00010000 ?
  1. -00000017 ?
     C9C1D3E5  (LH.NLM|LHCloseAll+69)
  1. -00000017 ?
  1. -00000001 ?
  1. -C9E2723C ?
  1. -00000001 ?
  1. -00000000 ?
  1. -C0BA6340 ?
  1. -00000001 ?
  1. -CF4B5680 ?
     C9E05590  (LHIPXSER.NLM|ShutdownSession+130)
  1. -C9E27234 ?
  1. -C9E2723C ?
  1. -000000C7 ?
  1. -00010000 ?
     FC105801  (SERVER.NLM|ThreadContextSwitch+31)
  1. -CF8C120C ?
  1. -D8045000 ?
  1. -0000F41A ?
  1. -01080F00 ?
  1. -00000000 ?
  1. -00000000 ?
  1. -000001C9 ?
  1. -CF4B5680 ?
     C9E05451  (LHIPXSER.NLM|VerifySessions+F1)
  1. -D8045000 ?
  1. D475F41A (THREADS.NLM|ReqFunc+4A)
  1. -01080F00 ?
  1. -00000000 ?
  1. -00000000 ?
  1. -C9E21540 ?
  1. -0000000A ?
     C9E01805  (LHIPXSER.NLM|main+441)
  1. -C9E1B6A8 ?
  1. -C98D9740 ?
  1. -36343834 ?
  1. -00000501 ?
     C9E01054  (LHIPXSER.NLM|_cstart_+0)
     D4752394  (THREADS.NLM|stackavail+34)
  1. -C978DC40 ?
  1. -C98D9740 ?
     D488E39E  (CLIB.NLM|_SetupArgv+2E)
  1. -00000002 ?
  1. -C9E1F044 ?
  1. -00000002 ?
  1. -C9E1F044 ?
     C9E0105E  (LHIPXSER.NLM|_cstart_+A)
     C9E013C4  (LHIPXSER.NLM|main+0)
     D47523AE  (THREADS.NLM|stackavail+4E)
     D473D2A6  (THREADS.NLM|getcmd+21E)
     C9E01054  (LHIPXSER.NLM|_cstart_+0)
  1. -00000000 ?
  1. -00000000 ?
  1. -00004246 ?
  1. -C9E293E0 ?
  1. -00000000 ?
     D473D0E4  (THREADS.NLM|getcmd+5C)
  1. -C8815C80 ?
  1. -00000000 ?
     D473D0DC  (THREADS.NLM|getcmd+54)
  1. -C8815C80 ?
  1. -00000000 ?
  1. -00000000 ?
  1. -00000000 ?
  1. -C9E293E0 ?
  1. D4759720 (THREADS.NLM|(Data Start)+2720)
     FC01F3C2  (SERVER.NLM|TcoNewSystemThreadEntryPoint+26)
  1. -C9E293E0 ?
  1. -00000000 ?
  1. -00000000 ?
  1. -C9E23000 ?
  1. -000081D5 ?
  1. -00000000 ?
  1. -00000000 ?
  1. -2B7A5484 ?
  1. -000080B5 ?
  1. -001B0EE4 ?
     0001F8FB  (LOADER.EXE|kGetProcessorStatus+2CF)
  1. -00000000 ?
  1. -00000000 ?
  1. -00000000 ?
  1. -00000000 ?
  1. -00000000 ?
  1. -00000000 ?
  1. -0394D798 ?
  1. -00000000 ?

Additional Information:

  The CPU encountered a problem executing code in LH.NLM.  The problem may be in that module or in data passed to that module by a process owned by LHIPXSER.NLM.

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/05728a02644ea97d85257068007342ab.txt
  • Last modified: 2023/12/28 07:39
  • by 127.0.0.1