Troubleshooting
Problem
If the ITDS server appears hung or has generated a core file, it is important to collect a thread dump in order to identify the reason for the hang or crash condition.
Resolving The Problem
Purpose: Gather ibmslapd (or any) processes thread stacks. Usually used when ibmslapd is hung.
Requirements: gdb must be installed on the system. You can download gdb (also referred to as wdb on HP) using the following url:
http://h21007.www2.hp.com/portal/site/dspp
Software Downloads -> Featured Downloads -> HP WDB
On HP use the wdb debugger
wdb {program} [ pid | core ] | tee gdb.out
wdb=> thread apply all where
wdb=> quit
{program} is the fully qualified path to the ibmslapd executable.
you must pass either the process ID (pid) or the core parameter.
1) To collect the thread dump from a hung server
1.1) Identify the process ID
To locate the the process ID issue the following command:
ps -ef | grep ibmslapd
1.2) Collect the thread dump
On HP use the wdb debugger
wdb {program} <pid > | tee gdb.out
wdb=> thread apply all where
wdb=> quit
where {program} is the fully qualified path to the ibmslapd executable.
<pid> is the process ID collected in step 1.1
2) To collect the thread dump from a core file
wdb {program} <core> | tee gdb.out
wdb=> thread apply all where
wdb=> quit
where {program} is the fully qualified path to the ibmslapd executable.
<core> is the full path and name of the generated core file.
Core file location:
ITDS v6.x - <instanceLocation>/idsslapd-<instanceName>/workdir
ITDS v5.2 - current workdir where from ibmslapd process is started.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21268414