To Collect Debug Data on a Portal Server Crashed Process

Use this task to collect data when a Portal Server process has stopped (crashed) unexpectedly. Run all the commands on the actual machine where the core file(s) were generated.

1. Collect the general system information as explained in To Collect Required Debug Data for Any Portal Server Problem.

2. Get the output of the following commands.

   Solaris OS

   ps -ef | grep server-rootvmstat 5 5iostat -xtopuptime

   HP-UX

   ps -aux | grep server-rootvmstat 5 5iostat -xtopsar

   Linux

   ps -aux | grep server-rootvmstat 5 5topuptimesar

   Windows

   Obtain the PROXY process PID: C:\windbg-root>tlist.exe

   Obtain process details of the PROXY running process PID: C:\windbg-root>tlist.exe proxy-pid

3. Get the swap information.

   Solaris OS

   swap -l

   HP-UX

   swapinfo

   Linux

   free

   Windows

   Already provided in C:\report.txt as described in To Collect Required Debug Data for Any Portal Server Problem.

4. Get the system logs.

   Solaris OS and Linux

   /var/adm/messages/var/log/syslog

   HP-UX

   /var/adm/syslog/syslog.log

   Windows

   Event log files:Start-> Settings-> Control Panel —> Event Viewer-> Select LogThen click Action-> Save log file as

5. Get the the Directory Server Access, Errors, and Audit logs used by Portal Server.

   UNIX and Linux

   server-root/slapd-identifier/logs/accessserver-root/slapd-identifier/logs/errors server-root/slapd-identifier/logs/audit (if enabled)

   Windows

   server-root\slapd-identifier\logs\accessserver-root\slapd-identifier\logs\errors server-root\slapd-identifier\logs\audit (if enabled)

6. Get the Access Manager configuration file.

   UNIX and Linux

   /opt/SUNWam/lib/AMConfig.properties

   Windows

   access-manager-server-root\lib\AMConfig.properties

7. Get the Access Manager log files.

   UNIX and Linux

   /var/opt/SUNWam/*

   Windows

   access-manager-server-root\debug\*

8. Get core files (called “Crash Dumps” by Windows).

   Solaris OS

   See 1.6 Configuring Solaris OS to Generate Core Files if a core file was not generated.

   Linux

   Core dumps are turned off by default in the /etc/profile file. You can make per user changes by editing your ~/.bash_profile file. Look for the following line:

   ulimit -S -c 0 > /dev/null 2>&1

   You can either comment out the entire line to set no limit on the size of the core files or set your own maximum size.

   Windows

   Generate a crash dump during a crash of Portal Server by using the following commands:

   Get the PORTAL process PID : C:\windbg-root>tlist.exeGenerate a crash dump when the PORTAL process crashes: C:\windbg-root>adplus.vbs -crash -FullOnFirst -p portal-pid -o C:\crashdump_dir

   The adplus.vbs command watches portal-pid until it crashes and will generate the dmp file. Provide the complete generated folder under C:\crashdump_dir.

   ---

   Note –

   If you didn't install the Debugging Tools for Windows, you can use the drwtsn32.exe -i command to select Dr. Watson as the default debugger. Use the drwtsn32.exe command, check all options, and choose the path for crash dumps. Then provide the dump and the drwtsn32.log files.

   ---

9. (Solaris OS only) For each core file, provide the output of the following commands.

   file corefile
   pstack corefile
   pmap corefile
   pflags corefile
   

10. (Solaris OS only) Archive the result of the script pkg_app (one core file is sufficient).

    ./pkg_app.ksh Pid-of-application corefile
    

    ---

    Note –

    The Sun Support Center must have the output from the pkg_app script to properly analyze the core file(s).

    ---