Domino Windows Service Crash

HCL Domino Domino Forum
1

Recently the lotus domino service in one of our server crashed periodically.

From the nsd file, we found that the service always crashed at the same point when executing “nnotes.LScBuiltIn::FullTrim+494”

May I know what could it be the possible problem causing this?

Please find the error extracted from the nsd below,

Domino Version : Release 8.0.1 (32-bit server)

############################################################

FATAL THREAD 1/15 [ nAMgr: 189c: 0df8]

FP=0x0012e8c8, PC=0x60afd0fe, SP=0x0012e880

stkbase=00130000, total stksize=98304, used stksize=6016

EAX=0x00000000, EBX=0x000000f8, ECX=0x00000000, EDX=0x00000000

ESI=0x76ea9f14, EDI=0x76ea9f20, CS=0x0000001b, SS=0x00000023

DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00210297

Exception code: c0000005 (ACCESS_VIOLATION)

############################################################

@[ 1] 0x60afd0fe nnotes.LScBuiltIn::FullTrim+494 (7ecace2c,af9be0,4089,7ecacaf8)

@[ 2] 0x600dec78 nnotes.LSsThread::OP_BUILTIN+216 (60afcf10,81,1,2)

@[ 3] 0x6002011c nnotes.LSsThread::NRun+204 (7ecacaf8,0,6b0d414,0)

@[ 4] 0x60021ed6 nnotes.LSsThread::Run+182 (7ecacaf8,12e9b4,60ad03c6,af9be0)

@[ 5] 0x600a8d2d nnotes.LSsInstance::Resume+29 (af9be0,6b0d414,12e9e0,60ad0078)

@[ 6] 0x60ad03c6 nnotes.LSIThread::Run+86 (6b0d414,15180,1,6b0d414)

@[ 7] 0x60ad0078 nnotes.LSIThread::RunInternal+72 (120002,15180,2e5692,482578d9)

@[ 8] 0x60ad02ec nnotes.LSIThread::RunToCompletion+332 (6b0d414,15180,1,6b09154)

@[ 9] 0x60acbb7f nnotes.CLSIDocument::RunScript+639 (6b09314,41,1,60baeb45)

@[10] 0x605f23a5 nnotes.CRawActionLotusScript::Run+565 (2a48,6af3994,0,12ee2c)

@[11] 0x605ee88a nnotes.CRawAction::Run+58 (0,12f924,0,12ee58)

@[12] 0x605ef49d nnotes.CRawAction::Execute+221 (6b09234,0,12f62c,605ec816)

@[13] 0x605e77e6 nnotes.CAssistant::RunAlone+22 (6b0a014,12f924,6b0cf14,6b0a014)

@[14] 0x605ec816 nnotes.CAssistant::Run+3590 (6b0a014,12f9a4,12fb70,12fb68)

@[15] 0x631343e3 namgrdll.RunTask@32+2051 (1,58a,0,0,0,0,0,0)

@[16] 0x6313470f namgrdll.ProcessRunMessage@4+63 (12fb68)

@[17] 0x63134791 namgrdll.ProcessMessage@4+33 (12fb68)

@[18] 0x63134955 namgrdll.ExecutiveMain@4+261 (0)

@[19] 0x63139695 namgrdll.AddInMain@12+309 (400000,3,af5414)

@[20] 0x0040102f nAMgr.NotesMain@8+47 (3,400000)

@[21] 0x00401164 nAMgr.notes_main+212 (0,0)

@[22] 0x00401056 nAMgr.main+22 (3,b61fa8)

@[23] 0x0040133d nAMgr.mainCRTStartup+323 (0,0)

[24] 0x77e6f23b kernel32.ProcessIdToSessionId+521 (4011fa,0)

Thank you very much.

2

Subject: May be because of Agent Manager

HiI had seen an IBM document about how to do analysis of NSD file.

We can identify the executable in the failing process by performing a word search for “fatal”.

Your NSD output contains the word “FATAL THREAD 1/15 [ nAMgr: 189c: 0df8]”. This means server is crased due to agent manager task.

i think so.

Because in my case i have faced this situation and after NSD analysis i found the reason for server crash. That was router task.

So based on that, your NSD looks like same and i think it’s Agent manager task which cause the server to crash.

Please find more detail about NSD analysis at below link

Hope it should be helpful to you

Thanks

3

Subject: Thanks… Will try that

Thanks prem C yadav. I will try that out. Thanks a lot.

4

Subject: looks like an agent is crashing it

look in your server log to see what agent is running just before the server crashes.