Initial Troubleshooting Steps

The following checks should be done first for almost any package installation problem:

Check which version of the pkg:/entire constraint package is installed. You might need to update the pkg:/entire package.

The following command shows the version of the pkg:/entire package that is installed in this image:
```
$ pkg list -v entire
```
Check your package publisher origin. You might need to add or remove publisher origins.

The following command lists publishers that are configured in this image that are enabled:
```
$ pkg publisher -n
```
Use the --no-network-cache global option to ensure that you are seeing the current content of configured publisher locations and not a cached copy. See the pkg(1) man page for more information.

See Enabling and Disabling Publisher Origins for information about how to see whether particular publisher locations are currently enabled.
Check whether any version-lock facet is set to false. See Relaxing Version Constraints Specified by Constraint Packages for more information.
```
$ pkg facet
```
Check whether any package is frozen at a particular version. See Locking Packages to a Specified Version for more information.
```
$ pkg freeze
```
Check whether an IDR is installed. You might need to reject the IDR. See Installing an IDR Custom Software Update for information about installing superseding IDRs and removing IDRs.

The following command lists any IDRs that are installed:
```
$ pkg list '*idr*'
```
Check whether packages installed from a different publisher might be blocking your update or installation.

The following command lists any packages that are installed from the internalpublisher publisher:
```
$ pkg list -v '*internalpublisher*'
```

Check whether the package you want to install is available from configured publishers and can be installed in this image. The following command shows whether the package you want to install is available from configured publishers. See also Check Available Versions.

$ pkg list -af name-of-package-to-install

When you have determined that the packages you need are available from configured publishers, use the following steps as you proceed with your installation:

Use the -nv options whenever you install or update to see what changes will be made, such as which versions of which packages will be installed or updated and whether a new BE will be created. The -v option also shows any release notes that apply to this particular installation or update operation. See also Preview the Update Operation.
To receive more detailed error messaging, specify more of the FMRI of the package you want to install, including the version and publisher.

If you are updating, the system must have access to a package repository that provides the packages that are currently installed on the system. For example, if you are updating from Oracle Solaris 11.3 to Oracle Solaris 11.4, the solaris publisher must be configured with access to both the installed Oracle Solaris 11.3 packages and the desired Oracle Solaris 11.4 packages. If packages are installed from another publisher, such as ha-cluster or solarisstudio, those publishers also must be configured with access to currently installed packages as well as desired newer packages.

The cause of most update errors is an incomplete package repository. See Best Practices for Creating and Using Local IPS Package Repositories in Creating Package Repositories in Oracle Solaris 11.4.