This section describes system administration bugs in Solaris 10 OS.
The Solaris Volume Manager GUI fails to start successfully. However, no system panic is detected.
Workaround: Remove the following lines from the /var/sadm/smc/toolboxes/smc/smc.tbx file.
<ToolBoxURL> <URL>file:/var/sadm/smc/toolboxes/tsol_files/tsol_files.tbx</URL> </ToolBoxURL> <ToolBoxURL> <URL>file:/var/sadm/smc/toolboxed/tsol_ldap/tsol_ldap.tbx</URL> </ToolBoxURL>
The Solaris Management Console hangs and does not allow root login to the Solaris Management Console after enabling Solaris Trusted Extensions. The following error message might be displayed the Solaris Management Console hangs:
Configuring the Management Server...
Workaround: Perform the following steps:
Configure Solaris Trusted Extensions and start the Solaris Management Console.
Choose Open ToolBox from the Console menu.
Select localhost if it is listed.
If localhost is not listed, then type localhost.
Choose the Policy=TSOL toolbox.
Log in again to the Solaris Management Console as root.
(Optional) If the second login to the Solaris Management Console fails, repeat steps 1 through 5 by typing 127.0.0.1 instead of localhost in step 3.
When you attach a zone, if the original host and the new host have packages at the same patch level but at different intermediate patch histories, the zone attach might fail. Various error messages are displayed. The error message depends on the patch histories of the two hosts.
Workaround: Ensure that the original host and the new host machines have had the same sequence of patch versions applied for each patch.
In systems which have an AHCI compliant SATA controller, the BIOS setup typically enables the controller to be set in either AHCI, legacy, or RAID modes. Solaris supports AHCI and legacy modes.
The SATA mode setting in BIOS must not be changed after an initial Solaris installation. The SATA mode setting must also not be changed before or after a Solaris upgrade. If the SATA mode BIOS setting is modified after installing Solaris, the system will reset and fail to boot without indicating what led to the failure.
Workaround: If boot failure is encountered as a result of changing the BIOS setting, revert back to the original setting in order to boot Solaris.
Starting with patch 119254-42 and 119255-42, the patch installation utilities, patchadd and patchrm, have been modified to change the way that certain patches delivering new features or existing files that are incompatible with the running system are handled. This utilities modification affects the installation of these patches on any Solaris 10 release. These “deferred-activation” patches handle the large scope of change delivered in Kernel patches better.
In deferred Activation patching, a loopback file system, lofs, is used to create a copy of the root file system. The original files being patched are copied to a safe location and the lofs copy of the root file system is patched. Then the original file is lofs mounted back over the new file as it is patched. This means the running system remains consistent over the duration of patching, new features are not active and any incompatible change is hidden until the user reboots.
Users must reboot as soon as possible after applying a Deferred Activation Patch, but they do not have to reboot immediately, they can still add further patches then reboot.
The patch README provides instructions on which patches require a reboot.
Note - Sun strongly recommends that patch operations are carried out in a single-user mode, especially when this is recommended by the patch README.
If you are running non-global zones or have lofs disabled, consider the following points when installing or removing deferred-activation patches:
All non-global zones must be in a halted state for this patch operation. You must halt the non-global zone before applying the patch.
Deferred-activation patching requires the loopback file system, lofs in order to complete successfully. Systems running Sun Cluster 3.1 or Sun Cluster 3.2 are likely to have lofs turned off because of restrictions on HA-NFS functionality when lofs is enabled. Therefore, before a deferred-activation patch is installed, you must re-enable the loopback file system by performing the following steps.
Remove or comment out the following line in the /etc/system file:
Reboot your system.
Install the patch.
After you have completed the patch installation operation, restore or uncomment the same line from the /etc/system file.
Reboot the system to resume normal operations.
No error message is displayed.
Workaround: Sun recommends Solaris Live Upgrade to manage patching. Solaris Live Upgrade prevents the problems of patching a running system. Solaris Live Upgrade reduces the amount of downtime involved in patching and reduces risk by providing fallback capability if problems occur. For more information, see Solaris 10 5/08 Installation Guide: Solaris Live Upgrade and Upgrade Planning.
When run on large file systems, for example ZFS, applications using statvfs(2) or statfs(2) to get information about the state of the file system exhibit an error. The following error message is displayed:
Value too large for defined data type
Workaround: Applications should use statvfs64() instead.
On systems running a Solaris release that is not zones aware, using patchadd -R, or any command that accepts the -R option to specify an alternate root path for a global zone that has non-global zones installed, will not work.
In contrast with the error message that is displayed by using the luupgrade [-t, -T, -p, -P] command, no error message regarding the use of appropriate command-level restrictions is displayed in this instance.
There is no indication that the -R option did not work. As a result of the failure of the command, Solaris 10 packages or patches are not installed on any of the installed non-global zones.
This problem occurs while installing and uninstalling packages or patches.
Note - The -R option works if the alternate boot environment has configured non-global zones, but no installed non-global zones. However, to avoid a potential problem, or if you are not sure whether there are any installed non-global zones used as the alternate root path, restrict the use of the -R option in all instances.
For more information, see the following man pages :
Workaround 1: Upgrade the OS to at least the Solaris 10 1/06 release.
If you are running the Solaris 10 3/05 release, install the following patches to enable the use of commands that accept the -R option to create an alternate root path:
Patch ID 119254-19 for SPARC based systems
Patch ID 119255-19 for x86 based systems
Workaround 2: Restrict the use of the patchadd -R command or any command that accepts the -R option to create an alternate root path.
Instead, boot the alternate root, for example, the Solaris 10 release, as the active OS. Then install and uninstall the Solaris 10 packages and patches without using the -R option.
A system that runs the Sun Patch Manager Tool 2.0 can manage remote systems that run Patch Manager Tool, including Sun Patch Manager Tool 1.0.
However, a system with an earlier version of Patch Manager Tool cannot manage remote systems that run Patch Manager Tool 2.0. Earlier versions include the following:
Sun Patch Manager Base Software 1.x
Sun Patch Manager Tool 1.0
Note - Common Information Model/Web Based Enterprise Management (CIM/WBEM) support for Patch Manager Tool does not exist in the Solaris 8 OS. Consequently, remote management with Patch Manager does not apply to Solaris 8 systems.
If you use the smdiskless command to delete a diskless client, the command fails. The diskless client is not removed from the system databases. The following error message is displayed:
Failing with error EXM_BMS.
Workaround: Unshare the /export partition before adding the client.
If you use the smosservice delete command to remove a diskless client service, the command does not successfully remove all the service directories.
Workaround: Follow these steps.
Make sure that no clients exist that use the service.
# unshare /export/exec/Solaris_10_sparc.all # rm -rf /export/exec/Solaris_10_sparc.all # rm -rf /export/exec/.copyofSolaris_10_sparc.all # rm -rf /export/.copyofSolaris_10 # rm -rf /export/Solaris_10 # rm -rf /export/share # rm -rf /export/root/templates/Solaris_10 # rm -rf /export/root/clone/Solaris_10 # rm -rf /tftpboot/inetboot.sun4u.Solaris_10
Remove the following entry from the /etc/bootparams file.
Note - Remove this entry only if this file server does not provide functions or resources for any other services.
Remove the following entry from the /etc/dfs/dfstab file.
share -F nfs -o ro /export/exec/Solaris_8_sparc.all/usr
Modify the /var/sadm/system/admin/services/Solaris_10 file.
If the file server is not Solaris_10, delete the file.
If the file server is Solaris_10, remove all entries after the first three lines. The deleted lines indicate the service USR_PATH and SPOOLED ROOT packages in /export/root/templates/Solaris_10 and the supported platforms.
After modifying the contents of snmpd.conf, you can issue the command kill -HUP snmp Process ID. This command stops the snmp process. The command then sends a signal to the System Management Agent's master agent (snmpd) to reread snmpd.conf and implement the modifications that you introduced. The command might not always cause the master agent to reread the configuration file. Consequently, using the command might not always activate modifications in the configuration file.
Instead of using kill -HUP, restart the System Management Agent after adding modifications to snmpd.conf. Perform the following steps:
Type the following command:
# /etc/init.d/init.sma restart
You are booting a Sun LX50 which has a Service partition and Solaris 10 OS on x86 is installed. Pressing the F4 function key to boot the Service partition, when given the option, causes the screen to go blank. The system then fails to boot the Service partition.
Workaround: Do not press the F4 key when the BIOS Bootup Screen is displayed. After a time-out period, the Current Disk Partition Information screen is displayed. Select the number in the Part# column that corresponds to type=DIAGNOSTIC. Press the Return key. The system boots the Service partition.
If you choose to use the com.sun application programming interface rather than the javax application programming interface to develop your WBEM software, only Common Information Model (CIM) remote method invocation (RMI) is fully supported. Other protocols, such as XML/HTTP, are not guaranteed to work completely with the com.sun application programming interface.
The following table lists examples of invocations that execute successfully under RMI but fail under XML/HTTP: