|Skip Navigation Links|
|Exit Print View|
|System Administration Guide: Advanced Administration Oracle Solaris 10 8/11 Information Library|
This section describes new or changed troubleshooting information in this release.
For information on new or changed troubleshooting features in the Oracle Solaris 10 release, see the following:
For a complete listing of new features and a description of Oracle Solaris releases, see Oracle Solaris 10 8/11 What’s New.
Solaris 10 6/06: The common agent container is a stand-alone Java program that is included in the Oracle Solaris OS. This program implements a container for Java management applications. The common agent container provides a management infrastructure that is designed for Java Management Extensions (JMX) and Java Dynamic Management Kit (Java DMK) based functionality. The software is installed by the SUNWcacaort package and resides in the /usr/lib/cacao directory.
Typically, the container is not visible. However, there are two instances when you might need to interact with the container daemon:
It is possible that another application might attempt to use a network port that is reserved for the common agent container.
In the event that a certificate store is compromised, you might have to regenerate the common agent container certificate keys.
For information about how to troubleshoot these problems, see Troubleshooting Common Agent Container Problems in the Oracle Solaris OS.
Solaris 10 1/06: If a system crash occurs in the GRUB based boot environment, it is possible that the SMF service svc:/system/boot-archive:default might fail when the system is rebooted. If this problem occurs, reboot the system and select the failsafe archive in the GRUB boot menu. Follow the prompts to rebuild the boot archive. After the archive is rebuilt, reboot the system. To continue the boot process, you can use the svcadm command to clear the svc:/system/boot-archive:default service. For more information on GRUB based booting, see Booting an x86 Based System by Using GRUB (Task Map) in System Administration Guide: Basic Administration.
The Oracle Solaris Dynamic Tracing (DTrace) facility is a comprehensive dynamic tracking facility that gives you a new level of observerability into the Solaris kernel and user processes. DTrace helps you understand your system by permitting you to dynamically instrument the OS kernel and user processes to record data that you specify at locations of interest, called, probes. Each probe can be associated with custom programs that are written in the new D programming language. All of DTrace's instrumentation is entirely dynamic and available for use on your production system. For more information, see the dtrace(1M) man page and the Solaris Dynamic Tracing Guide.
kmdb has replaced kadb as the standard “in situ” Solaris kernel debugger.
kmdb brings all the power and flexibility of mdb to live kernel debugging. kmdb supports the following:
Debugger commands (dcmds)
Debugger modules (dmods)
Access to kernel type data
Kernel execution control
For more information, see the kmdb(1) man page. For step-by-step instructions on using kmdb to troubleshoot a system, see How to Boot the System With the Kernel Debugger (kmdb) in System Administration Guide: Basic Administration and How to Boot a System With the Kernel Debugger in the GRUB Boot Environment (kmdb) in System Administration Guide: Basic Administration.