To Collect Required Debug Data For a Crashed Directory Proxy Server Process

This procedure describes what data to collect when a Directory Proxy Server process unexpectedly dies.

1. Try to restart Directory Proxy Server and record the results.

2. Include the test case to reproduce the problem.

3. Collect statistics about the system running Directory Proxy Server.

   Solaris OS

   ps -aux | grep server-root

   vmstat 5 5

   iostat -x

   top

   uptime

   HP-UX

   ps -aux | grep server-root

   vmstat 5 5

   iostat -x

   top

   sar

   Red Hat

   ps -aux | grep server-root

   vmstat 5 5

   top

   uptime

   sar

   Windows

   Get the process ID using the tlist.exe command, then get process details using the same command.

   win-dbg-root\tlist.exe pid

4. Collect swap information.

   Solaris OS

   swap -l

   HP-UX

   swapinfo

   Red Hat

   free

   Windows

   Already provided in C:\report.txt.

5. Collect system logs.

   Solaris OS

   /var/adm/messages

   /var/log/syslog

   HP-UX

   /var/adm/syslog/syslog.log

   Red Hat

   /var/log/messages

   /var/log/syslog

   Windows

   Retrieve the Event log files.

   From the Control Panel, open the Event Viewer. Select the event log. Then select Action > Save log file as to save the log.

6. Collect core files.

   For instructions on preparing your system to produce core files or crash dumps in the event of a crash, see 1.6 Configuring the Operating System to Generate Core Files.

   1. For each core file on Solaris OS, collect output from the following commands.

      cd server-root/bin/dps/server/bin

      file core-file

      pstack core-file

      pmap core-file

      pflags core-file

   2. For at least one of the core files on Solaris OS, collect output from the pkg_app script.

      ./pkg_app.ksh pid core-file

      Here, pid is the server process ID number. See To Run the pkg_app Script for instructions on using pkg_app.