Synopsis
Begin an inventory of an inherited Solaris machine by identifying the release, the current zone, and the software image. Start in an ordinary account with a Bourne-style shell. The procedures in this chapter follow Oracle’s Solaris 11.4 manuals. The troubleshooting case comes from Oracle’s service administration guide.
Distinguish Solaris 11.4 from Solaris 10
Read the release label, the kernel release, and the current zone.
cat /etc/release
uname -r
zonenameUse the product name from /etc/release to select the applicable manuals. A kernel release of 5.11 alone does not identify a Solaris 11.4 update. A zone name other than global identifies a non-global zone. Services and installed software visible there describe that zone. Oracle release identification · Oracle zone identification
On Solaris 11.4, use the Image Packaging System (IPS) to read the version constraint for this image.
pkg list entireRecord the complete version of the installed entire package. The version distinguishes software update levels within 11.4. Release-specific troubleshooting instructions may depend on a particular Support Repository Update (SRU). Oracle’s installed-version guide
On Solaris 10, consult the System V Release 4 (SVR4) package database instead. For example, inspect the record for a particular file.
pkgchk -l -p /usr/bin/lsRead the package names under Referenced by the following packages. Use the Solaris 10 manuals for further package work. The remaining sections describe 11.4. Oracle Solaris 10 package inspection · Oracle’s comparison of packaging commands
Trace an installed file
On Solaris 11.4, find the installed package that delivers a system library. The local search works against the current image.
pkg search -l /lib/libinetutil.so.1Find the row with the exact file path and read its package name. Oracle documents system/library as the provider in its example. If the local result names that package, read its installed version and publisher.
pkg info system/libraryIf the provider differs, substitute the returned package name. If the file is absent from the image, choose a file present there and repeat the local search. A repository search can include versions the machine has never installed. Oracle file-to-package lookup
Follow a service failure to its log
The Service Management Facility (SMF) records each instance’s state and can explain failures. Check for instances that require attention.
svcs -xvWhen the command reports an instance, read the reason and impact. Oracle documents a package depot instance in maintenance: its start method failed. The service log identified an invalid package repository at the configured directory. In that case, the immediate investigation concerns the configured repository path and its contents. Clearing the service alone would leave that condition in place. Oracle’s documented package depot failure
Use the full instance name printed by the local diagnostic. The following assignment selects the depot from the documented case. Substitute a local name if the depot is absent. Inspect the state, dependencies, and log path.
service=svc:/application/pkg/depot:default
svcs -l "$service"
svcs -d "$service"
svcs -L "$service"If the initial diagnostic is quiet, use svcs -a to select an existing service for inspection. Read access to a service log can depend on local permissions. Record the path for the service owner if access is restricted.
Identify the next boot environment
A boot environment is an independently bootable system image. In the global zone, list the environments visible to the account. If access is restricted, request the listing from the administrator responsible for boot environments.
beadm listRead the Active column. N marks the environment in use now, R marks the default for the next boot, and NR marks one environment with both roles. Two different names for N and R mean that the next default boot would select a different image. Record both names before planning maintenance. A non-global zone’s listing concerns its own environments. Obtain the host’s boot selection from the global-zone administrator. Oracle boot environment listing · Oracle administrative rights
For a handoff, record the zone, installed software level, service instance and reason, log path, and boot selection. Compare the observations with illumos through OmniOS or examine persistent service settings.