Server crash in ActLogSession with PANIC: OSVBlockAddr: Bad VBlock handle (0\0).

Technote (troubleshooting)


Problem

server crash

AIX


###### thread 96/131 :: server, pid=1343630, tid=3248213, ptid=11052)
######
###################################
[1] 0xd0124314  _p_nsleep(??, ??) + 0x10
[2] 0xd038d9dc  nsleep(??, ??) + 0xa8
[3] 0xd0441a1c  sleep(??) + 0x58
[4] 0xd2dad7a4  OSRunExternalScript(0x31478570, 0x1) + 0x274
[5] 0xd2dacf1c  OSFaultCleanupExt(0x0, 0x1000, 0x0, 0x0, 0x0, 0x0) +
0x290
[6] 0xd2daea38  OSFaultCleanup(0x0, 0x1000, 0x0) + 0x24
[7] 0xd3ba0e7c  fatal_error(0xb, 0x3147934c, 0x314790c0) + 0x240
[8] <signal>
[9] 0xd0124774  pthread_kill(??, ??) + 0x88
[10] 0xd01241e4  _p_raise(??) + 0x88
[11] 0xd038dd70  raise(??) + 0x2c
[12] 0xd2c5155c  Panic(0x3147a5f0) + 0xd4
[13] 0xd2c51158  OSVBlockAddr(0x30008740, 0x0) + 0x98
[14] 0x1002fb9c  ActLogSession(0x84810a08, 0x10001, 0x0, 0x0, 0x0, 0x0)
+ 0xa0
[15] 0x100222cc  DoSessionMessage(0x84810a08, 0x8b706d44) + 0xca0
[16] 0x10024a2c  ReceiveComplete(0x84810a08, 0x8b706d44) + 0x394
[17] 0x10015d58  DbServer(0x102b9d5, 0xe2a50) + 0xbdc
[18] 0x100adba8  WorkThreadTask(0x36b3b8, 0x0) + 0x924
[19] 0x100c14bc  Scheduler(0x0) + 0x294
[20] 0xd2c577b4  ThreadWrapper(0x0) + 0x10c
[21] 0xd010d780  _pthread_body(??) + 0x118




WINDOWS

############################################################
### thread 5/237: [ nSERVER:  0a1c:  2b88] FATAL THREAD (Panic)
### FP=0x2af4c0c4, PC=0x7d61c846, SP=0x2af4c058
### stkbase=0x2af50000, total stksize=262144, used stksize=16296
### EAX=0x00000000, EBX=0x2af4cc94, ECX=0x00000000, EDX=0x00000000
### ESI=0x00005320, EDI=0x00000000, CS=0x00000023, SS=0x0000002b
### DS=0x0000002b, ES=0x0000002b, FS=0x00000053, GS=0x0000002b
Flags=0x00000206
############################################################
[ 1] 0x7d61c846 ntdll.ZwWaitForSingleObject+21 (5320,16e360,0,2af4c874)
[ 2] 0x7d4d8c0d kernel32.WaitForSingleObject+18
(5320,16e360,2af4d008,2af4ccac)
@[ 3] 0x601b4745 nnotes.FRSendCommandToService+789
(2af4c894,2af4cc94,2af4ccac,5)
@[ 4] 0x601b537f nnotes.OSRunExternalScript@8+1055 (5dc,1)
@[ 5] 0x601b58ff nnotes.FRTerminateWindowsResources+975 (1,1010,1,0)
@[ 6] 0x601b5d28 nnotes.OSFaultCleanupExt@24+984
(1e86a68,1010,0,0,0,2af4d330)
@[ 7] 0x601b5daa nnotes.OSFaultCleanup@12+26 (0,1010,0)
@[ 8] 0x601c1354 nnotes.OSNTUnhandledExceptionFilter@4+276 (2af4e368)
@[ 9] 0x6018352d nnotes.Panic@4+589 (2af4e38c)
@[10] 0x6000432f nnotes.OSVBlockAddr@8+111 (100a58a0,0)
@[11] 0x1001194f nserverl.ActLogSession@24+63
(5236d948,2,0,0,0,2af4e568)
@[12] 0x10012563 nserverl.ActLogOpenSessions@0+243 ()
@[13] 0x10012745 nserverl.ActLogPrimeShift@4+229 (2af4e840)
@[14] 0x1000210c nserverl.OncePerDayStuff@0+220 ()
@[15] 0x10004220 nserverl.OneMinuteStuff@4+256 (3c)
@[16] 0x10004ab2 nserverl.PollTask@8+546 (8c9f00ea,24080001)
@[17] 0x10001a2e nserverl.Scheduler@4+750 (0)
@[18] 0x6010cf1f nnotes.ThreadWrapper@4+175 (0)
[19] 0x7d4dfe37 kernel32.FlsSetValue+316 (0,0,0,0)


Error Message = PANIC: OSVBlockAddr: Bad VBlock handle (0\0)


Symptom

server crashes

Cause

 VarPtr had bActivityInfo block either an initial NULL or it got NULLed out at some point. the block was NULLed out - so it cannot be NULL

Diagnosing the problem

could not reproduce, code review diagnosed the problem

Resolving the problem

has been identified with

SPR # OFFI8CVPQN and apar LO57545

fixed in 8.5.2 FP4, 8.5.3 FP1, 9.0 release

VarPtr->bActivityInfo can become NULLed, so check it */
if (!IsNullVBLOCK(VarPtr->bActivityInfo))
pActivityInfo = ExecBlock(ACTIVITY_INFO, VarPtr->bActivityInfo);
else
return (ERR_SRV_ACTIVITY_INIT_FAILED);


So a check here, solved the crash.


Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Domino
Crash

Software version:

8.5.1, 8.5.2, 8.5.3

Operating system(s):

AIX, Linux, Solaris, Windows, i5/OS

Reference #:

1636111

Modified date:

2013-05-08

Translate my page

Machine Translation

Content navigation