illumos through OmniOS

Synopsis

At an unfamiliar OmniOS console, establish which installation is visible before interpreting a service or package listing. Use an ordinary account and a Bourne-style shell. The examples use OmniOS r151060 and its native userland. OmniOS is a distribution built on illumos, which supplies the kernel and core system facilities. OmniOS release notes · OmniOS

Identify the installation and zone

Read the distribution label, the name of the machine, the kernel build, and the current zone.

Shell input
cat /etc/release
uname -n
uname -v
zonename

Record the release identifier beginning with r151 from the first file. The kernel build identifies a different layer. A native zone shares the host kernel. A zone can have its own userland, packages, and services. The name global identifies the global zone. Any other zone name limits the scope of this inventory. In a non-global zone, report the zone name with every finding about the machine. OmniOS zones · OmniOS zonename(1)

The following observations came from two ordinary accounts on the same host.

CheckGlobal zoneNon-global zone
zonenameglobalfieldlab
Release in /etc/releaser151060r151060b

Both sessions returned the same kernel build from uname -v, even though their release files differed. A service query issued in fieldlab describes the instance in that zone.

Locate the source of an installed command

OmniOS manages software with the Image Packaging System (IPS). An image is the installation against which the package client operates. Start with the running image and a familiar executable.

Shell input
pkg list entire
pkg search -l /usr/bin/ls

On r151060, the first query reported version 11-151060.0 for the installed entire package. In the second result, look for a path matching usr/bin/ls and read the package on that row. The example returned pkg:/SUNWcs@0.5.11-151060.0. The option -l restricts the search to installed packages. If the query returns no match, check the spelling and inspect the path with ls -ld /usr/bin/ls. OmniOS pkg(1)

List the publishers configured for this image.

Shell input
pkg publisher

A publisher identifies a source of packages. A configured repository address alone does not identify which package delivered a particular file. Keep the installed package result and the configured source as separate observations. OmniOS IPS repositories

Read a service instance

The Service Management Facility (SMF) tracks named instances of services. A single service can have several instances. The full instance name, called a fault management resource identifier (FMRI), includes the suffix after the final colon. List instances, including disabled ones. Press q to leave the pager.

Shell input
svcs -a | more

Find the Secure Shell (SSH) instance, svc:/network/ssh:default. If it is absent, choose an instance from the listing and replace the value assigned to service below. Keep the same shell for the remaining steps.

Shell input
service=svc:/network/ssh:default
svcs -l "$service"
svcprop -c -p general/enabled "$service"

Read the state and enabled fields. An online state records the service manager’s assessment. A temporary enable or disable can override the persistent setting until reboot. The separate property query reads the configured Boolean value. On the r151060 installation, the SSH instance was online, and the persistent value was true. A running SSH service can still reject a particular connection because of network or authentication policy. OmniOS svcs(1) · OmniOS svcprop(1)

Investigate an unhealthy instance

Ask SMF which services require investigation.

Shell input
svcs -xv

A quiet result means that this diagnostic found no problem to report. If it names an instance, assign that full name to service in the earlier command. Inspect that instance from both directions.

Shell input
svcs -xv "$service"
svcs -d "$service"
svcs -D "$service"
svcs -L "$service"

Lowercase -d lists the instance’s dependencies. Uppercase -D lists its dependents. The last command located the SSH instance log at /var/svc/log/network-ssh:default.log. In the dependency list, the loopback service was online and the optional autofs service was disabled. An optional dependency can be disabled while SSH is online. A required dependency in maintenance, however, can keep its dependent offline. If the log is unreadable, give its path to the administrator responsible for the zone. OmniOS svcs(1)

A report service waiting for input

In a pair of local services on OmniOS r151060, svc:/site/observations-report:default was enabled but offline. Its detail showed a required dependency on svc:/site/observations-source:default, which was in maintenance. The reverse dependency listing for the source confirmed that the report was waiting for it.

The source log at /var/svc/log/site-observations-source:default.log recorded the following entry.

Example log excerpt

Method "start" exited with status 1.

The service diagnostic attributed maintenance to repeated failures of that start method. The next investigation belongs to the source service. Inspect its method configuration and the entries preceding the failure in its log. Restarting the dependent report would leave its required source in maintenance.

Close the first-hour report with the release, host, zone, installed package, service instance, observed state, persistent setting, and next diagnostic step. Continue with service state across systems or file ownership across systems.

UNIX is a registered trademark of The Open Group.