Use this task to collect data when a Messaging Server process has stopped (crashed) unexpectedly. Run all the commands on the actual machine where the core file(s) were generated.
Collect the general system information as explained in To Collect Required Debug Data for Any Messaging Server Problem.
Note whether you can you restart Messaging Server.
Get the output of the following commands.
ps -ef | grep server-rootvmstat 5 5iostat -xtopuptime
ps -aux | grep server-rootvmstat 5 5iostat -xtopsar
ps -aux | grep server-rootvmstat 5 5topuptimesar
Obtain the MESSAGING process PID: C:\windbg-root>tlist.exe
Obtain process details of the MESSAGING running process PID: C:\windbg-root>tlist.exe messaging-pid
Get the swap information.
Already provided in C:\report.txt as described in To Collect Required Debug Data for Any Messaging Server Problem.
Get the system logs.
Event log files:Start-> Settings-> Control Panel —> Event Viewer-> Select LogThen click Action-> Save log file as
For UNIX systems, depending on your site's configuration of the SNDOPR_PRIORITY option.dat option and your syslog configuration (syslog.conf), the MTA might be sending automatically generated syslog notices to a pre—determined location. Also, the LOG_SNDOPR option.dat option controls whether additional potential syslog notices are generated by the MTA message logging facility.
Get core files (called “Crash Dumps” by Windows).
See 1.6 Configuring Solaris OS to Generate Core Files if a core file was not generated.
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.
Generate a crash dump during a crash of Messaging Server by using the following commands:
Get the MESSAGING process PID : C:\windbg-root>tlist.exeGenerate a crash dump when the MESSAGING process crashes: C:\windbg-root>adplus.vbs -crash -FullOnFirst -p messaging-pid -o C:\crashdump_dir
The adplus.vbs command watches messaging-pid until it crashes and will generate the dmp file. Provide the complete generated folder under C:\crashdump_dir.
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.
(Solaris OS only) For each core file, provide the output of the following commands.
file corefile pstack corefile pmap corefile pflags corefile
(Solaris OS only) Archive the result of the script pkg_app (one core file is sufficient).
./pkg_app.ksh Pid-of-application corefile
The Sun Support Center must have the output from the pkg_app script to properly analyze the core file(s).