IBM Support

Server crashed with LockMemHandle() Handle 0x30313132 is not a valid MEMHANDLE

Technote (troubleshooting)


Problem

Server crashed with panic error and crashing thread stack:


Error Message = PANIC: ERROR - LockMemHandle() Handle
0x30313132 is not a valid MEMHANDLE

###################################
thread 190/247::server pid=15204594,k-id=41877619,
pthr-id=48574
stack::k-state=wait,stk max-size=4200584,cur-size=12120
###################################
raise.nsleep(??, ??) at 0x90000000002b544
sleep(??) at 0x900000000142968
OSRunExternalScript(0x140b34460, 0x100000001) at
0x900000003bbd490
OSFaultCleanupExt(0x0, 0x100000001000, 0x0, 0x0, 0x0, 0x0) at
0x900000003bbcc80
OSFaultCleanup(0x0, 0x100000001000, 0x0) at 0x900000003bbe848
fatal_error(0xb0000000b, 0x140b34b50, 0x140b348a0) at
0x9000000043c8e98
pthread_kill(??, ??) at 0x9000000007a56b0
_p_raise(??) at 0x9000000007a4f28
raise.raise(??) at 0x90000000002baac
Panic(0x140b35810) at 0x9000000033e5a14
LockMemHandle(0x3031313230313132, 0x140b359b0, 0x0) at
0x90000000342ab90
OSMemoryUnlock(0x3031313230313132) at 0x90000000342b588
DbDirManGetDBChanges(0x73662c6d61696c2f, 0x627065746572736f,
0x2e6e73662c6d6169, 0x6c2f747361626172, 0x692e6e73662c6d61,
0x696c2f616d63636f, 0x776e2e6e73662c6d, 0x61696c2f63626f72) at
0x9000000037d1a78 @REGS
$r0:0xbadc0ffee0ddf00d $stkp:0x0000000140b33930
$toc:0xbadc0ffee0ddf00d


Windows Crashing Stack:

############################################################
### thread 159/239: [ nSERVER: 2064: 1208] FATAL THREAD (Panic)
### FP=0x3a3d6968, PC=0x77ef047a, SP=0x3a3d6968
### stkbase=0x3a3e0000, total stksize=4194304, used stksize=38552
### EAX=0xF10000000000000, EBX=0x000927c0, ECX=0xF1000E224BFB6A2, EDX=0x0769e000
### ESI=0x00000000, EDI=0x00002658, CS=0xF1000E200000033, SS=0x0000002b
### DS=0x00000000, ES=0x00000000, FS=0xF1000E200000000, GS=0x00000000 Flags=0x00000287
############################################################
[ 1] 0x77ef047a ntdll.ZwWaitForSingleObject+10 (48BE96573327,77d6e344,4,4151f60)
[ 2] 0x77d704ef kernel32.WaitForSingleObjectEx+223 (2658,0,0,0)
@[ 3] 0x004c6b17 nnotes.FRSendCommandToService+1943 (3a3dbfe0,3a3dc2f8,0,4c2e00)
@[ 4] 0x004ca400 nnotes.OSRunExternalScript+5860 (4,0,2746104,3)
@[ 5] 0x004c3c2d nnotes.FRTerminateWindowsResources+2277 (3a3de6bc,3a3de6bc,200,0)
@[ 6] 0x004cd3ca nnotes.OSFaultCleanupExt+622 (0,4c2fc7,150014,274a230)
@[ 7] 0x004cde41 nnotes.OSFaultCleanup+29 (0,0,3a3de010,1674b81)
@[ 8] 0x004e7a4a nnotes.OSNTUnhandledExceptionFilter+626 (3a3df270,272d184,3a3df2e0,4d)
@[ 9] 0x00455dcc nnotes.Panic+856 (1208,27406d0,7868706d,ffffffff)
@[10] 0x00487509 nnotes.OSMemoryUnlock+457 (58380008,9b08c750,2b8,36a9010)
@[11] 0x01a3f296 nnotes.DbDirManGetDBChanges+2850 (9616D2C66736E2E,65796168745C6C,16D2C66736E2E78,37574616D5C6C69)


Resolving the problem

The issue has been reported under SPR VPRS8TWTSE - Prevent a crash associated with passing an invalid database list to NSFGetDBChanges which is fixed in Domino 9.0.1 and 8.5.3 Fix Pack 5.

It is also set to be addressed in 9.0IF5.



Document information

More support for: IBM Domino
Mail Server

Software version: 8.5.2, 8.5.3, 9.0

Operating system(s): AIX

Reference #: 1596387

Modified date: 10 November 2013