The following procedure uses SPARC platform as an example but the steps remain the same for x86 platform as well. Once you have downloaded the 3 packages from my oracle support site, place them in a temporary location. The file can only be edited by the root user. When editing this file, use the command: visudo with no arguments. It is recommended that only this command be used to modify the sudoers file, as this file may not be located in the same directory on all systems.
Oracle Solaris is delivered by a set of packages, with each group of packages constrained by an incorporation. Each incorporation roughly represents the organization that developed each group of packages, though there are some cross-incorporation dependencies within the packages themselves. Dependencies of type incorporate , sometimes with variant. See incorporate Dependency and Mutually Exclusive Software Components for more information about incorporate dependencies and variant.
A license action to ensure that a license is displayed when the incorporation is installed. See License Actions for more information about license actions. Each package delivered on the system contains a require dependency on one of these incorporations. See require Dependency for more information.
Oracle Solaris also includes a special incorporation named entire. The entire incorporation constrains all other incorporations to the same build by including both require and incorporate dependencies on each incorporation package. In this way, the entire incorporation defines a software surface such that all packages are upgraded as a single group.
Examples of reasons an incorporation package might fail to update include the following installation states of an incorporate dependency of the incorporation package:.
The following example attempts to update all installed packages because no package names are specified. Because one package cannot be installed, no packages are installed and the update fails.
Use -v options. For example, use -v or -vv to receive more verbose output. Specify a package to update. Providing more detailed input often results in more detailed messaging. For example, in addition to the name of the package, include the version in the package FMRI.
The following command includes a -v option and specifies to update to the entire 0. This command also specifies the -n option instead of the --be-name option. The -n option shows what will be done but does not actually make any changes to this image.
The -r option looks for this package in the configured package repositories, not in the installed image. To fix this problem, you can instruct the update operation to update all installed packages except for particular specified packages.
Use one or more --reject options in the pkg update command to perform the update without attempting to update the packages specified in the --reject options. Wildcards can be used in --reject arguments. If you receive these error messages, package probably is a core operating system package that must be kept in sync with other core operating system packages. Use the pkg facet command to check the value of the facet. If the value of this version-lock facet is false , use the pkg change-facet command to change the value of this facet to true , and then try the update operation again.
If you receive a message such as the following message that a required package cannot be found, check whether the package is available from your configured publishers.
Use the following command to show whether package2 is available from your configured package publishers:. Use the pkg publisher command to check your publisher origin location. You might need to change your publisher origin location. If the location is a local package repository, you might need to update the repository. In the following output from the pkg update command, the initial error message states that a suitable version of the required package desktop-incorporation cannot be found.
The reason the desktop-incorporation package is not suitable is because one of its dependent packages is not found. Because no suitable version is found, the desktop-incorporation package is rejected.
The next error message states that a suitable version of the required package python-extra cannot be found. The reason the python-extra package is not suitable is because the python-extra package requires the desktop-incorporation package, and no suitable version of desktop-incorporation was found. This information shows that the solution to this update failure is to find a way to install the required version of the desktop-incorporation package.
The following commands show that the package that cannot be found for the required desktop-incorporation package is not required.
The python-sexy package is incorporated by the desktop-incorporation package, but it is not required. The incorporate dependency says that if the python-sexy package is installed, it must be installed at the specified version. However, because no package requires the python-sexy package, the python-sexy package does not need to be installed.
Therefore, one solution to this update failure is to uninstall the python-sexy package. A different version of this package is currently installed, and the update could not locate the version specified by the desktop-incorporation incorporation. If you uninstall the package, the update process will not need to find the updated package. Either use the pkg set-publisher command to add that repository to your publisher origin locations, or use the pkgrecv command to add that package to your currently set publisher origin.
If you use wildcards with an update operation, you might not see any error messages even though some packages that should have been updated were not updated.
You might see an error message if you specify a package name without wildcards. For example, the following operation might complete without error and yet not update any packages, even though you verified that newer packages are available from your configured publishers:. Because the package is frozen, it cannot be updated. See Locking Packages to a Specified Version for more information about the pkg freeze and pkg unfreeze commands. The pkg sync-linked error shown in Sync Linked Package Cannot Be Installed is similar but indicates a package in a non-global zone is preventing the update.
Error message: pkg sync-linked: The installed package package is not permissible. A sync-linked package is a package in a non-global zone. You might see a package rejected with the reason being a version mismatch with the parent image. Core operating system packages must be the same version in non-global zones as in the global zone. You cannot update these packages separately in a non-global zone.
Similarly, freezing any of these packages in a non-global zone causes the update to fail for the global zone and all non-global zones. The following command displays the list of packages that must remain in sync between the global zone and non-global zones:. Error message: The following pattern s did not match any allowable packages.
Try using a different matching pattern, or refreshing publisher information. If the solaris publisher origin in this image is set to a package repository that does not contain the same versions of the system packages that are installed in the global zone, attempting to install a non-global zone results in the following error:. To install a non-global zone, the repository that you set as the solaris publisher origin must contain at least the same system software that is installed in the global zone where you are installing the non-global zone.
The repository can also contain older or newer software, but it must contain the same software that is installed in the global zone. Error message: pkg: The image cannot be modified as it is currently in use by another package client. The error message should include the name and the pid of the client that has the image locked, as shown in the following example:. Try your pkg command again after the current package process exits process in this example.
If the process does not exit quickly, use ptree -a , for example, to begin to examine the process. The package process that is currently operating on this image might be Update Manager checking whether updates are available. The following informational message is followed by the path of the files that were salvaged and the temporary location where the files were moved:.
Directories are reference-counted in IPS. When the last package installed in the image that either explicitly or implicitly references a directory no longer references that directory, that directory is removed. Unpackaged file system objects are files and directories that were not delivered by an IPS package. This directory can get quite large.
Make sure the flush-content-cache-on-success image property value is set to true. The value of the flush-content-cache-on-success property is true by default. When the value of flush-content-cache-on-success is true , cached files are removed when pkg install and pkg update operations complete successfully.
If the flush-content-cache-on-success property is set to false , you can use the command shown in the following example to reset the value to true :. Flushing the content cache setting flush-content-cache-on-success to true can cause some pkg operations to take longer to complete.
You can set the maximum size of this cache with the -s option. Use a local package repository. Exit Print View. Search Scope:. This Document Entire Library. Documentation Home » Oracle Solaris Language: English. Troubleshooting Package Installation and Update This appendix shows how to handle some errors that you might see when you install or update packages. Initial Troubleshooting Steps Check whether the package you want to install is available from configured publishers and can be installed in this image.
Check your package publisher origin. 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.
0コメント