APAR status
Closed as fixed if next.
Error description
A domino server has Domino Unified Messaging installed. The server crashes and a nsd is generated. The duc enabled processes in the nsd are not displaying the callstacks correctly. No function calls are being displayed in the callstack for the duc enabled processes: Here is an example: I can see the nnnotes module displays the function call but the process ncsumhlr only displays an address. ############################################################ ### thread 13/19: [ncsumhlr: 1270: 06dc] ### FP=0x0a97f064, PC=0x7d61c846, SP=0x0a97eff8 ### stkbase=0x0a980000, total stksize=32768, used stksize=4104 ############################################################ [ 1] 0x7d61c846 ntdll.ZwWaitForSingleObject+21 (264,ffffffff,0,a97f08c) [ 2] 0x7d4d8c0d kernel32.WaitForSingleObject+18 (264,ffffffff,138ceac,a97f5e4) [ 3] 0x0040ddbb ncsumhlr+56763 (4ae0b0,ffffffff,0,56f) [ 4] 0x00403538 ncsumhlr+13624 (127006dc,0,1db,419a08) [ 5] 0x00402266 ncsumhlr+8806 (138ceac,0,c11c40,c11bc0) [ 6] 0x00407284 ncsumhlr+29316 (0,c11c40,c11bc0,a97ffb8) [ 7] 0x0040c684 ncsumhlr+50820 (c11c40,0,0,c11bc0) [ 8] 0x004103a2 ncsumhlr+66466 (c11bc0,0,0,c11bc0) [ 9] 0x7d4dfe37 kernel32.FlsSetValue+316 (0,0,0,0) ############################################################ ### thread 14/19: [ncsumhlr: 1270: 079c] ### FP=0x0aeba108, PC=0x7d61c846, SP=0x0aeba09c ### stkbase=0x0aec0000, total stksize=32768, used stksize=24420 ############################################################ [ 1] 0x7d61c846 ntdll.ZwWaitForSingleObject+21 (a08,3e8,0,aeba14c) [ 2] 0x7d4d8c0d kernel32.WaitForSingleObject+18 (a08,3e8,363a596f,3e8) @[ 3] 0x600a1166 nnotes.WaitOnNativeSemaphore@16+150 (2be,3e8,3e8,0) @[ 4] 0x600cf699 nnotes.OSWaitEvent@8+105 (363a596f,3e8) @[ 5] 0x60061d52 nnotes.MQGetExtended@36+322 (152ad8,aebc5f8,54c,3e8,0,aeba19c,f10f10,ffffffff,0) @[ 6] 0x60067956 nnotes.MQGet@24+38 (152ad8,aebc5f8,54c,1,0,aeba1c8) [ 7] 0x00402dc1 ncsumhlr+11713 (138d2e0,0,1db,419a08) [ 8] 0x00402266 ncsumhlr+8806 (138d2e0,0,c11b50,c11ad0) [ 9] 0x00407284 ncsumhlr+29316 (0,c11b50,c11ad0,aebffb8) [10] 0x0040c684 ncsumhlr+50820 (c11b50,0,0,c11ad0) [11] 0x004103a2 ncsumhlr+66466 (c11ad0,0,0,c11ad0) [12] 0x7d4dfe37 kernel32.FlsSetValue+316 (0,0,0,0) I suspect the problem is because there is no SYM file for the ncsumhlr module. Here is the symbol table obtained from the nsd: <@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@> Section: Notes Process Info -> SYM Files (Time 12:27:23) <@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@> SymFile Idx SymSrc SYMFSize SysMod ImgTime SymTime ModulePath LotusDomino.sym --- NDMLSYM 11997290 No N/A same awt.dll --- IMAGE 1241088 No 08/20/2009@13:07:29 same C:\Program Files\IBM\Lotus\Domino\jvm\bin\awt.dll j9jit24.pdb --- PDB 3756032 No 07/30/2009@18:03:21 same C:\Program Files\IBM\Lotus\Domino\jvm\bin\j9jit24.dll j9thr24.pdb --- PDB 49152 No 07/30/2009@17:51:18 same C:\Program Files\IBM\Lotus\Domino\jvm\bin\J9THR24.dll j9vm24.pdb --- PDB 368640 No 07/30/2009@18:03:05 same C:\Program Files\IBM\Lotus\Domino\jvm\bin\j9vm24.dll jvm.pdb --- PDB 114688 No 07/30/2009@18:03:18 same C:\Program Files\IBM\Lotus\Domino\jvm\bin\j9vm\jvm.dll jclscar_24.pdb --- PDB 323584 No 07/30/2009@18:03:14 same C:\Program Files\IBM\Lotus\Domino\jvm\bin\jclscar_24.dll LotusDomino.sym 6 NDSYM 11997290 No 09/29/2009@07:37:58 same C:\Program Files\IBM\Lotus\Domino\nAdminP.EXE LotusDomino.sym 11 NDSYM 11997290 No 09/29/2009@07:48:27 same C:\Program Files\IBM\Lotus\Domino\nAMgr.EXE LotusDomino.sym 12 NDSYM 11997290 No 09/29/2009@07:48:27 same C:\Program Files\IBM\Lotus\Domino\namgrdll.dll LotusDomino.sym 19 NDSYM 11997290 No 09/29/2009@07:43:02 same C:\Program Files\IBM\Lotus\Domino\nCalConn.EXE LotusDomino.sym 26 NDSYM 11997290 No 09/29/2009@07:38:05 same C:\Program Files\IBM\Lotus\Domino\nCldbdir.EXE LotusDomino.sym 27 NDSYM 11997290 No 09/29/2009@07:42:59 same C:\Program Files\IBM\Lotus\Domino\nClrepl.EXE LotusDomino.sym 30 NDSYM 11997290 No 09/29/2009@07:38:06 same C:\Program Files\IBM\Lotus\Domino\ncompact.EXE ncsumhlr.exe --- IMAGE 733184 No 09/29/2008@20:37:33 same C:\Program Files\IBM\Lotus\Domino\ncsumhlr.EXE LotusDomino.sym 33 NDSYM 11997290 No 09/29/2009@07:42:17 same C:\Program Files\IBM\Lotus\Domino\nDAOSMgr.EXE LotusDomino.sym 58 NDSYM 11997290 No 09/29/2009@07:39:07 same C:\Program Files\IBM\Lotus\Domino\nevent.EXE LotusDomino.sym 91 NDSYM 11997290 No 09/29/2009@07:41:26 same C:\Program Files\IBM\Lotus\Domino\nlogasio.EXE LotusDomino.sym 99 NDSYM 11997290 No 09/29/2009@07:42:05 same C:\Program Files\IBM\Lotus\Domino\nmtc.EXE LotusDomino.sym 101 NDSYM 11997290 No 09/29/2009@14:04:23 same C:\Program Files\IBM\Lotus\Domino\nnotes.dll LotusDomino.sym 107 NDSYM 11997290 No 09/29/2009@07:42:23 same C:\Program Files\IBM\Lotus\Domino\nNTCP.DLL nprocmon.exe --- IMAGE 57344 No 09/29/2009@07:43:06 same C:\Program Files\IBM\Lotus\Domino\nprocmon.EXE LotusDomino.sym 120 NDSYM 11997290 No 09/29/2009@07:43:00 same C:\Program Files\IBM\Lotus\Domino\nReplica.EXE LotusDomino.sym 121 NDSYM 11997290 No 09/29/2009@07:37:54 same C:\Program Files\IBM\Lotus\Domino\nRouter.EXE LotusDomino.sym 124 NDSYM 11997290 No 09/29/2009@07:43:02 same C:\Program Files\IBM\Lotus\Domino\nSched.EXE LotusDomino.sym 128 NDSYM 11997290 No 09/29/2009@07:43:07 same C:\Program Files\IBM\Lotus\Domino\nSERVER.EXE LotusDomino.sym 129 NDSYM 11997290 No 09/29/2009@07:43:08 same C:\Program Files\IBM\Lotus\Domino\nserverl.dll nservice.exe --- IMAGE 98304 No 09/29/2009@07:43:10 same C:\Program Files\IBM\Lotus\Domino\nservice.exe nucadminp.exe --- IMAGE 139264 No 09/29/2008@20:37:33 same C:\Program Files\IBM\Lotus\Domino\nucadminp.EXE nucevent.exe --- IMAGE 90112 No 09/29/2008@20:37:35 same C:\Program Files\IBM\Lotus\Domino\nucevent.EXE nucextn.dll --- IMAGE 315392 No 09/29/2008@20:37:35 same C:\Program Files\IBM\Lotus\Domino\nucextn.DLL LotusDomino.sym 141 NDSYM 11997290 No 09/29/2009@07:43:15 same C:\Program Files\IBM\Lotus\Domino\nUpdate.EXE mswsock.dll --- IMAGE 524288 Yes 06/20/2008@19:19:47 same C:\WINDOWS\System32\mswsock.dll ntdll.dll --- IMAGE 983040 Yes 02/09/2009@11:02:50 same C:\WINDOWS\system32\ntdll.dll WS2_32.dll --- IMAGE 94208 Yes 02/17/2007@14:02:17 same C:\WINDOWS\system32\WS2_32.dll ADVAPI32.dll --- IMAGE 638976 Yes 07/18/2009@16:58:24 same C:\WINDOWS\syswow64\ADVAPI32.dll kernel32.dll --- IMAGE 1245184 Yes 03/21/2009@17:08:22 same C:\WINDOWS\syswow64\kernel32.dll OLEAUT32.dll --- IMAGE 569344 Yes 12/13/2007@07:49:29 same C:\WINDOWS\syswow64\OLEAUT32.dll USER32.dll --- IMAGE 851968 Yes 03/02/2007@06:38:42 same C:\WINDOWS\syswow64\USER32.dll If I had access to a sym file, I could manuall run the nsd command similar to the syntax below: \nsd -sympath c:\tmp -dumpsym NNOTES!60000000@608CB7E0 to obtain to obtain the function call from ncsumhlr.exe Is this normal expected behavior of the DUC software to NOT display the function calls in the callstack contained in the nsd? Is there a sym file available to manually run the command line noted above to obtain the callstack function calls ? I am unable to thoroughly analyze what the Domino Unified Messaging software is doing at the time the nsd had run because of this problem.
Local fix
Problem summary
The problem will be fixed in the next release of the product.
Problem conclusion
Temporary fix
Comments
This APAR is associated with SPR# LMIL86RKTE. The problem will be fixed in the next release of the product.
APAR Information
APAR number
LO52866
Reported component name
DOMINO SERVER
Reported component ID
5724E6200
Reported release
802
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-06-25
Closed date
2011-01-28
Last modified date
2011-01-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R802 PSN
UP
[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSKTMJ","label":"Lotus Domino"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.2","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
28 January 2011