Solaris 11 has been out on the market for nigh on two years and it's an absolutely brilliant evolution in the history of Solaris, however I've come to notice one common issue that really shouldn't be an issue at all: the number of calls we're getting from people not being able to interpret the failure messages that pkg(1M) produces.
This post aims to explain how to interpret, understand and resolve the most common pkg(1M) errors.
Lets start off with interpreting the basic format of the error. Take the following:
# pkg install compatibility/ucb Creating Plan (Solver setup): - pkg install: No matching version of compatibility/ucb can be installed: Reject: pkg://email@example.com,5.11-0.151.0.1:20101104T230637Z pkg://firstname.lastname@example.org,5.11-0.175.0.0.0.2.1:20111019T053003Z pkg://email@example.com,5.11-0.175.0.10.1.0.0:20120918T160038Z pkg://firstname.lastname@example.org,5.11-0.175.1.0.0.24.2:20120919T184131Z Reason: This version is excluded by installed incorporation pkg://email@example.com,5.11-0.175.1.9.0.5.2:20130704T025151Z #
This is the general format of the most important part of most of the failure messages you get from pkg(1M) and they're actually surprisingly easy to interpret when you know what to look out for.
As a general rule, I look for the very last "Reject" and "Reason" lines, the versions in each and then work backwards from there.
In this example, we can see four different versions of the
compatibility/ucb pkg didn't install because it is excluded by the installed incorporation:
osnet-incorporation. Now the important part of this is the version strings. Note how the version in the "Reason" line is later than the version strings in the lines before. This is the big clue as to why
compatibility/ucb pkg failed to install.
In this case, the
compatibility/ucb pkg failed to install because the system on which we are trying to install the pkg is running Solaris 188.8.131.52.1 (aka Solaris 11.1 w/ SRU 9.5.1). This is later than the revisions offered by the repository the client is referencing and attempting to install the
compatibility/ucb from. In this case, the latest revision the repository is offering is
5.11-0.175.1.0.0.24.2 which corresponds to Solaris 184.108.40.206 or just Solaris 11.1 without any SRUs.
This often isn't a problem, however it is in this case because the
compatibility/ucb was actually updated in the build up to Solaris 220.127.116.11 (aka S11.1 SRU6.4) which introduced a dependency on
firstname.lastname@example.org,5.11-0.175.1.6.0.4.0 or later. As the repository isn't offering any SRUs, this dependency won't be met and the pkg can't be installed.
The solution is to point the client to a repository server that offers the full IPS repository AND at least SRU 9.5.1 (as this is what is installed on the client) or to make the partial SRU 9.5.1 IPS update image accessible to the client alongside the full release repository...
NOTE: the client needs to access BOTH. Failure to do so will cause the error we'll address next.
Of course, the simplest method is to update the client to point to the Oracle support repository at https://pkg.oracle.com/solaris/support (you'll need a certificate and key pair in order to do this) but I understand this isn't always possible. In situations where your clients can't access the public Oracle servers, I highly recommend you create a local repository server - it can be a zone - and point all your clients to this single internal repository server.
Here are 3 more commonly seen pkg(1M) errors, their causes and solutions. I've left these quite short to allow you to interpret the messages yourself to see why the failures have occurred.
pkg update: No solution was found to satisfy constraints latest incorporations: pkg://email@example.com,5.11-0.175.0.10.0.4.0:20120731T142644Z pkg://firstname.lastname@example.org,5.11-0.175.0.10.0.4.0:20120731T141438Z pkg://email@example.com,5.11-0.175.0.11.0.3.0:20120824T161817Z pkg://firstname.lastname@example.org,5.11-0.175.0.11.0.4.1:20120901T011439Z pkg://email@example.com,5.11-0.175.0.11.0.3.0:20120824T161815Z pkg://solaris/consolidation/X/Xfirstname.lastname@example.org,5.11-0.175.0.10.0.2.1231:20120716T221822Z pkg://email@example.com,5.11-0.175.0.11.0.4.0:20120830T143219Z pkg://firstname.lastname@example.org,5.11-0.175.0.11.0.4.0:20120830T142828Z pkg://email@example.com,5.11-0.175.0.11.0.4.1:20120830T142013Z pkg://firstname.lastname@example.org,5.11-0.175.0.11.0.3.0:20120824T162258Z pkg://email@example.com,5.11-0.175.0.11.0.1.108:20120810T173009Z The following indicates why the system cannot update to the latest version: No suitable version of required package pkg://firstname.lastname@example.org,5.11-0.175.0.11.0.4.0:20120830T142828Z found: Reject: pkg://email@example.com,5.11-0.175.0.11.0.4.0:20120830T142828Z Reason: All versions matching 'incorporate' dependency pkg:/firstname.lastname@example.org,5.11-0.175.0.10.0.2.0 are rejected Reject: pkg://email@example.com,5.11-0.175.0.10.0.2.0:20120716T221431Z Reason: A version for 'require' dependency on pkg:/firstname.lastname@example.org,5.11-0.175.0.0.0.2.537 cannot be found
Cause: The IPS repository the client is referring to is incomplete and most likely offering only a partial IPS repository image. This commonly occurs when the repository has been incorrectly configured to only provide the contents of a service repository update (SRU) image or the client is referring directly to the SRU IPS ISO image without access to a full IPS repository. This fails because the SRU IPS images are not complete images; they are partial images.
A client needs to have access to both a complete IPS repository and any SRUs or repositories containing those updates that the client has installed.
Solution: Ensure the repository your client is references contains the full IPS repository image and any service repository updates (SRUs) you have or wish to install onto your clients.
Details on creating a local IPS repository can be found in Copying IPS Package Repositories. The README file supplied with the SRU download and Maintaining Your Local IPS Package Repository contain details on how you update your local repository with the SRU.
The full IPS repository image can be downloaded from http://www.oracle.com/technetwork/server-storage/solaris11/downloads/index.html
# pkg install compatibility/ucb Creating Plan (Solver setup): / pkg install: No matching version of compatibility/ucb can be installed: Reject: pkg://email@example.com,5.11-0.175.1.6.0.3.2:20130322T212735Z Reason: This version is excluded by installed incorporation pkg://firstname.lastname@example.org,5.11-0.175.1.5.0.4.2:20130228T222858Z #
Cause: The pkg you are attempting to install is dependent on a later of a pkg that is not installed.
In this example, the
pkg://email@example.com,5.11-0.175.1.6.0.3.2 pkg can't be installed because it requires
pkg://firstname.lastname@example.org,5.11-0.175.1.6.0.3.2 to be installed first. At the moment
pkg://email@example.com,5.11-0.175.1.5.0.4.2, an older revision, is installed.
This normally happens when a pkg depends on a specific version of another pkg and your repository is offering a later revision than is installed on your system. By default pkg(1M) will always attempt to install the latest revision of a pkg available.
Solution: There are two possible solutions...
pkg install <pkgname>@<version>
pkg install firstname.lastname@example.org
# pkg set-publisher -G http://pkg.oracle.com/solaris/release -g https://pkg.oracle.com/solaris/support solaris pkg set-publisher: The origin URIs for 'solaris' do not appear to point to a valid pkg repository. Please verify the repository's location and the client's network configuration. Additional details: Unable to contact valid package repository Encountered the following error(s): Unable to contact any configured publishers. This is likely a network configuration problem. Framework error: code: 35 reason: error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure URL: 'https://pkg.oracle.com/solaris/support' #
Cause: The client is attempting to access the Oracle support repository (https://pkg.oracle.com/solaris/support) without a valid certificate and key pair.
Solution: You need to obtain a certificate and key pair from https://pkg-register.oracle.com and update your client to utilize the certificate and key pair as per the detailed at https://pkg-register.oracle.com/help/
And that's it for the most common errors at the moment.
Now of course, I've not just sat here and typed this mammoth post out just for the benefit of my readers :-) I've also set the wheels in motion to get these messages changed by logging Bug/RFE 17281770 and writing a knowledge document - Doc ID 1574718.1 (contains most of what is in this post) to try and change things and help customers who need a more formal Oracle document whilst we wait for the changes to happen.
I plan to keep this post and Doc ID 1574718.1 updated as differing pkg(1M) errors increase in frequency.