Several tools are available that you can use to collect general information for troubleshooting purposes. This section provides information about the following troubleshooting tools:
The idsktune command provides information about system parameters, patch level, and tuning recommendations. You can use the output of this command to detect problems in thread libraries or patches that are missing. For more information about the idsktune command, see idsktune(1M)
Run the idsktune command as follows:
The idsktune command is delivered next to the dsee_deploy command with zip distribution software only.
The Solaris pkg_app script packages an executable and all of its shared libraries into one compressed tar file. You provide the process ID of the application and, optionally, the name of the core file to be opened.
You can download this script from http://kaneda.central.sun.com/pkg_app/. This script retrieves the correct version of the binary of the running process or from the core and works with 32 and 64 bit libraries.
The files are stripped of their directory paths, and are stored under a relative directory named /app with their names only, allowing them to be unpacked in one directory. On Solaris 9 and Solaris 10, the list of files output by the pkg_app script is derived from the core file rather than the process image, if it is specified. You must still provide the process ID of the running application to assist in path resolution.
As superuser, run the pkg_app script as follows:
# pkg_app server-pid core-file
You can also run the pkg_app script without a core file. This reduces the size of the pkg_app output. You need to later set the variable to the correct location of the core file.
The dirtracer tool is a shell script that gathers debugging information about a running, hung, or stopped Directory Server process. This information can be used by Sun Support to diagnose a problem. The scripts collects information about the operating system configuration, the Directory Server configuration, and the runtime data elements, as well as log files, databases, cores, gcores, and pstack output. The type of information gathered depends upon the type of problem you are experiencing.
The dirtracer script is available from BigAdmin at http://www.sun.com/bigadmin/scripts/.
As superuser, run the dirtracer script as follows:
#./ dirtracer -f ./dirtracer.config
The dirtracer.config file contains the configuration parameters used by the dirtracer script to generate its output. The dirtracer script comes with a tool to generate this configuration file called the configurator. This interactive shell script automatically creates a configuration file that addresses the type of problem you are experiencing. The configurator set the parameters for log gathering, core collection, as well as many other parameters.