LO74853: SERVER CRASH: LOCKMEMHANDLE() HANDLE 0X0 IS NOT A VALID MEMHANDLE

APAR status

• Closed as program error.

Error description

• Server crashed with the following callstack:
  Thread 28 (Thread 0xeb1c9b70 (LWP 2038)):
  #0 0xf7781430 in __kernel_vsyscall ()
  #1 0x0029db21 in select () from /lib/libc.so.6
  #2 0xf54196f3 in FRDoSleep () from
  /opt/lotus/notes/latest/linux/libnotes.so
  #3 0xf541ab25 in OSRunExternalScript () from
  /opt/lotus/notes/latest/linux/libnotes.so
  #4 0xf541c0f3 in OSFaultCleanupExt () from
  /opt/lotus/notes/latest/linux/libnotes.so
  #5 0xf541c1e0 in OSFaultCleanup () from
  /opt/lotus/notes/latest/linux/libnotes.so
  #6 0xf53e61a7 in fatal_error () from
  /opt/lotus/notes/latest/linux/libnotes.so
  #7 <signal handler called>
  #8 0xf7781430 in __kernel_vsyscall ()
  #9 0xf528a7a0 in raise () from /lib/libpthread.so.0
  #10 0xf54367f7 in Panic () from
  /opt/lotus/notes/latest/linux/libnotes.so
  #11 0xf5400992 in LockMemHandle () from
  /opt/lotus/notes/latest/linux/libnotes.so
  #12 0xf5400fb4 in OSMemoryLock () from
  /opt/lotus/notes/latest/linux/libnotes.so
  #13 0xf5b579d2 in DbAllocAndSetRRV () from
  /opt/lotus/notes/latest/linux/libnotes.so
  #14 0xf5af81de in NoteUpdateImpl () from
  /opt/lotus/notes/latest/linux/libnotes.so
  #15 0xf5b00183 in iNoteUpdate2 () from
  /opt/lotus/notes/latest/linux/libnotes.so
  #16 0xf5ba4bdb in DispatchNoteUpdate () from
  /opt/lotus/notes/latest/linux/libnotes.so
  #17 0xf5ba6108 in NSFNoteUpdateExtended3 () from
  /opt/lotus/notes/latest/linux/libnotes.so
  #18 0xf5ba6896 in NSFNoteUpdateExtendedFlags2 () from
  /opt/lotus/notes/latest/linux/libnotes.so
  #19 0x080bb102 in ServerNoteUpdate ()
  #20 0x080a108d in DbServer ()
  #21 0x080c4786 in WorkThreadTask ()
  #22 0x080704b8 in Scheduler ()
  #23 0xf5411306 in ThreadWrapper () from
  /opt/lotus/notes/latest/linux/libnotes.so
  #24 0xf5282a49 in start_thread () from /lib/libpthread.so.0
  #25 0x002a563e in clone () from /lib/libc.so.6
  
  <@@ ------ Notes Data -> OS Data -> MM/OS Structure Information
  (Time
  00:09:21) ------ @@>
  
   Start Time = 04/08/2013 11:32:35 PM
   Crash Time = 04/09/2013 12:08:44 AM
   Console Log Enabled = 1
   Console Position = 131017
   Error Message = PANIC: ERROR - LockMemHandle() Handle 0x0 is
  not a
  valid MEMHANDLE
  
   Console Position = 131017
   SharedDPoolSize = 8388608
   FaultRecovery = 0x00010012
   Cleanup Script Timeout= 600
   Crash Limits = 3 crashes in 5 minutes
   Core Dump Path =
   StaticHang = Virtual Thread [ server:1050: 73] (Native thread [
  server:1050:3944520560]) (0x41a/0x49/0xeb1c9b70)
   ConfigFileSem = ( SEM:#0:0x010d) n=0, wcnt=-1, Users=-1,
  Owner=[
         : 0]
   FDSem = ( RWSEM:#53:0x410f) rdcnt=-1, refcnt=0 Writer=[
      : 0], n=53, wcnt=-1, Users=0, swCnt=0, ssCnt=0 Owner=[ :
    0]
  

Local fix

• This fix of removing and re-creating the database has resolved
  the issue.
  

Problem summary

• Server Crash: Lockmemhandle() Handle 0x0 Is Not A Valid
   Memhandle
  

Problem conclusion

• Server Crash: Lockmemhandle() Handle 0x0 Is Not A Valid
   Memhandle
  

Temporary fix

Comments

• This APAR is associated with SPR# JCHS96PVF4.
  Server Crash: Lockmemhandle() Handle 0x0 Is Not A Valid
   Memhandle
  

APAR Information

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

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

Fix information

• Fixed component name

  DOMINO SERVER

• Fixed component ID

  5724E6200

Applicable component levels

• R853 PSN

     UP