LO38927: NPROCMON PANIC: SERVER PROCESS TERMINATED ABNORMALLY

APAR status

• Closed as unreproducible.

Error description

• NPROCMON crash with error message "PANIC: Server Process
  terminated abnormally"
  The server is exiting with an abnormal status and nprocmon is
  seeing this and
  then forces a panic.
  
  This is the same issue as was tracked in LMAA62ER6U however that
  SPR seems to
  have derailed from the original issue that was reported.
  Also there was no mention of 8.x so I felt it was necessary to
  open a new SPR.
  Also see Ken's comments from LMAA62ER6U:
  
  "08/20/2007 09:49:12 AM: Ken Brunsen /  Changed Regression from
  NULL to Unknown
  General Comments: It would appear that Eric is working an issue
  with a customer
  related to this spr and has distributed code to them. The
  problem is that right
  now this spr seems to be getting used to store any issues
  related to the server
  exiting abnormally and that's not good. I am going to close this
  spr out and in
  the future specific sprs need to be opened for each incident.
  Eric, if a
  customer is having the server exit abnormally then please enter
  a new spr for
  it based on why the server is exiting (the error it returns) and
  also please
  make sure to submit your new procmon code to the pack (enhanced
  debugging code
  is always useful). Thanks"
  
  
  Stack:
  
  ############################################################
  ### thread 1/2: [nprocmon:  1764:  1768] FATAL THREAD (Panic)
  ### FP=0012e128, PC=7c8285ec, SP=0012e0b8
  ### stkbase=00130000, total stksize=20480, used stksize=8008
  ### EAX=0x00000000, EBX=0x00000000, ECX=0x0012d700,
  EDX=0x00000000
  ### ESI=0x00000490, EDI=0x00000000, CS=0x0000001b,
  SS=0x00000023
  ### DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000
  Flags=0x00000297
  ############################################################
   [ 1] 0x7c8285ec ntdll.KiFastSystemCallRet+0
  (490,493e0,0,12e6b0)
   [ 2] 0x77e61c8d kernel32.WaitForSingleObject+18
  (490,493e0,1,12e8cc)
  @[ 3] 0x601a8f34 nnotes.OSRunExternalScript@8+1300 (12c,1)
  @[ 4] 0x601a93ca nnotes.FRTerminateWindowsResources+986
  (1,0,1010,1)
  @[ 5] 0x601a978f nnotes.OSFaultCleanupExt@24+895
  (b34dd8,1010,0,0,0,12ebfc)
  @[ 6] 0x601a981a nnotes.OSFaultCleanup@12+26 (0,1010,0)
  @[ 7] 0x601b4d14 nnotes.OSNTUnhandledExceptionFilter@4+276
  (12fc34)
  @[ 8] 0x60179db8 nnotes.Panic@4+520 (12fc54)
   [ 9] 0x004010e5 nprocmon+4325 (400000,1,400000,0)
   [10] 0x0040112f nprocmon+4399 (2,400000,0,ece)
   [11] 0x00401264 nprocmon+4708 (0,0,0,2)
   [12] 0x00401156 nprocmon+4438 (2,3f2a48,3f2a80,94)
   [13] 0x004014e5 nprocmon+5349 (0,0,7ffde000,0)
   [14] 0x77e6f23b kernel32.ProcessIdToSessionId+521
  (401379,0,78746341,20)
  
  This is what you see at the Domino console:
  
  [1764:0002-1768]  Thread=[1764:0002-1768]
  Stack base=0x0012F178, Stack size = -748 bytes
  PANIC: Server Process terminated abnormally (-1073740972)
  

Local fix

• Enable the parameter PROCESS_MONITOR_DISABLED=1 to disable the
  process monitor
  function.
  

Problem summary

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# CTOI7QFKSL.
  Fixed in 8.0.2 FP2
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• NA
  

Fix information

Applicable component levels

• R802 PSN

     UP