This section describes system administration issues in Oracle Solaris 11.3.
A kernel zone or a zone that is installed from a unified archive might display the following error message when you run the pkg verify command after you log into the zone:
# pkg verify pkg://solaris/system/core-os ERROR: Group: 'root (0)' should be 'sys (3)'
Workaround: To fix the errors reported by the pkg verify command, run the following command:
# pkg fix pkg://solaris/system/core-os
Because the puppet service does not offer a refresh method, whenever you need to apply a new puppet service configuration, you must run the svcadm restart puppet master command.
Workaround: You can eliminate the puppet restart by creating a file under /etc/svc/profile/site with the following content:
<?xml version="1.0" ?> <!DOCTYPE service_bundle SYSTEM '/usr/share/lib/xml/dtd/service_bundle.dtd.1'> <!-- Manifest created by svcbundle (2015-Sep-21 13:27:28-0600) --> <service_bundle type="profile" name="application/puppet"> <service version="1" type="service" name="application/puppet"> <exec_method timeout_seconds="60" type="method" name="refresh" exec=":true"/> </service> </service_bundle>
After you create the file, run the svcadm restart manifest-import command.
To fix security issues, the Squid package has been updated to version 3.5.5. Because the names of some of the helper methods starting with version 3.5.5 have changed, you might have to update the /etc/squid/squid.conf file to use the new names.
Workaround: Run the following command to determine which helper methods are enabled:
Then, make the necessary updates in the /etc/squid/squid.conf file. For information about the helper name changes, refer to http://artfiles.org/squid-cache.org/pub/archive/3.2/squid-22.214.171.124-RELEASENOTES.html#ss2.6.
# svcadm restart svc:/network/http:squid
An attempt to offline a hotplug port with dependent devices that are currently in use by the system might fail with the following error message:
# hotplug poweroff /pci@13c/pci@1/SYS/RCSA/PCIE11 ERROR: devices or resources are busy.
Workaround: Wait for two minutes for the active holds to be released before retrying the hotplug offline command. You must repeat this process until the hotplug offline command succeeds.