Contained WithinFind More DocumentationFeatured Support Resources |  Download this book in PDF (521 KB)
Chapter 2 Solaris Runtime IssuesThis chapter describes runtime issues that are known to be problems. Note – Some of the issues and bugs in this chapter have been fixed in subsequent Solaris 10 releases. If you have upgraded your Solaris software, certain issues and bugs in this chapter might no longer apply. To see which bugs and issues no longer apply to your specific Solaris 10 software, refer to Appendix A, Table of Integrated Bug Fixes in the Solaris 10 Operating System. Common Desktop EnvironmentThe following bugs in Solaris 10 OS apply to the Common Desktop Environment (CDE). Trusted Administrative Roles Other Than Root Not Authorized to Connect to the X Window Server (6579866)When an x64 system is configured for Solaris Trusted Extensions, users with administrative roles other than root cannot connect to the X Window server on the console. Applications will fail to start. No error message is displayed. Workaround: Permit TCP connections that are coming from the local host. To permit the TCP connections, create a /etc/X0.hosts file and add a single line with the global zone's host name. Trusted CDE Screen Lock Logs Out the User (6564548)On the Trusted CDE desktop, the screen lock starts correctly but when you unlock the screen, the desktop displays an inaccurate message and then logs you out. The problem does not occur with LDAP name service but only with other name services. The following error message is displayed:
Workaround: Choose one of the following workarounds.
Cannot Switch Roles on Trusted Java DS (6546892)In a multi-label session on the Trusted Java DS desktop, when you select Switch to a different role, the desktop displays an inaccurate message. Also, the role cannot be switched. This bug does not affect the LDAP name service but affects all other name services. The following error message is displayed:
Workaround: Choose one of the following workarounds.
Mouse Pointer and the dtfile Icon Are Not Displayed When You Drag the dtfile Icon (6462945)When you drag the dtfile icon, the icon and the mouse pointer might not be displayed. No error message is displayed. Workaround: Add the following lines to the /usr/dt/config/<locale>/sys.resources file , under #if EXT_SUN_TS OL:
SMC Updates the tnrhdb File But Does Not Run tnctl to Update the Trusted Host Cache (6471594)When the SMC is used to manage network security templates, the /etc/s ecurity/tsol/tnrhdb file is updated but the tndb cache is not updated. Network security definitions do not take effect. No error message is displayed. Workaround: After you modify a network entry in the SMC, manually refresh the tndb cache with one of the following commands:
Trusted Stripe Disappears From The Screen After Resolution Change (6460624)When you type the /usr/X11/bin/xrander -s command to set a smaller screen resolution, Trusted Stripe is no longer displayed. This affects the Trusted CDE Desktop but not the Trusted Java DS Desktop. No error message is displayed. Workaround: After the resolution changes, restart the Workspace Manager. Select windows -> Restart Workspace Manager from the CDE workspace menu and click OK. x86: GNOME Applications Fail With dtremote (6278039)GNOME applications do not start if you log in remotely and enable accessibility in gnome-at-properties. If you attempt to start a GNOME application, the following error message is displayed:
Workaround: None. Do not enable accessibility when you log in by using dtremote. To revert to the default desktop settings in which accessibility is disabled, close the GNOME session. Issue the following command:
x86: kdmconfig Command Does Not Create System Identification Configuration File for Xorg X Server (6217442)If you use the JumpStart installation method, the process might use a system identification configuration (sysidcfg) file. This file is used to generate a specific Xsun configuration file for a system. The Xsun configuration portion of a sysidcfg file is created by the command kdmconfig -d filename. However, on systems that use the default Xorg server, the command does not create a file with any Xorg configuration information. Consequently, you cannot use the JumpStart method on these systems without some additional preparatory steps. Workaround: Before using the JumpStart installation method on a system that uses the Xorg server, perform the following steps.
For instructions about how to perform a custom JumpStart installation, see the Solaris 10 8/07 Installation Guide: Custom JumpStart and Advanced Installations. Chapter 4 includes information about the JumpStart rules file, while Chapter 5 contains a section about finish scripts. CDE Removable Media Auto Run Capability Removed (4634260)The Removable Media auto run capability in the CDE desktop environment has been temporarily removed from the Solaris 10 software. Workaround: To use the auto run function for a CD-ROM or another removable media volume, you must do one of the following:
Solaris PDASync Cannot Delete Last Entry From the Desktop (4260435)After you delete the last item from the desktop, the item is restored from the handheld device to the desktop when you synchronize your handheld device. Examples of items that you might delete, and then have restored, are the last appointment in your Calendar or the last address in the Address Manager. Workaround: Manually delete the last entry from the handheld device prior to synchronization. File SystemsThe following file system bugs apply to the Solaris 10 release. zoneadm install Fails With a ZFS Legacy Mount (6449301)If a non-global zone is initially configured with a ZFS file system to be mounted with the `add fs subcommand and specifies mountpoint=legacy, the subsequent zone installation fails. The following error message is displayed.
Workaround: Add access to a ZFS file system after installing the non-global zone. ZFS and UNIX/POSIX Compliance IssuesZFS is designed to be a POSIX compliant file system and in most situations, ZFS is POSIX compliant. However, two edge case conditions exist when ZFS does not meet the POSIX compliance tests:
Related CRs:
fdisk -E Can Sweep Disk Used by ZFS Without Warning (6412771)If you use the fdisk -E command to modify a disk that is used by a ZFS storage pool, the pool becomes unusable and might cause an I/O failure or system panic. Workaround: Do not use the fdisk command to modify a disk that is used by a ZFS storage pool. If you need to access a disk that is used by a ZFS storage pool, use the format utility. In general, disks that are in use by file systems should not be modified. ZFS and Third-Party Backup Product IssuesThe following are the issues with the Veritas NetBackup and Brightstor ARCserve Backup products. Veritas NetBackup Does Not Back Up and Preserve Files With ZFS/NFSv4 ACLs (6352899)The Veritas NetBackup product can be used to back up ZFS files, and this configuration is supported. However, this product does not currently support backing up or restoring NFSv4-style ACL information from ZFS files. Traditional permission bits and other file attributes are correctly backed up and restored. If a user tries to back up or restore ZFS files, the NFSv4-style ACL information from ZFS files is silently dropped. There is no error message indicating that the ACL information from ZFS files has been dropped. Support for ZFS/NFSv4 ACLs is under development and is expected to be available in the next Veritas NetBackup release. Workaround 1: As of the Solaris 10 8/07 release, both the tar and cpio commands correctly handle ZFS files with NFSv4-style ACLs. Use the tar command with the -p option or the cpiocommand with the -P option to write the ZFS files to a file. Then, use the Veritas NetBackup to back up the tar or cpio archive. Workaround 2: As an alternative to using Veritas NetBackup, use the ZFS send and receive commands to back up ZFS files. These commands correctly handle all attributes of ZFS files. BrightStor ARCserve Backup Client Agent for UNIX (Solaris) and ZFS SupportThe BrightStor ARCserve Backup (BAB) Client Agent for UNIX (Solaris) can be used to backup and restore ZFS files. However, ZFS NFSv4-style ACLs are not preserved during backup. Traditional UNIX file permissions and attributes are preserved. Workaround: If you want to preserve ZFS files with NFSv4-style ACLs, use the tar command with the -p option or the cpio command with the -P option to write the ZFS files to a file. Then, use BAB to backup the tar or cpio archive. ZFS GUI Should Check For /usr/lib/embedded_su at the Beginning of Each Wizard (6326334)If you add the SUNWzfsg package from a Solaris 10 8/07 release to a system that runs a pre-Solaris 10 6/06 release, which does not have the embedded_su patch, the ZFS Administration application wizards are not fully functional. If you attempt to run the ZFS Administration application on a system without the embedded_su patch, you will only be able to browse your ZFS configuration. The following error message is displayed:
Workaround: Add the embedded_su patch (119574-02) to the system that runs a pre-Solaris 10 6/06 release. Fails to Sync File System on Panic (6250422)If a host panics with file system I/O occurring to a target, which is connected by using the Solaris iSCSI software initiator, the I/O might not be able to flush or sync to the target device. This inability to flush or sync might cause file system corruption. No error message is displayed. Workaround: Use the journaling file system like UFS. Starting with Solaris 10, UFS logging is enabled by default. For more information about UFS, see What’s New in File Systems? in System Administration Guide: Devices and File Systems. Upgrading From Some Solaris Express or Solaris 10 Releases Requires Remounting of File SystemsAfter you upgrade an NFSv4 server from 6/05 to Solaris Express 7/05 or later (including all Solaris 10 updates), your programs might encounter EACCES errors. Furthermore, directories might erroneously appear to be empty. To prevent these errors, unmount and then remount the client file systems. In case unmounting fails, you might need to forcibly unmount the file system by using umount -f. Alternatively, you can also reboot the client. NFSv4 Access Control List Functions Might Work IncorrectlyNFSv4 Access Control List (ACL) functions might work improperly if clients and servers in the network are installed with different previous Solaris 10 releases. The affected ACL functions and command-line utilities that use these functions are the following:
For more information about these functions and utilities, see their respective man pages. For example, errors might be observed in a network that includes the following configuration:
The following table illustrates the results of the ACL functions in client-server configurations with different Solaris 10 releases.
Workaround: For the NFSv4 ACL functionality to work properly, perform a full installation of the Solaris 10 OS on both the server and the client. Access Problems Between Solaris NFSv4 Clients and NFSv4 ServersIn the current Solaris 10 version, Solaris implementation of NFSv4 Access Control Lists (ACL) is now compliant with RFC 3530 specifications. However, errors occur for NFSv4 clients that use the Solaris 10 Beta 2 or Beta 1 versions. These clients cannot create files in the NFSv4 servers that are using the current Solaris 10 release. The following error message is displayed:
Workaround: None. Using mkfs Command to Create File System Might Fail on Very Large Disks (6352813)The mkfs command might be unable to create a file system on disks with a certain disk geometry and whose sizes are greater than 8 Gbytes. The derived cylinder group size is too large for the 1-Kbyte fragment. The large size of the cylinder group means that the excess metadata cannot be accommodated in a block. The following error message is displayed:
Workaround: Use the newfs command instead. Or, assign a larger fragment size, such as 4096, when you use the mkfs command. File System Creation Might Fail on Small Slices (6346510)Creating a UFS file system with the newfs command might fail under the following conditions:
The error is caused by the large-size requirement of the file system for metadata. The following warning message is displayed:
Workaround: As superuser, perform one of the following workarounds:
System Crash Dump Fails on Devices Greater Than 1 TByte (6214480)The system cannot generate a dump on a partition that is equal to or greater than 1 Tbyte in size. If such a device is on a system, the following might occur after the system boots subsequent to a system panic:
Workaround: Configure the size of your system's dump device to less than 1 Tbyte. Using smosservice Command to Add OS Services Results in Insufficient Disk Space Message (5073840)If you use the smosservice command to add OS services to a UFS file system, a message that there is insufficient disk space available is displayed. This error is specific to UFS file systems on EFI-labeled disks. Workaround: Complete the following workaround.
Hardware–Related Issue and BugsThe following hardware–related issue and bugs apply to the Solaris 10 release. The (ZFS) ARC Allocates Memory Inside The Kernel Cage Preventing DR (6522017)ZFS can potentially allocate kernel memory across all system boards on systems with very large memory configurations. One free system board is required for dynamic memory reconfiguration so that the memory from the board to be dynamically reconfigured can be copied to the free board. The dynamic memory reconfiguration means that you cannot dynamically reconfigure memory on systems with very large memory configurations that have ZFS running. High-end SunFireTM servers can relocate kernel pages so that this issue is avoided. These servers must have kernel page relocation (KPR) enabled for domains with more than 32 cores. No error message is displayed Workaround: Reduce the amount of kernel memory that ZFS can allocate by setting the zfs_arc_max parameter in the /etc/system file. The following example sets the maximum size to 512 Mbytes.
mpathadm Does Not Display Load-Balance Setting Specific to DeviceThe mpathadm show logical-unit subcommand lists the load balancing global configuration value for the Current Load Balance property. However, entries in the csi_vhci.conf that change the load-balance type for a specific product are not reflected in the mpathadm output even when the setting is active. Registration Tool Prevents Power Management on Some Framebuffers (6321362)If the background processes for the registration tool are left running, the Elite3D and Creator3D framebuffers stop power management. This failure reduces the power savings when the system is in a power-managed state. Under certain conditions, sys-suspend might also hang. No error message is displayed. The system might hang during a system suspend or resume operation. Workaround: Run the following command approximately 60 seconds after each login:
SPARC: Sun Crypto Accelerator 4000 Board Versions 1.0 and 1.1 Not Supported in Solaris 10 OSA new cryptographic framework is provided in Solaris 10 OS. However, versions 1.0 and 1.1 of the Sun Crypto Accelerator 4000 board's software and firmware do not utilize this framework. Consequently, these versions are not supported in the Solaris 10 OS. The 2.0 release uses the new framework. This release is available as a free upgrade to current Sun Crypto Accelerator 4000 users who plan to use Solaris 10 OS. Because the Sun Crypto Accelerator 4000 is an export-controlled product, you must contact Sun Enterprise Services or your local sales channel to obtain the free upgrade. Additional information is available on the Sun Crypto Accelerator 4000 web page at Sun's products site. Certain USB 2.0 Controllers Are DisabledSupport for certain USB 2.0 controllers has been disabled because of incompatibilities between these devices and the EHCI driver. The following message is displayed:
For the latest information about USB devices, see http://www.sun.com/io_technologies/USB-Faq.html. Supported USB Devices and Corresponding Hub ConfigurationsThis Solaris release supports both USB 1.1 and USB 2.0 devices. The following table is a summary of USB devices that work in specific configurations. Connection types can either be direct to the computer or through a USB hub. Note that USB 1.1 devices and hubs are low speed or full speed. USB 2.0 devices and hubs are high speed. For details about ports and speeds of operation, see the System Administration Guide: Devices and File Systems. Table 2–1 USB Devices and Configurations
x86: Limitations Exist With Certain Device Drivers in Solaris 10 OSThe following list describes limitations with certain drivers and interfaces in this release of Solaris 10 for x86 platforms:
DVD-ROM/CD-ROM Drives on Headless SystemsPower management of interactive devices such as removable media is linked with power management of your monitor and the graphics card that drives your monitor. If your screen is active, devices such as the CD-ROM drive and diskette remain at full-power mode. These devices might switch to low-power mode on a system without a monitor. To restore power to the CD or diskette, type volcheck to obtain the latest status from each removable device. Alternatively, you can disable power management on your system by using the Dtpower GUI. By disabling power management, these devices are constantly at full power. x86: Manual Configuration Required to Specify Non-US English KeyboardsBy default, the kdmconfig program specifies Generic US-English(104-Key) as the keyboard type that is connected to the system. If the system's keyboard is not a US-English keyboard, you must manually specify the keyboard type during installation. Otherwise, installation continues by using the default keyboard specification that is inconsistent with the system's actual keyboard type. Workaround 1: If the system's keyboard is not a US-English keyboard, perform the following steps during installation:
Workaround 2: If you want to change the keyboard type in a system that is already running Solaris 10 OS, use the kdmconfig program. Choose the option that applies to the type of X server your system is running.
SPARC: jfca Driver for Certain Host Bus Adapters That Are Connected to Tape Devices Might Cause Errors (6210240)The jfca driver for the following host bus adapters (HBAs) might cause system panics or I/O failures when these HBAs are connected to tape devices:
The jfca driver for these HBAs is prone to race conditions when certain operations are being run, and thus causes the errors. The operations are the following:
Error messages similar to the following examples might be displayed:
Workaround: Do not connect tape devices to either the SG-PCI1FC-JF2 or SG-PCI2FC-JF2 HBA. Contention Exists Between Certain Devices That Share the Same Bus (6196994)A bus contention occurs if Quad Fast-Ethernet (QFE) cards share the same bus with any of the following adapters:
The infinite-burst parameter of the ce driver that is used by these adapters is enabled by default. Consequently, little or no bus time is available for the QFE ports that share the same bus. Workaround: Do not place QFE cards on the same bus as the network adapters in the list. hat_getkpfnum() DDI Function Is Obsolete (5046984)The hat_getkpfnum() DDI function is obsolete. Developers should update their device drivers to not use the hat_getkpfnum() DDI interface. If drivers are using hat_getkpfnum,() warnings similar to the following example are displayed:
To determine if a driver is using hat_getkpfnum(), consult the driver source code, or examine the driver's symbols by using nm(). Using the driver mydrv as an example, type the following syntax:
For guidance about migrating drivers away from hat_getkpfnum(), refer to Appendix B, Summary of Solaris DDI/DKI Services, in Writing Device Drivers. x86: Soft System-Shutdown is Not Supported in Solaris OS on x86 (4873161, 5043369)The Solaris OS on x86 does not support a soft system-shutdown that is initiated by a command. A command to shut down simulates pressing the power button to turn the power off. On x86-based systems, issuing this command while the Solaris OS is running turns the power off immediately without properly shutting down the operating system. The improper shutdown process might corrupt the file system. Workaround: Before powering off, shut down the operating system first. Perform the following steps:
For more information about the commands to shut down the operating system, see the man pages for the init(1M), halt(1M), and shutdown(1M) commands. For information about turning off your system's power, refer to the system's manuals. Some DVD and CD-ROM Drives Fail to Boot Solaris (4397457)The default timeout value for the SCSI portion of the SunSwiftTM PCI Ethernet/SCSI host adapter (X1032A) card does not meet the timeout requirements of Sun's SCSI DVD-ROM drive (X6168A). With marginal media, the DVD-ROM occasionally experiences timeout errors. The only exceptions are Sun Fire 6800, 4810, 4800, and 3800 systems. These systems overwrite the SCSI timeout value by means of OpenBoot PROM. Workaround: For other platforms, use the on-board SCSI interfaces or DVD-ROM compatible SCSI adapters, such as the following examples:
iPlanet Directory Server 5.1 IssuesThis section provides important information for users of iPlanetTM Directory Server 5.1 who are upgrading to the new Solaris 10 release. Installing Directory Server 5.1Sun Java System Directory Server 5 2005Q1 replaces iPlanet Directory Server 5.1 that was integrated in the Solaris 9 Operating System. In Solaris 10 OS, this new Directory Server can be installed as part of the Sun Java Enterprise System. Note – For information about the Sun Java System Directory Server 5 2005Q1, refer to the documentation for the Sun Java System at http://docs.sun.com. Solaris 10 OS continues to support Directory Server 5.1. You might need to install Directory Server 5.1 under the following circumstances:
In Solaris 10 release, you install the Directory Server 5.1 manually. Follow these steps:
Migrating to the Sun Java System Directory Server 5 2005Q1 Caution – The database formats of the two Directory Server versions are incompatible. Thus, if you are a Directory Server 5.1 user, Sun recommends that you migrate your database to a database that is formatted for the Sun Java System Directory Server 5 2005Q1. To perform a migration, both versions of the Directory Server must exist in the system that has been upgraded to the Solaris 10 OS. If you are a DS 5.1 user, but are using the compressed archive (.tar.gz) delivery format, you can skip immediately to the migration instructions in Step 2.
After migrating your data, make sure you continue to back up directory data in the same way as you backed up directory data before migration. Future disaster recovery might require the migrated database. Issues While Running DebuggerThe following issues involve the kernel debugger. SPARC: Problems With dbx Debugger While Processing 64-bit Objects (6347707)The dbx debugger terminates with a memory access failure while processing certain 64-bit executable files and libraries. However, the problem does not affect the normal use of these 64-bit objects. An error message similar to the following example is displayed:
Workaround: Use either the mdb debugger or the Solaris Dynamic Tracing facility instead. These alternatives can diagnose processes that use the 64-bit objects. System Might Loop When Master CPU Is Changed (4405263)A system that is running the Solaris kernel debugger to debug a live system might loop with incomplete error messages. This loop occurs when the OpenBoot PROM's master CPU is changed. A system reset restores the system to operation. However, the traces of the original failure are lost. Consequently, you cannot perform a diagnosis of the fatal reset. Workaround: When the system is at the PROM level, the OpenBoot's ok prompt is displayed. In a system with multiple CPUs, the ok prompt is preceded by a number that is enclosed in curly braces. This number indicates the active CPU in the system. To run your debug session while at the PROM level, use the following steps.
Note – Make sure that you upgrade the system to the latest version of the OpenBoot PROM. Localization IssuesThis section describes localization issues that apply to Solaris 10 OS. Multiple Input Method Switcher Applications Appear in Trusted Java DSWhen you log in to the Trusted Java DS with UTF-8 or Asian locales, the Input Method Switcher application, iiim-panel, appears per label by default. Thus in multiple label environment, multiple iiim-panel appears, which could be confusing to the user. No error message is displayed. Workaround: Stop using the iiim-panel. Perform the following steps:
Note – When Attach to each application is selected, language switcher list will not be displayed for GTK applications. You can switch input language through non-GTK applications or by running GTK applications with X Input Method instead of IIIM. For example:
Wnn8 Japanese Input MethodWnn8 Japanese Input method cannot be used if the Wnn8 servers are not enabled. Workaround: Enable the Wnn8 servers:
In addition, select Wnn8 as the Japanese Language engine by running the iiim-properties command. Uninstaller Displays Strings Incorrectly in Some Locales (6487062)This bugs affects how you uninstall Solaris Trusted Extensions by using prodreg in locales other than C, POSIX, or any English locale. Strings are not displayed correctly in these locales when you uninstall by using prodreg. No error message is displayed. The uninstaller shows placeholder strings, and buttons do not display correctly. Workaround: Before you uninstall with prodreg, run the following commands:
Then uninstall with prodreg. Input Method Cannot Be Enabled With Primary Administrator Rights (6475081)A user who has the Primary Administrator right can not use the input method for specific locales which prevents that user from entering characters normally. The input method status is not displayed in the workspace. No error message is displayed. Workaround: Add the following lines to the /etc/security/exec_attr file:
For information about the file format, see the exec_attr(4) man page. New ChuYin Input Method Not Supported in Upgrade to IIIMF rev.12 (6492129)When you upgrade the OS to the Solaris 10 6/06 or Solaris 10 11/06 release, the input method framework and individual input methods get upgraded from rev.10 to rev.12. However, ChuYin is not in the list of supported input methods. Also, you cannot use the function keys F2 and F3 to switch methods Workaround: Use PinYin to type traditional Chinese characters with Hanyu PinYin. Use Ctrl+Shift to switch input methods. AltGr Does Not Work As Mode Switcher in Some Russian Locales (6487712)The AltGr key does not work as a mode switcher for the Russian Xsun layout inru_RU.KOI8-R and ru_RU.ANSI1251 locales. Workaround 1: Switch to the ru_RU.UTF-8 or the ru_RU.ISO8859-5 locale. Workaround 2: Use IIIMFTM instead of the Russian keyboard layout. Arabic Text Not Appearing in ar LocalesIf your x86 system is using Xorg as the default Xserver, the Arabic font (iso7759-6) does not appear in the ar locale. This error does not occur if you are using XSun instead of XOrg. Workaround: Follow these steps.
Alternatively, you can log in to ar_EG.UTF-8 or other UTF-8 locales. Solaris PDASync Does Not Support Data Exchange With the Multibyte Internationalized PDA Device (4263814)If you exchange multibyte data between a PDA device and Solaris CDE, the data might be corrupted in both environments. Workaround: Back up your data on your personal computer with the PDA backup utility before you run the Solaris PDASync application. If you accidentally exchange multibyte data and corrupt that data, restore your data from the backup. L10N Messages Missing When Using localeadm Utility to Add Locales (6423974)When the Locale_config configuration file is created using the DVD/net image, using the Locale_config file to add locales leaves many unlocalized messages on the Gnome Desktop. No error message is displayed. Workaround 1:
Login as superuser and do the following: Workaround 2: Re-create the Locale_config file by using the CD images. Several Arabic Fonts Do Not Work in GNOME (6384024)In GNOME when you select certain Arabic fonts, the characters do not display. This problem appears when you select fonts for applications, the desktop, or the window title using the GNOME font properties menu. The affected fonts include:
No error message is displayed. Workaround: Use any of the newly delivered Kacst family of fonts to display Arabic characters in GNOME applications. Unable to Switch Input Language on Session-Saved Applications (6360759)Multiple language input is supported in UTF-8 locales, but the language switch is not working with session-saved applications where mouse button 1 is clicked first after login. This problem occurs with the Java Desktop System (Java DS). No error message is displayed. Workaround: Click mouse button 1 on the background workspace or Launch Menu before clicking any application. Keyboard Shortcuts in Mozilla in ES Locale Are Unusual and Ambiguous (6288620)The keyboard shortcuts in Mozilla 1.7 are unusual, especially in Spanish locale. For example, Ctrl-S is being used for copying as well as for saving. No error message is displayed. Workaround: Identify the shortcut keys assigned to user actions from menu in the product. Migration Note to UTF-8 localesWhen migrating to UTF-8 locales, the files affect the method that you use to import or export data. Microsoft Office FilesMicrosoft Office files are encoded in Unicode. StarOffice applications can read and write the Unicode encoded files. HTML FilesHTML files authored using HTML editors such as Mozilla Composer, or HTML files saved by a web browser, usually contain a charset encoding tag. After exporting or importing, you can browse such HTML files with the Mozilla Navigator web browser, or edit the files with Mozilla Composer, according to the encoding tag in the HTML file. Fixing Broken HTML FileSome HTML files might be displayed in garbage characters. This problem is typically due to the following reasons:
To find the charset encoding tag in the HTML file, perform the following actions:
The charset information is in the bottom of the General tab, for example:
If the string charset=us-ascii does not match the actual encoding of the file, the file might appear broken. To edit the encodings of the HTML file, perform the following actions:
Emails Saved As Portable FormatModern mails are tagged with the MIME charset tag. The Email and Calendar application accepts MIME charset tags. You do not need to perform any encoding conversion. Plain Text FilesPlain text files do not have a charset tag. If the files are not in UTF-8 encoding, encoding conversion is needed. For example, to convert a plain text file encoded in Traditional Chinese big5 to UTF-8, execute the following command:
You can also use the File System Examiner for the encoding conversion. You can use the Text Editor to read and write character encoding text automatically or by specifying an encoding explicitly when opening or saving a file. To start Text Editor, click Launch, then choose Applications->Accessories->Text Editor. File Names and Directory NamesIf file names and directory names using multibyte characters are not in UTF-8 encoding, encoding conversion is needed. You can use File System Examiner to convert file and directory names and the contents of plain text files from legacy character encodings to UTF-8 encoding. Refer to the online Help for File System Examiner for more information. To start File Systems Examiner, click Launch, then choose Applications->Utilities->File System Examiner. When you access non-UTF-8 file or directory names on Microsoft Windows via SMB using File Manager, you can access the non-UTF-8 file or directory names without encoding conversion. Launching Legacy Locale ApplicationsFor applications that are not ready to migrate to Unicode UTF-8, you can create a launcher on a front panel to start the application in legacy locales. You can also launch the applications directly from the command line. Perform the following steps to create a launcher for an application.
When you need to run CLI (command line interface) applications which are specific to a legacy locale, open a Terminal window in the legacy locale first and then run the CLI applications in the same Terminal window. To open a Terminal window in a legacy locale, enter the following command:
Instead of opening a new Terminal window in a legacy locale, you can switch the locale setting from UTF-8 to a legacy locale in the current Terminal window by changing the encoding the Set Character Encoding menu in the Terminal window. Then you must also set the LANG and LANG environment variables to the current shell. Hardware for Estonian Keyboard Type 6, French Canadian Keyboard Type 6, and Polish Programmers Keyboard Type 5 Not AvailableSoftware support for three additional keyboard layouts has been added to the Solaris OS: Estonian keyboard Type 6, French Canadian keyboard Type 6, and Polish programmers keyboard Type 5. This software gives users in Estonia, Canada, and Poland greater flexibility for keyboard input by modifying standard U.S. keyboard layouts to their own language needs. Currently, no hardware is available for the three additional keyboard layout types. Workaround: To take advantage of this new keyboard software, modify the /usr/openwin/share/etc/keytables/keytable.map file in one of the following ways:
Cannot Print Documents in Portable Document Format (6239307, 6218079)On all locales, the Document Viewer cannot print localized files that are in Portable Document Format (PDF). Workaround: Choose one of the following workarounds:
Sort Capability in the European UTF-8 Locales Does Not Function Correctly (4307314)The sort capability in the European UTF-8 locales does not work properly. Workaround: Before you attempt to sort in a FIGGS UTF-8 locale, set the LC_COLLATE variable to the ISO–1 equivalent.
Then start sorting. Networking IssuesThe following networking bugs apply to the Solaris 10 release. Login Fails on iSCSI Target With Two Portals and One Bad Portal (6476060)If an iSCSI target or an array returns more than one IP address as part of its send target response, the initiator takes into account only the last address in the list and not the first one, as it used to prior to this release. As a result, if the last IP address is bad or invalid, the connection to this target fails. Workaround: Return the different target portal group tags (TPGT) for each entry in its send target response. The initiator tries to establish a connection to all the IP addresses so that the connection succeeds. System Domain of Interpretation Is Not Configurable (6314248)The system Domain of Interpretation (DOI) is not configurable. When the SMC is used to create a new trusted network template, the SMC sets the DOI to 0 and Solaris Trusted Extensions does not function correctly. Various error messages are displayed. Workaround: Set the DOI to 1 using the SMC. IP Forwarding Disabled by Default in Solaris 10 OSIn this Solaris release, IP forwarding is disabled by default. This setting applies to both IPv4 and IPv6 regardless of other system configurations. Systems with multiple IP interfaces that formerly forwarded IP packets by default no longer have this automatic feature. To enable IP forwarding in multihomed systems, administrators must manually perform additional configuration steps. Workaround: The command routeadm enables IP forwarding. The configuration changes that are the result of routeadm usage persist across system reboots.
For more information about IP forwarding, see the routeadm(1M) man page. Zone Not Booting When IP Address Belongs to a Failed IP Network Multipathing Group (6184000)A zone can be configured so that the zone's IP address becomes part of an IP Network Multipathing (IPMP) group. The configuration process is documented in How to Extend IP Network Multipathing Functionality to Shared-IP Non-Global Zones in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones. If all the network interfaces in the IPMP group fail, a zone does not boot if it has an IP address that is part of the IPMP group. The following example illustrates the result if you attempt to boot the zone.
Workaround: Repair at least one network interface in the group. Intermittent Errors Might Occur With the Use of DataDigests (5108515)Internet SCSI (iSCSI) targets might report cyclic redundancy check (CRC) errors if DataDigests are enabled. User applications that update input/output buffers after transmitting to the iSCSI initiator might cause a miscalculation of the CRC. When the target responds with a CRC error, the iSCSI Initiator retransmits the data with the correct DataDigest CRC. Data integrity is maintained. However, data transfer performance is affected. No error message is displayed. Workaround: Do not use the DataDigest option. ATM LANE Subnets for IPv4/IPv6 Might Not Complete Initialization (4625849)During system boot, multiple instances might not connect to their LAN Emulation (LANE) instance if more than eight LANE instances are on a single adapter. This bug does not appear at multiuser level. Workaround: To reinitialize your SunATM network, perform the following steps:
Configuring Multiple Tunnels Between Two IP Nodes With Filtering Enabled Might Result in Packet Loss (4152864)If you configure multiple IP tunnels between two IP nodes, and enable ip_strict_dst_multihoming or other IP filters, packet loss might result. Workaround: Choose one of the following:
Security IssuesThe following security issues applies to the Solaris 10 release. Nonpassword Logins Fail With pam_ldap Enabled (6365896)After the account management PAM module for LDAP (pam_ldap) is enabled, users must have passwords to log in to the system. Consequently, nonpassword-based logins fail, including those logins that use the following tools:
Workaround: None. Incorrect Parameters Might Cause Panic in Sun StorEdge T3 (4319812)A Sun StorEdgeTM T3 system might panic if an application uses the HTTP interface to send tokens with out-of-range parameters. Service Management FacilityThis section describes issues that involve the Service Management Facility of Solaris 10 OS. For more information about this new feature in the Solaris OS, see Solaris Service Manager in Solaris 10 What’s New. Print Services Have Offline Settings by Default (5100134)When a host has no local printers configured, two print services, ipp-listener and rfc1179, are set to offline by default. These services are automatically moved to online after local printers are configured on the host. The default offline settings of these services do not indicate an error. Therefore, no user intervention is required. Workaround: None. Login Prompts Sometimes Appear Before File Systems Are Mounted (5082164)During system startups, sometimes the login services such as console or ssh logins start before remote file systems and naming services become available. Consequently, the user name might not be recognized or the user's home directory might not be available. Workaround: If the error occurs, wait for a few seconds and then log in again. Alternatively, log in from a local account to view the system state. Smart CardThe following Smart Card bugs apply to Solaris 10 OS. System Does Not Respond to Smart Card (4415094)If ocfserv terminates and the display is locked, the system remains locked even when a smart card is inserted or removed. Workaround: Perform the following steps to unlock your system:
ocfserv restarts and smart card login and capability are restored. Edit Config File Menu Item in Smartcards Management Console Does Not Work (4447632)The Edit Config File menu item in the Smartcards Management Console does not edit smart card configuration files that are located in /etc/smartcard/opencard.properties . If the menu item is selected, a warning is displayed which indicates not to continue unless requested by technical support. Workaround: Do not use the Edit Config File menu item in the Smartcards Management Console. For information on smart card configuration, see the Solaris Smartcard Administration Guide. Solaris Commands and StandardsThe following section describes behavior changes in certain commands and standards in Solaris 10 OS. Unsupported Options in the ddi_dma_mem_alloc(9F) Man Page (6571030)The ddi_dma_mem_alloc(9F) man page describes three options which are not supported. The unsupported options are as follows:
Workaround: None. Changed Man Pages for Solaris Trusted Extensions Are in Reference Manual OnlyThe following Solaris Trusted Extensions man pages are revised for this release:
The revised man pages cannot be viewed using the man command. To view the revised man pages, see the Solaris Trusted Extensions Reference Manual. Failed Unconfigure Command cfgadm Might Succeed Later Without Notice (6483258)Sometimes the cfgadm -c unconfigure command fails because of pending I/Os. With the changed kernel, the command is retried offline. The cfgadm's unconfigure command might, however, succeed later without any notice to the user. Workaround: Run the cfgadm -al command. Bash 2.0.5b No Longer Sets Some Environment VariablesSolaris 10 OS includes Bash 2.0.5b. This shell no longer automatically exports the following variables to the environment:
This new behavior applies even if the shell assigns default values to these variables. Workaround: Export these variables manually. New ln Utility Requires -f OptionThe behavior of /usr/bin/ln has changed to adhere to all of the standards from SVID3 through XCU6. If you use the ln command without the -f option to link to an existing target file, the link is not established. Instead, a diagnostic message is written to standard error, and the command proceeds to link any remaining source files. Finally, the ln command exits with an error value. For example, if file b exists, the syntax ln a b generates the following message:
This behavior change affects existing shell scripts or programs that include the ln command without the -f option. Scripts that used to work might now fail in Solaris 10 OS. Workaround: Use the -f option with the ln command. If you have existing scripts that execute the link utility, make sure to modify these scripts to comply with the command's new behavior. New tcsh Rejects setenv Variable Names That Use a Dash or an Equals SignIn Solaris 10 OS, tcsh has been upgraded to version 6.12. This version no longer accepts environment variables whose names use a dash or an equals sign. Scripts that contain setenv lines and that work in earlier Solaris versions might generate errors in the current Solaris 10 release. The following error message is displayed:
For more information, refer to the tcsh man page for the Solaris 10 OS. Workaround: Do not use the dash or equals sign in names for environment variables. STDIO getc Family EOF Condition Behavior ChangeApplications that were built in strict standard C conformance mode are affected by the behavior changes of certain library functions. An example is applications that were compiled by using the cc -Xc or c89 compilation mode. The behavior has changed for the following library functions:
A formal interpretation of the 1990 C Standard requires that after an end-of-file condition is set, no more data is returned from the file on subsequent input operations. The exception is if the file pointer is repositioned or the error and end-of-file flags are explicitly cleared by the application. The behavior for all other compilation modes remains unchanged. Specifically, the interfaces can read additional newly written data from the stream after the end-of-file indicator has been set. Workaround: Call fseek() or clearerr() on the stream to read additional data after the EOF condition has been reported on the stream. Output Columns of the ps Command Have Been WidenedDue to larger UIDs, processor ids, and cumulative execution time, the columns of the ps command output have been widened. Customer scripts should not assume fixed output columns. Workaround: Scripts should use the -o option of the ps command. For more information, see the ps(1) man page. Command ping -v Does Not Work on IPv6 Addresses (4984993)The command ping -v fails when the command is applied to addresses that use Internet Protocol version 6 (IPv6). The following error message is displayed:
Workaround: None. To obtain the same ICMP packet information that ping -v provides, use the snoop command. Solaris Volume ManagerThe following Solaris Volume Manager bugs apply to the Solaris 10 release. Solaris Volume Manager metattach Command Might FailIf you have a Solaris Volume Manager mirrored root (/) file system in which the file system does not start on cylinder 0, all submirrors you attach must also not start on cylinder 0. If you attempt to attach a submirror starting on cylinder 0 to a mirror in which the original submirror does not start on cylinder 0, the following error message is displayed:
Workaround: Choose one of the following workarounds:
Note – By default, the JumpStart installation process starts swap at cylinder 0 and the root (/) file system somewhere else on the disk. Common system administration practice is to start slice 0 at cylinder 0. Mirroring a default JumpStart installation with root on slice 0, but not cylinder 0, to a typical secondary disk with slice 0 that starts at cylinder 0, can cause problems. This mirroring results in an error message when you attempt to attach the second submirror. For more information about the default behavior of Solaris installation programs, see the Solaris 10 Installation Guides. Solaris Volume Manager metassist Command Fails in Non-English Locales (5067097)In non-English locales, the Solaris Volume Manager metassist command might fail to create volumes. For example, if LANG is set to ja (Japanese), the following error message is displayed:
Workaround: As superuser, set the LANG variable to LANG=C. For the Bourne, Korn, and Bash shells, use the following command:
For the C shell, use the following command:
Volume Creation Fails in Systems With Unformatted Disks (5064066)Creating Solaris Volume Manager volume configurations with the metassist command might fail if an unformatted disk is in the system. The following error message is displayed:
Workaround: Manually format any unformatted disks before you issue the metassist command. Hot Spares Do Not Work Correctly When Solaris Volume Manager RAID-1 (Mirror) or RAID-5 Volumes Are Created in Disk Sets Built on Soft Partitions (4981358)If you create a Solaris Volume Manager RAID-1 (mirror) or RAID-5 volume in a disk set that is built on top of a soft partition, hot spare devices do not work correctly. Problems that you might encounter include, but are not limited to, the following:
Solaris Volume Manager metadevadm Command Fails if Logical Device Name No Longer Exists (4645721)You cannot replace a failed drive with a drive that has been configured with the Solaris Volume Manager software. The replacement drive must be new to Solaris Volume Manager software. If you physically move a disk from one slot to another slot on a Sun StorEdge A5x00, the metadevadm command fails. This failure occurs when the logical device name for the slice no longer exists. However, the device ID for the disk remains present in the metadevice replica. The following message is displayed:
Note – You can access the disk at the new location during this time. However, you might need to use the old logical device name to access the slice. Workaround: Physically move the drive back to its original slot. Solaris Volume Manager metarecover Command Fails to Update metadb Namespace (4645776)If you remove and replace a physical disk from the system, and then use the metarecover -p -d command to write the appropriate soft partition specific information to the disk, an open failure results. The command does not update the metadevice database namespace to reflect the change in disk device identification. The condition causes an open failure for each such soft partition that is built on top of the disk. The following message is displayed:
Workaround: Create a soft partition on the new disk instead of using the metarecover command to recover the soft partition. Note – If the soft partition is part of a mirror or RAID 5, use the metareplace command without the -e option to replace the old soft partition with the new soft partition.
Sun Java Desktop SystemThis section describes issues that apply to the Sun Java Desktop System (Java DS) in the Solaris 10 OS. Email and CalendarThis section describes issues related to Email and Calendars. Problems With Using Multiple Attachments (6260583)If you drag and drop email messages to a new email message body, the content of the new email message is corrupted. Workaround: To send multiple attachments, perform the following steps:
Problem With Changing Authentication Type (6246543)After you change the authentication type for the incoming mail server, Email and Calendar might not work correctly. Workaround: Restart Email and Calendar. Incomplete List of Contacts in Contact Folder (5088514)After you import an LDAP Data Interchange Format file containing several contacts, only some of the contacts are displayed in your contact folder. This is a display problem only. Email and Calendar has imported all the contacts. Workaround: Restart Email and Calendar. Login IssuesThis section describes login issues. Cannot Login Using GDM Unless Clearance is Set to admin_high (6432114)The login fails when you log in to the Solaris Trusted Extensions Java Desktop Systems (Java DS) by using GDM. This failure is caused by the PAM configuration. The pam.conf(4) file does not contain the required entries for GDM. On login, the following error message is displayed:
Workaround: Add the following two lines to the /etc/pam.conf file:
For information about the file format, see the pam.conf(4) man page. Login Error MessageYou might encounter the following error message when you log in to a Java Desktop System session:
Workaround: Ensure that your hostname is set up correctly in the /etc/hosts file. Perform the following steps:
Help SystemWrong Help Window Opened For Volume Control (6253210)If you use the Yelp browser to open the online help for Volume Control, the help file for the Keyboard Accessibility panel application is opened instead. Workaround: None. Online Help Freezes (5090731)If you open an application's online help and no help files exist for that application, an error dialog box is displayed. Unless you click OK, the online Help system freezes and you cannot open the online help of other applications that you start subsequently. Workaround: You must click the OK button in the error dialog box. Mozilla BrowserCannot Print Certain Documents From the Mozilla BrowserYou cannot print documents from the Mozilla browser if the documents contain Unicode characters that are not in the Basic Multilingual Plane (BMP). Workaround: None. System-Level IssuesUser Preferences Not Fully CompatibleUser preferences in your home account for an earlier version of the GNOME Desktop might be partly incompatible with the version on the Java DS Release 3. Workaround: Reset your preferences. Perform the following steps:
Problems With Online Registration of StarOffice 7 Software (6208829)You might be unable to complete the online registration of the StarOffice 7 software if the software cannot find Mozilla on the system. The software must be able to locate the Email and Calendar application to successfully send documents. Workaround: Add /usr/sfw/bin to your PATH. Perform the following steps.
Problems With Sound RecorderThe slide bar and the side counter do not work when the Sound Recorder is recording a new.wav file. Workaround: None. Release Notes Do Not Display in Thunderbird Help (6565136)The release notes in the Thunderbird Help section fail to display. No error message is displayed. Workaround: Set Firefox as the default browser. When opening Firefox for the first time, the system asks you if you want to set Firefox as the default browser. Select Yes. Then select Edit-> Preferences-> Main-> Check Now. Trusted Java DS Workspace Does Not Start on Initial Change of Label (6550104)When you use the Trusted Java Desktop System (Java DS) workspace switcher to change the label of a workspace, the desktop does not start in that workspace. All applications fail to open in that workspace. No error message is displayed. Workaround: Add the following line to the /usr/openwin/server/etc/TrustedExtensionsPolicy file:
If the /usr/X11/lib/X11/xserver/TrustedExtensionsPolicy file is present on the system, also add the same line to this file. This change becomes effective on subsequent Trusted CDE and Java DS sessions. For more information, see the TrustedExtensionsPolicy(4) man page. Nautilus ACL MASK is Not in Sync With Group Permissions (6464485)The Group permissions in the Permissions tab should be the same as the Mask permissions in the Access Tab, but on some occasions they appear out of sync. Workaround: Click the Close button, and then click Reload. View the file properties again. The Group permissions and the Mask permissions will now be in sync again. The permissions are set to what you changed the Mask to in the previous step. strftime(3c) Should Support GNU Extension in %-m And %-d (6448815)The Java DS menu bar and some applications, like Evolution, incorrectly display Chinese date. The incorrect date is displayed in the %-m M %-d D format where M and D are the month and date in Chinese respectively. Workaround: Perform the following steps:
x86: Cannot Configure Full-Screen Magnification on Systems With One Video CardIf your Solaris 10 system has a single physical video card, you cannot configure the system for full-screen magnification. For such a configuration, you must use a separate configuration file in which you define settings for a dummy driver. First, make sure that the Xserver is not running. Then perform the following steps:
x86: Problems Configuring USB Mouse Device as Extension Device for Use With GNOME On-Screen KeyboardYou cannot set up a USB mouse device as an extension device with the GNOME On-Screen Keyboard (GOK). The configuration fails when you are setting up the USB mouse device while using a PS2 mouse device as the core pointer. To properly set up the USB mouse, follow these steps.
x86: GNOME Applications Fail With dtremote (6278039)GNOME applications do not start if you log in remotely and enable accessibility in gnome-at-properties. If you attempt to start a GNOME application, the following error message is displayed:
Workaround: None. Do not enable accessibility when you log in by using dtremote. To revert to the default desktop settings in which accessibility is disabled, close the GNOME session. Issue the following command:
Certain View Options Might Cause File Manager to Fail (6233643)The File Manager might fail if you use the following View options:
Depending on the View options that you use, the following error messages might be displayed:
Workaround: None. Every time these problems occur, restart File Manager or click the Restart Application button on the crash dialog box. Problems Creating Certain Types of Archives (5082008)You cannot use Archive Manager to create the following types of archives:
Workaround: None. System AdministrationThis section describes system administration bugs in Solaris 10 OS. Trusted $HOME Ownership Incorrect When Administrative Role Created (6579845)When the system is configured for Solaris Trusted Extensions and you use the SMC to create roles, the role's home directory might have incorrect ownership. Various error messages are displayed. Workaround: Log in as the root user. After you create a role, verify whether the new role's home directory has the correct owner and group.
The group for all roles should be sysadmin(14). Otherwise, change the group to sysadmin(14) by using the following chown command:
SAN 4.4.13 Emulex Error With Patch 119914-12 (6558400)While using Storade rasagent running with Emulex HBA driver version 2.20K and above, the following error message is posted to the /var/adm/messages file:
Workaround: These messages may be ignored. To stop the messages from being posted to the /var/adm/messages file, stop the Storade rasagent deamon. iscsitgtd Double Frees on Target Creation With an Alias (6554915)Using the optional parameter --alias or -a with the iscsitadm create target command within the iSCSI process daemon might cause the daemon process to panic by creating a process code dump. Because the iSCSI target daemon process is under the control of the Solaris SMF facility, the facility automatically restarts after a momentary pause while the process creates its core file. Workaround: Do not specify the optional --alias or -a parameters with the iscsitadm create target CLI command. Use the optional parameters with the iscsitadm modify target CLI command. iSCSI Target Coredumps When Running JIST Test Suite (6550844)When running the Java technology-based Interoperability Standards Test Suite (JIST), read, write, or compare load test with 10 threads as part of the entrance test for Amber Road, the iSCSI target generates a core dump. This core dump might cause the JIST test to fail with data compare errors. Sometimes the JIST might run successfully. However, a new core file is generated. Workaround: None. zoneadm attach Command Might Fail (6550154)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. Solaris is Unable to Handle Mode Switches Between Legacy and AHCI Modes for the SATA Controller (6520224)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. Deferred Activation Patching (6486471)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 features 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 feature patches better. These large kernel patches have always required a reboot, but now the required reboot activates the changes made by the loopback file system, lofs. lofs ensures the stability of the running system. 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:
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 8/07 Installation Guide: Solaris Live Upgrade and Upgrade Planning. Possible Error With 32-bit Applications Getting File System State on Large File Systems (6468905)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:
Workaround: Applications should use statvfs64() instead. x86: Uninstallation of Solaris Trusted Extensions Fails (6460106)Uninstallation of Solaris Trusted Extensions on x86 systems fails. On rebooting the system, the following error message is displayed:
The system then hangs. Workaround: Perform the following steps:
Using patchadd With the -R Option To Specify an Alternative Root Path From Systems That Are Not Zones Aware Should Be Restricted (6464969)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:
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. Sun Patch Manager Tool 2.0 Not Compatible With Previous VersionsA 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:
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. SPARC: Error Messages Displayed During Dynamic Reconfiguration (6312424)During dynamic reconfiguration (DR), error messages might be displayed. The messages are displayed if you perform DR while input and output operations are active on devices that are in the DR path. After the messages are displayed, the input and output operations are retried and eventually succeed. The following is a sample that is displayed:
Workaround: None. Ignore the error messages. Error Messages Displayed by pkgchk After You Remove Patches for Zones (6267966)The patchadd and patchrm commands work improperly in non-global zones with inherited file systems. Consequently, in those zones, the pkgchk command might generate error messages about packages under the following circumstances:
The following sample message is displayed when the pkgchk command is used on SUNWcsu under the circumstances previously listed.
Workaround: None. The errors are harmless. Ignore the error messages. Race Condition Between kcfd and IPsec Algorithm Availability (6266083)Systems with the Solaris 10 8/07 release might cause problems with IPsec. This problem might occur on a freshly installed system or a system that imports a large number of new Service Management Facility (SMF) manifests during the boot. After these booting conditions, IPsec, which is part of svc:/network/initial:default, might be initialized prior to the encryption framework, which is part of svc:/system/cryptosvc:default. Because authentication or encryption algorithms are not available, creation of IPsec security associations might fail with an error message such as the following:
For example, this error might occur when using DR on a Sun Fire E25K system, which involves IPsec services. Workaround: Before performing operations that use IPsec services, perform the following steps after a boot that imports a large number of new SMF manifests:
Now you can perform actions that create IPsec security associations, such as using DR on a Sun Fire E25K system. This procedure needs to be repeated only when a large number of new SMF manifests are imported during the boot. Solaris Product Registry Administration Utility Fails to Launch in a Zone (6220284)If you attempt to launch the Solaris Product Registry administration utility in a zone, the attempt fails. During the zone installation, productregistry, the Solaris Product Registry database, is not duplicated in the zone. Consequently, the utility cannot run in a zone. Workaround: As superuser, copy the productregistry database to the zone.
In the previous command, zone_path is the path to the root directory of the zone that you created. Cannot Delete Existing Diskless Clients From the System (6205746)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:
Workaround: Unshare the /export partition before adding the client. SPARC: smosservice delete Command Does Not Successfully Remove All Directories (6192105)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.
SPARC: Stopping the System by Using Keyboard Sequences Might Cause a System Panic (5061679)If you attempt to stop the system by pressing keyboard sequences such as Stop-A or L1-A, the system might panic. An error message similar to the following example is displayed:
Workaround: Do not use keyboard sequences to force the system to enter OpenBoot PROM. kill -HUP Does Not Always Cause the Agent to Reread the snmpd.conf Configuration File (4988483)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:
x86: Pressing the F4 Key During BIOS Bootup Fails to Boot the Service Partition (4782757, 5051157)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. Solaris WBEM Services 2.5 Daemon Cannot Locate com.sun Application Programming Interface Providers (4619576)The Solaris WBEM Services 2.5 daemon cannot locate providers that are written to the com.sun.wbem.provider interface or to the com.sun.wbem.provider20 interface. Even if you create a Solaris_ProviderPath instance for a provider that is written to these interfaces, the Solaris WBEM Services 2.5 daemon does not locate the provider. Workaround: To enable the daemon to locate such a provider, stop and restart the Solaris WBEM Services 2.5 daemon.
Note – If you use the Some com.sun Application Programming Interface Method Invocations Fail Under XML/HTTP Transport Protocol (4497393, 4497399, 4497406, 4497411)If you choose to use the com.sun application programming
interface rather than the The following table lists examples of invocations that execute successfully under RMI but fail under XML/HTTP:
Cannot Modify File-System Mount Properties With Solaris Management Console Mounts and Shares Tool (4466829)The Solaris Management Console Mounts and Shares tool cannot modify mount options on system-critical file systems such as root (/), /usr, and /var. Workaround: Choose one of the following workarounds:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|