Server crash - NSD analysis

HCL Domino Domino Forum
1

I checked NSD while which is generated during server crash. I have also analysed this NSD using Lotus Notes Diagnostic tool (LND 2.5). This tool has given me highlights as follows:

"Process memory for nhttp (PID:0d70) is near the OS limit.

Check the Stack related infos tab - Process Memory section"

In process memory section following info given,

Page fault count: 11.8M

Virt. Size: 1.9G

Peak Virt Size: 1.9G

Paged pool usage: 40.1M

Peak paged pool usage: 55.7M

Paged pool limit: -1

Non paged pool usage: 3.8M

Peak Non paged pool usage: 5.2M

Non paged pool limit: -1

Page file usage: 281.8K

Peak page file usage: 435.9K

Page file limit: -1

Work set size: 1.6G

Peak work set size: 1.6G

Max. work set size: 1.3M

Handle count: 12960

Kernel time : 1107:50:03

User time Time: 10770:45:50

[Proc Name: Pid] : [ nHTTP: 0d70: 0d70]

Server physical RAM: 3GB

Can anybody suggest me to prevent this server crash?

do i need to workout on memory managment?

do i need to upgrade the server memory which is 3GB(I think, this is sufficient)?

pls suggest.

2

Subject: Server crash - NSD analysis

Hi

Can you post the FATAL THREAD section of the NSD files with the few lines under it

For example:

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

FATAL THREAD 1/2 [ domdsm:107a8:67076]

FP=0x0012a34c, PC=0x60069a86, SP=0x0012a2f0, stksize=92

EAX=0x01a3088c, EBX=0x01a48650, ECX=0x0000bffe, EDX=0x01a325e6

ESI=0x00004000, EDI=0x0032ff78, CS=0x0000001b, SS=0x00000023

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

Exception code: c0000005 (ACCESS_VIOLATION)

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

@[ 1] 0x60069a86 nnotes._fdDelete@4+118 (4000,12a368,608770ef,4000)

@[ 2] 0x60069a0c nnotes._OSFileClose@4+12 (4000,12adc0,12a380,60872ea7)

@[ 3] 0x608770ef nnotes._sqloclose+15 (4000,12b59c,5010,0)

@[ 4] 0x60872ea7 nnotes._sqlpgclf+71 (12adc0,1aaa2cb,70,1aaa2f3)

@[ 5] 0x60885458 nnotes._sqlpgfdl+616 (12b9a4,1aaa2cb,41,12be44)

@[ 6] 0x60876a6f nnotes._sqlpgcdl+927 (12bf44,12b9a4,0,12be44).

Date

Topic

Frequently asked question - How to analyze Notes/Domino NSDs? (Jean-Yves Riverin)

or call IBM support.

JYR

3

Subject: RE: Server crash - NSD analysis

Hi Jean, many thanks for your reply,Please find Fatal thread as below and guide accordingly. meanwhile I will go thru link which u have provided. If you need any more info from NSD, pls get back to me.

Build: 6.5.6

Host Name: MYATSWHQ00PARC1

Date: Fri May 23 12:05:57 2008

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

FATAL THREAD 91/143 [ nhttp: 0d70: 0868]

FP=0x0ec774c4, PC=0x60001422, SP=0x0ec774bc

stkbase=0ec80000, total stksize=262144, used stksize=35652

EAX=0x00000000, EBX=0x00001bff, ECX=0x00000000, EDX=0x7ae92000

ESI=0x7ae92004, EDI=0x7ae92004, CS=0x0000001b, SS=0x00000023

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

Exception code: c0000005 (ACCESS_VIOLATION)

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

@[ 1] 0x60001422 nnotes.Csetmem@12+130 (7ae91ecc,138,0,1c0c)

@[ 2] 0x601e6266 nnotes.FTFDGroupMgr::PopulateGroupEntry+22 (7ae91ecc,ec77540,1bff,465e7fc)

@[ 3] 0x601e5fe8 nnotes.FTFDGroupMgr::AddFDEntry+136 (ec77540,1bff,465e7fc,17faa030)

@[ 4] 0x601e5dee nnotes.FTFDGroupMgr::GetOSFD+110 (ec77540,17faa6b6,1,0)

@[ 5] 0x09923f73 nFTGTR40.CSearchMetaInfo::FTGMetaOpen+67 (99291b4,17faa6b6,17fa8414,ec7876c)

@[ 6] 0x09922653 nFTGTR40.CSearchMetaInfo::CSearchMetaInfo+243 (ec777a8,ffffffff,ec77784,17fa8474)

@[ 7] 0x09921a1c nFTGTR40.CSearchIndexSet::AddLogicalLayerList+76 (ec777a8,1,ec7871c,ec78700)

@[ 8] 0x099214b3 nFTGTR40.CSearchIndexSet::CSearchIndexSet+115 (3231140c,ec7871c,ec7876c,3231140c)

@[ 9] 0x0991fd85 nFTGTR40.CSearch::run+197 (1b56f3a6,400a0c,0,36323928)

@[10] 0x0991fba0 nFTGTR40.FTGSearch@24+592 (51651444,3231140c,30cb,1b56f3a6)

@[11] 0x601d40a4 nnotes.FTSearchExt@60+868 (125,ec78a00,0,1b56f3a6)

@[12] 0x62695d88 nlsxbe.ANDocColl::ANDCExecuteFTSearch+296 (1b56f3a6,30580000,30cb,0)

@[13] 0x6264a3c0 nlsxbe.ANDatabase::ANDFullTextSearch+304 (0,1b56f3a6,30580000,0)

@[14] 0x62653d63 nlsxbe.ANDatabase::LANDFullTextSearch+163 (ec78f98,56f4f748,305807e4,7)

@[15] 0x62643bb7 nlsxbe.ANDatabase::ANDispatchMethod+1335 (ec78f98,ec78f68,1b9c0f2c,ec78f98)

@[16] 0x62642eb2 nlsxbe.ANCLASSCONTROL@16+2050 (19027298,109,ec78f4c,ec78f98)

@[17] 0x626431b9 nlsxbe._tag_NotesADTControl::ClassControl+25 (30580810,19027298,109,ec78f4c)

@[18] 0x60057bc2 nnotes.LSsInstance::AdtCallBack+226 (19027298,626426b0,109,1b9c0f10)

@[19] 0x6006ef4d nnotes.LScObjCli::ProdMethodCall+61 (1b9c0ed0,403,1be71430,10005)

@[20] 0x6006ee44 nnotes.LSsThread::AdtDoProdCallout+164 (1bed2ac8,1b9c0ed0,10005,1be713e4)

@[21] 0x6006ed5f nnotes.LSsThread::AdtCallMethod+47 (6,1be76db4,1,1bed2ac8)

@[22] 0x60023544 nnotes.LSsThread::NRun+6516 (1bed2ac8,0,17fa8314,0)

@[23] 0x60023ce6 nnotes.LSsThread::Run+182 (1bed2ac8,ec790dc,609aba5d,19027298)

@[24] 0x600b31fa nnotes.LSsInstance::Resume+26 (19027298,17fa8314,ec79108,609abaf1)

@[25] 0x609aba5d nnotes.LSIThread::Run+93 (17fa8314,0,1,17fa8314)

@[26] 0x609abaf1 nnotes.LSIThread::RunInternal+65 (ec70002,0,1bed0000,0)

@[27] 0x609abd68 nnotes.LSIThread::RunToCompletion+328 (17fa8314,0,1,60b3806c)

@[28] 0x609a6e98 nnotes.CLSIDocument::RunScript+584 (17f96a14,80d,1,60a479ac)

@[29] 0x605f2b01 nnotes.CRawActionLotusScript::Run+577 (2f8a,17f8bf94,b89,ec793dc)

@[30] 0x605ef246 nnotes.CRawAction::Run+54 (0,17f82c14,b89,ec793f8)

@[31] 0x605eee03 nnotes.CRawAction::Execute+275 (17f8d8f4,2dfe,ec79be0,605eb859)

@[32] 0x605ebb26 nnotes.CAssistant::RunAlone+22 (17f97014,17f82c14,0,17f82c14)

@[33] 0x605eb859 nnotes.CAssistant::Run+3833 (0,ec7a088,13f2a14,ec7b754)

@[34] 0x6060017a nnotes.AgentRun@16+1018 (46969d0,17f8bf94,0,10)

@[35] 0x00492b90 NINOTES.NAgent::Run+320 (0,77e620e0,ec7ce54,ec7bbc0)

@[36] 0x004a9bc3 NINOTES.NDocNote::HandleSaveAgent+691 (ec7bbc4,ec7bbc0,17f94014,ec7ce54)

@[37] 0x004ab5e1 NINOTES.NDocNote::SaveDoc+449 (ec7bbc4,ec7bbc0,13f7814,17f94014)

@[38] 0x004f6c07 NINOTES.CmdHandlerBase::WriteDoc+119 (0,0,17f94014,13f7814)

@[39] 0x004f6345 NINOTES.CmdHandlerBase::HandleOpenFormCmd+645 (1,0,0,17f94014)

@[40] 0x004407dd NINOTES.CmdHandlerBase::PrivHandle+269 (17f94014,0,0,13f7814)

@[41] 0x0043e7ab NINOTES.CmdHandler::PrivHandle+123 (17f94014,16bc4414,77e620e0,17f94014)

@[42] 0x0043e8cd NINOTES.CmdHandler::Handler+221 (17f94014,13f7814,2,0)

@[43] 0x00438a5a NINOTES.Cmd::Execute+58 (54e587a0,54e584b8,0,6825d8)

@[44] 0x0048012e NINOTES.InotesHTTPProcessRequestImpl+1758 (54e587b0,54e587a0,54e584b8,0)

@[45] 0x0047fa1f NINOTES.InotesHTTPProcessRequest+47 (54e587b0,3,55a756ff,55a756fb)

@[46] 0x10014ae4 nhttpstack.HTInotesRequest::ProcessRequest+36 (54e584b8,54e58350,0,0)

@[47] 0x10010a32 nhttpstack.HTRequestExtContainer::ProcessRequest+690 (5,56272818,44533c58,0)

@[48] 0x1001db73 nhttpstack.HTRequest::ProcessRequest+1747 (9444cd4,9444a12,9444ccc,6d6f642f)

@[49] 0x10022512 nhttpstack.HTSession::StartRequest+882 (9444a1e,9444a12,0,ec7ff50)

@[50] 0x1002c309 nhttpstack.HTWorkerThread::CheckForWork+441 (3,9444a12,100292e0,1002930a)

@[51] 0x1002c0f7 nhttpstack.HTWorkerThread::ThreadMain+87 (9444a12,0,0,0)

@[52] 0x60114a44 nnotes.ThreadWrapper@4+212 (0,0,0,0)

[53] 0x77e64829 KERNEL32.GetModuleHandleA+223

Invalid stack frame detected: Unable to read process memory for frame

4

Subject: RE: Server crash - NSD analysis

Hi Jean, I tried to analysed the NSD but still I could not trace the exact cause. can you pls help me to know the cause?Do i need to enable http logging request on the server which will give me thread log while next server crash? or how do I manage process memory, so that http will not exceed memory limit?

Pls help.

Many thanks in Advance