首页 分析Domino/Notes出错、崩溃、不响应
文章
取消

分析Domino/Notes出错、崩溃、不响应

分析工具

1、控制台调试日记

Stop Consolelog 停止控制台日记

Set Configuration Console_Log_Enabled=1 启用控制台日记,0禁用

2、NSD

服务器-基本-请运行 NSD 以收集诊断信息 启用

3、微软的Procmon监控进程调用注册表、文件的情况

Domino启动不了

使用Procmon.exe监视nserver.exe启动情况,发现注册表HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations里的东西导致的溢出错误,删除该项内容后正常重启

kvoop.exe 為什麼會造成 CPU 使用率到達100% ?
IBM 對於使用這個 kvoop.exe 程式的真正用途並沒有公開說明過,不過,就阿舍找到的一些資料來說,似乎是和 Lotus Domino / Notes 的全文索引功能有關,從 IBM 的支援說明文件可以知道,通常,會發生這個問題是因為資料庫全文檢索的索引量超過 1 G 的容量了,而要解決這個問題的方法不難,只要將現有的索引刪除,然後再重新建立,這樣就可以解決了。

Insufficient memory - too many design elements or
Insufficient memory - too many design elements (desk design pool)
This can be fixed by increasing the size of your desktop cache on Notes.

点击工作台属性 缓存大小设的大一点 删掉工作台上数据库的图标
Notes启动

When launched, Notes.exe does three main things and then calls Nlnotes.exe:
Displays the splash screen
Determines whether Lotus Notes is already running (and aborts, if it is)
Loads Qnc.exe, if you have it configured to do so

Ntaskldr.exe(Notes Task Loader)does not load until a Notes Client task is started.

notes –sa 启动基础版的Notes

Show Stat Platform出现PLATFORM not found in server statistics table

看看是不是禁用了:PLATFORM_STATISTICS_DISABLED=1

启用后如果导致CPU 100% 还是禁用吧

Domino崩溃,控制台显示**** DbMarkCorrupt(NoteOpenExtended: NBNS Checksum mismatch), DB=

运行load fixup -O -I <数据库名>

NSD

Data > IBM_TECHNICAL_SUPPORT directory and starts with “NSD”

搜索 Fatal、 Panic

Domino NSD日记错误1:

############################################################
### thread 6/7: [ nAMgr: 0428: 142c]
### FP=2d02e540, PC=7c95860c, SP=2d02e4d0
### stkbase=2d030000, total stksize=32768, used stksize=6960
############################################################
[ 1] 0x7c95860c ntdll.KiFastSystemCallRet+0 (5d0,927c0,0,2d02eac0)
[ 2] 0x7c821c8d kernel32.WaitForSingleObject+18 (5d0,927c0,3,2d02ecdc)
@[ 3] 0x601a4094 nnotes.OSRunExternalScript@8+1284 (258,1)
@[ 4] 0x601a452a nnotes.FRTerminateWindowsResources+986 (1,0,1000,1)
@[ 5] 0x601a48ef nnotes.OSFaultCleanupExt@24+895 (bf4bd0,1000,0,0,0,2d02f00c)
@[ 6] 0x601a497a nnotes.OSFaultCleanup@12+26 (0,1000,0)
@[ 7] 0x601afbd4 nnotes.OSNTUnhandledExceptionFilter@4+276 (2d02fb38)
[ 8] 0x76238d17 netshell.NetSetupSetProgressCallback+97272 (2d02fb38,7c88b7c0,2d02faf0,7c8361b7)
[ 9] 0x7773d6d2 netman.HrRasConnectionNameFromGuid+37502 (2d02fb38,c0000005,3bd98,0)
[10] 0x7c8361b7 kernel32.RemoveDirectoryA+516 (2d02fb38,0,0,0)
[11] 0x7c34c456 MSVCR71.XcptFilter+351 (0,2d02fb38,7c34246e,2d02fb40)
[12] 0x7c349426 MSVCR71.endthread+193 (39a70,0,0,39a70)
[13] 0x7c82482f kernel32.GetModuleHandleA+223 (0,0,0,0)
INFO (0): Generating core dump for [ nAMgr: 0428] (coreflags=0, exp=19bf29c, dbgver=6.6.0007.5)
INFO (0): Generated core dump file e:Program FilesIBMLotusDominodataIBM_TECHNICAL_SUPPORTcore_nAMgr_W32I_OAMASTERSERVER_2010_07_02@00_05_12.dmp

############################################################
### FATAL THREAD 6/7 [ nAMgr: 0428: 142c]
### FP=0x00000028, PC=0x7efea534, SP=0x2d02ff0c
### stkbase=2d030000, total stksize=32768, used stksize=244
### EAX=0x2cdf9000, EBX=0x001de408, ECX=0x2cdf9000, EDX=0x00000000
### ESI=0x000000a4, EDI=0x2cdf9001, CS=0x0000001b, SS=0x00000023
### DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00010212
Exception code: c0000005 (ACCESS_VIOLATION)
############################################################

解决:

Domino NSD日记错误2:

############################################################
### thread 33/104: [   nHTTP:  103c:  11c4] FATAL THREAD (Panic)
### FP=0x29bc7efc, PC=0x77f88f13, SP=0x29bc7ed8
### stkbase=0x29bd0000, total stksize=262144, used stksize=33064
### EAX=0x4fc80000, EBX=0x29bc7ef4, ECX=0x00001000, EDX=0x00000000
### ESI=0x77f88f08, EDI=0x0000178c, CS=0x0000001b, SS=0x00000023
### DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00000297
############################################################
[ 1] 0x77f88f13 ntdll.ZwWaitForSingleObject+11 (178c,493e0,0,601b4ec5)
[ 2] 0x77e6b40f KERNEL32.WaitForSingleObject+15 (29bc86c8,29bc8ac8,29bc8ae0,0)
@[ 3] 0x601b5aff nnotes.OSRunExternalScript@8+1055 (12c,1)
@[ 4] 0x601b607f nnotes.FRTerminateWindowsResources+975 (1,1010,0,0)
@[ 5] 0x601b64a8 nnotes.OSFaultCleanupExt@24+984 (1246a68,1010,0,0,0,29bc9164)
@[ 6] 0x601b652a nnotes.OSFaultCleanup@12+26 (0,1010,0)
@[ 7] 0x601c1a24 nnotes.OSNTUnhandledExceptionFilter@4+276 (29bca19c)
@[ 8] 0x6018477d nnotes.Panic@4+589 (61e1aca4)
@[ 9] 0x61ce4f36 nlsxbe.ANotes::ANRemoveFromPeerList+118 (4e872f98,4e872f98,4e872f98,29bca228)
@[10] 0x61d5438b nlsxbe.ANViewEntry::~ANViewEntry+171 (4e871cb0,29bca210,61cdfa5d,1)

@[11] 0x61d5501b nlsxbe.ANViewEntry::`scalar deleting destructor'+11 (1,4e871ae8,29bca234,61d1a5ca)
@[12] 0x61cdfa5d nlsxbe.ANotes::ANDeleteList+29 (4e871cb0,0,4e871ae8,4e871ae8)
@[13] 0x61d1a5ca nlsxbe.ANView::~ANView+282 (4e871ae8,29bca268,61ce2c3e,1)
@[14] 0x61d1ef8b nlsxbe.ANView::`scalar deleting destructor'+11 (1,29bc0003,4e871ae8,0)
@[15] 0x61ce2c3e nlsxbe.ANotes::ANDecRefCount+446 (1,29bca704,49d31ee4,0)
@[16] 0x61cc2dbf nlsxbe.ANCLASSCONTROL@16+143 (4dcb79b0,106,29bca6e8,0)
@[17] 0x61cc3879 nlsxbe._tag_NotesADTControl::ClassControl+25 (4e871b14,4dcb79b0,106,29bca6e8)
@[18] 0x6005086d nnotes.LSsInstance::AdtCallBack+269 (4dcb79b0,61cc2d30,106,49d31ec8)
@[19] 0x6005dd0f nnotes.LScObjCli::CallAdtProc+143 (49d31e88,106,0,4e3d2ce0)
@[20] 0x60087a1b nnotes.LScObjCli::DropDead+27 (49d31e88,4e2670a0,29bca7dc,60020aa6)
@[21] 0x60083154 nnotes.LSsThread::DeleteVar+356 (4e3d2ae8,4e3d2ce0,4e2670a0,29bca7e8)
@[22] 0x60020aa6 nnotes.LSsThread::DeleteLocals+198 (4e266ff8,4e3a1e50,4e2618f8,4e3d2ccc)
@[23] 0x6002087e nnotes.LSsThread::ProcLocalTerm+46 (4e3d2ae8,1,2,4e3d2ae8)
@[24] 0x6001e6fe nnotes.LSsThread::NRun+798 (4e3d2ae8,0,29a53218,0)
@[25] 0x60020276 nnotes.LSsThread::Run+182 (4e3d2ae8,29bca8c8,60c34396,4dcb79b0)
@[26] 0x600ade2d nnotes.LSsInstance::Resume+29 (4dcb79b0,29a53218,29bca8f4,60c34048)
@[27] 0x60c34396 nnotes.LSIThread::Run+86 (29a53218,0,1,29a53218)
@[28] 0x60c34048 nnotes.LSIThread::RunInternal+72 (29bc0002,0,0,0)
@[29] 0x60c342bc nnotes.LSIThread::RunToCompletion+332 (29a53218,0,1,29a53298)
@[30] 0x60c2facf nnotes.CLSIDocument::RunScript+639 (29a68b18,6b,1,60d18b41)
@[31] 0x60646b25 nnotes.CRawActionLotusScript::Run+565 (0,29a66b18,3c,29bcad40)
@[32] 0x60642eba nnotes.CRawAction::Run+58 (0,29a91818,3c,29bcad6c)
@[33] 0x60643acd nnotes.CRawAction::Execute+221 (29a443f8,32fd,29bcb538,60640e6a)
@[34] 0x6063bda6 nnotes.CAssistant::RunAlone+22 (29a90018,29a91818,29a90018,29a91818)
@[35] 0x60640e6a nnotes.CAssistant::Run+3658 (0,29bcbdfc,0,29bcd35c)
@[36] 0x6065536b nnotes.AgentRun@16+1291 (29a90018,29a66b18,0,10)
@[37] 0x0049bf50 NINOTES.NAgent::Run+512 (0,29a4e018,78d8018,77e8c354)
@[38] 0x004fbdeb NINOTES.CmdHandler::HandleOpenAgentCmd+459 (29a4e018,0,29a4e018,78d8018)
@[39] 0x0044536e NINOTES.CmdHandlerBase::PrivHandle+302 (29a4e018,0,0,78d8018)
@[40] 0x0044391d NINOTES.CmdHandler::PrivHandle+141 (29a4e018,29a4e018,294ff818,0)
@[41] 0x00444558 NINOTES.CmdHandler::Handler+216 (29a4e018,78d8018,29a4e034,72)
@[42] 0x0043a3ba NINOTES.Cmd::Execute+58 (4d5166d8,4d5163ec,4d516b20,6a6690)
@[43] 0x0048262c NINOTES.InotesHTTPProcessRequestImpl+1932 (4d5166e8,4d5166d8,4d5163ec,4d516b20)
@[44] 0x00484caf NINOTES.InotesHTTPProcessRequest+47 (4d5166e8,3,4c2f3a44,7375746f)
@[45] 0x10017644 nhttpstack.HTInotesRequest::ProcessRequest+36 (4d5163ec,4d516280,0,29bcf98c)
@[46] 0x10011e0d nhttpstack.HTRequestExtContainer::ProcessRequest+941 (5,1,4d23f834,0)
@[47] 0x1002356f nhttpstack.HTRequest::ProcessRequest+1919 (0,23b1e02f,0,5f544c2f)
@[48] 0x10028bac nhttpstack.HTSession::StartRequest+908 (23b1e03b,23b1e02f,0,650)
@[49] 0x100302ff nhttpstack.HTWorkerThread::CheckForWork+399 (1802ee8,23b1e02f,3,1002cc8a)
@[50] 0x10030868 nhttpstack.HTWorkerThread::ThreadMain+88 (23b1e02f,1003f2d0,6f768,0)
@[51] 0x6010dabf nnotes.ThreadWrapper@4+175 (0)
[52] 0x77e6b3bc KERNEL32.lstrcmpiW+183 (6010da10,0,0,dddd04d2)

解决:视图坏了,使用load fixup -f命令修复一下

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

FATAL THREAD 21/66 [   nHTTP:  23fc:  2724]### FP=0x3498ce70, PC=0x60001706, SP=0x3498ce64### stkbase=34990000, total stksize=262144, used stksize=12700### EAX=0x00002724, EBX=0x00002724, ECX=0x00000000, EDX=0x320668a8### ESI=0x00000198, EDI=0x000023fc, CS=0x0000001b, SS=0x00000023### DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00010202Exception code: c0000005 (ACCESS_VIOLATION)

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

@[ 1] 0x60001706 nnotes.OSLockWriteSem@4+22 (198)@[ 2] 0x61cf3e08 nlsxbe.ANNote::ANNAddToCollList+56 (ac1)@[ 3] 0x61d236c7 nlsxbe.ANDocColl::ANDCNavigate+535 (0)@[ 4] 0x61d24598 nlsxbe.Java_lotus_domino_local_DocumentCollection_NgetNextDocument@12+216 (fe31800,335a7160,335a715c)

日记中出现:'LSXBE: Out of backend memory'

解决:Java代码中没使用Recycle清理Java对象

while ( viewentry != null ) {
columnValues = null;
columnValues = viewentry.getColumnValues();
tmp = viewnavigator.getNextDocument();
viewentry.recycle();
viewentry = tmp;}

viewnavigator.recycle();

Fixup crashes Domino 851FP1, FP2 and FP3 with Invalid Pool free Chain
[0E4C:000F-0F5C] -- 16 (0x0010) bytes of 0 --
[0E4C:000F-0F5C] Thread=[0E4C:000F-0F5C]
Stack base=0x0012ED78, Stack size = -968 bytes
PANIC: Invalid pool free chain
'........)...D...'
:cry: 多米诺,爱你不易,恨你又难

NSD分析工具

Lotusphere 2008-HND107-Handout

链接:Troubleshooting Lotus Domino hangs and crashes

Domino crash related to low memory / Windows system resources

FAQ - How to analyze Notes/Domino NSDs?

Fixed causeless server crashes: Some tips for admins

Domino NSD日志诊断/分析

Mapping agent code to crash stacks

'LSXBE: Out of backend memory' errors coincide with Notes/Domino performance and crash issues

Troubleshooting Notes/Domino abnormal terminations on W32

Lotus Notes/Domino发生故障时常用的数据收集步骤

本文由作者按照 CC BY 4.0 进行授权