Troubleshooting
Problem
If the Directory Server appears hung, it is important to collect a thread dump in order to identify the reason for the hang condition.
Symptom
Purpose: Gather ibmslapd (or any) processes thread stacks. Usually used when ibmslapd is hung.
| Collecting Thread Dump Options on Windows |
 | Collecting the Thread Dump from a Hung Server |
 | Alternative option for Enabling Memory Dumps |
| Collecting a Thread Dump from a Hung Server |
1. First you need to install some tools.
Install the Windows debugging tools from here ( https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/ ).
2. Set a path to make life easier:
C:\>path=%path%;C:\Program Files\Debugging Tools for Windows
3. The debugger needs some environment variables set:
C:\>set _NT_EXECUTABLE_IMAGE_PATH=C:\Progra~1\IBM\LDAP\bin
C:\>set _NT_SYMBOL_PATH=SRV*C:\progra~1\IBM\ldap\bin*http://msdl.microsoft.com/download/symbols
4. Recreate the hang condition.
C:\>ibmslapd
5. Create a small script file with the debugger commands (makes multiple runs easier):
C:\>notepad DumpStacks.debugscript
Enter this text (2 lines):
~*k
q
Save the file
6. Get the pid of ibmslapd.exe process
C:\>tlist
0 System Process
8 System
136 SMSS.EXE
164 CSRSS.EXE
160 WINLOGON.EXE NetDDE Agent
212 SERVICES.EXE
224 LSASS.EXE
408 svchost.exe
436 spoolsv.exe
468 db2dasrrm.exe
488 db2licd.exe
532 db2sec.exe
544 db2rcmd.exe
576 defwatch.exe
592 svchost.exe
616 ibmdiradm.exe
656 rtvscan.exe Scan
760 regsvc.exe
776 mstask.exe SYSTEM AGENT COM WINDOW
828 VMwareService.e
880 WinMgmt.exe
892 svchost.exe
904 db2jds.exe
196 MSGSYS.EXE
1128 explorer.exe Program Manager
1312 VMwareTray.exe
1324 vptray.exe Norton AntiVirus Corporate Edition
1340 WF_Scheduler.ex
1372 WZQKPICK.EXE About WinZip Quick Pick
1476 CMD.EXE Command Prompt - tlist
448 wuauclt.exe Auto Update Client Window
920 CMD.EXE Command Prompt - ibmslapd
1424 ibmslapd.exe
1124 db2syscs.exe
1044 db2fmp.exe
1552 db2fmp.exe
1564 db2fmp.exe
1008 tlist.exe
7. Run the debugger and save the stack data to file stack.data:
C:\>cdb -pv -p 1424 -cf DumpStacks.debugscript -logo stack.data
Return to top of page
| Alternative Option - Enabling Memory Dumps |
1. Right click My Computer, and then click Properties
2. Click the advanced tab, then click the Startup and Recovery button
3 Click Write Debuging Information, and then click to select Kernel Dump.
4. Reproduce the crash condition
5. Send the memory.dmp file under the directory of \windows after the crash
For detailed information on memory dump file, refer to the following url: http://support.microsoft.com/kb/254649/
Return to top of page
[{"Product":{"code":"SSVJJU","label":"IBM Security Directory Server"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"General","Platform":[{"code":"PF033","label":"Windows"}],"Version":"5.2;6.0;6.1;6.2;6.3;6.3.1;6.4","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
17 January 2019
UID
swg21281915