test

Solaris 9 4/04 Release Notes

Chapter 2 Solaris Runtime Issues

This chapter describes runtime issues that are known to be problems. For late-breaking Solaris runtime issues that were not identified in time to be included in these release notes, refer to the Solaris 9 4/04 Release Notes at http://docs.sun.com/db/doc/817-3804.

The following runtime bug descriptions have been added to this chapter since the Solaris 9 4/04 Beta Release Notes was published on http://docs.sun.com.

Hardware–Related Bugs

The following hardware–related bugs apply to the Solaris 9 4/04 release.

System Panic Might Occur When USB Device Is Plugged in to USB 2.0 Port (5018218)

When certain USB devices are connected to a system by means of a USB 2.0 port, a race condition might occur. This condition might cause the system to panic.

Workaround: If the system panics, unplug the USB device, then reboot the system.

Support for Newer Digi Edgeport USB to Serial Converters Not Available in Solaris 9 4/04 OS (4900383)

The chip base for the Digi Edgeport USB-to-serial converters has recently changed, even though the new converters have retained the same model number. This change renders the newer converters unsupported in this Solaris OS release.

Support for Edgeport devices with the new chip will be available in a future Solaris release and as a patch.

Workaround: Order the device from the company, Inside Out Networks. When ordering, specify that the device will run on the Solaris OS. Ask for the older 930 unit.

For more information, go to http://www.ionetworks.com.

x86: USBA 1.0 Framework Device Driver for Universal Host Controller Interface Not Available in Solaris 9 4/04 OS (4990411)

The USBA 1.0 framework device driver (usba10_uhci) for the Universal Host Controller Interface (UHCI), is not available in the Solaris 9 4/04 release.

Running the usbconfig script that is available at http://www.sun.com/bigadmin, and specifying USBA 1.0 everywhere on systems with UHCI hardware, will bind all USB ports to the USBA 1.0 framework, with the exception of UHCI ports. This result is unexpected.

The output from the prtconf -D command will display the driver to which a USB host controller and its ports are bound.

Workaround: UHCI ports, if present, are still usable with the original USB framework.

Smart Card Bugs

The following Smart Card bugs apply to the Solaris 9 4/04 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:

  1. Perform a remote login to the machine on which the ocfserv process was terminated.

  2. Become superuser.

  3. Kill the dtsession process by typing the following in a terminal window.


    # pkill dtsession

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.

Common Desktop Environment (CDE) Bugs

The following CDE bugs apply to the Solaris 9 4/04 OS.

SPARC: Kernel Panics on Sun Blade 1000 and Sun Blade 2000 Systems if Power Management Is Enabled in a Diskless Client Setup (4985416)

In the Solaris 9 4/04 release, if power management is enabled in a diskless client setup on either a Sun BladeTM 1000 or a Sun BladeTM 2000 system, the kernel panics. This system panic occurs after a period of idle time.

The following error message is displayed:


/usr/sbin/pmconfig: /etc/power.conf line (18) failed to convert mount
point to prom name.

This message is also recorded in the /var/adm/messages file.

Workaround: To avoid this problem, follow these steps:

  1. Disable power management by editing the /etc/power.conf file. Change the autopm entry from default to disable.

  2. After you edit the /etc/power.conf file, choose from the following options:

    • Reboot the system for the changes to take effect.

    • Become superuser. Then, run the following command:


      # /usr/sbin/pmconfig

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 9 4/04 software.

Workaround: To use the auto run function for a CD-ROM or another removable media volume, you must do one of the following:

SPARC: dtmail Crashes When Launched From the Command Line if FontList Option Is Specified (4677329)

dtmail crashes after connecting with the IMAP server if the FontList option is specified when dtmail is launched from the command line. See the following example:


/usr/dt/bin/dtmail -xrm "Dtmail*FontList: -*-r-normal-*:"

The following error message is displayed:


Segmentation Fault

This problem occurs in both the C and ja locales.

Workaround: Do not specify the FontList option when you launch dtmail from the command line.

CDE Mailer Appears to Hang While Displaying Email With Long Lines (4418793)

If you try to read an email message with many long lines in any of the Solaris 9 4/04 Unicode or UTF-8 locales, CDE Mailer (dtmail) appears to hang. The message does not display immediately.

Workaround: Choose one of the following workarounds:

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.

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 SolarisTM PDASync application. If you accidentally exchange multibyte data and corrupt that data, restore your data from the backup.

GNOME 2.0 Issues and Bugs

The following information pertains to the GNOME 2.0 desktop.

GNOME 2.0 Documentation

For release notes and troubleshooting information for the GNOME 2.0 desktop, see the following documents at http://docs.sun.com:

System Administration Bugs

The following System Adminstration bugs apply to the Solaris 9 4/04 release.

cfgadm - l Command Does Not List USB Devices When Run Without Superuser Privileges (4999109)

Normally, the cfgadm -l command lists all dynamically reconfigurable hardware resources on a system, including USB devices. After you install the Solaris 9 4/04 software, the cfgadm -l command might no longer accurately list USB devices. Or, if you add the SUNWusb package by using the pkgadd command, this command might no longer accurately list USB devices.

Workaround: Choose from the following workarounds:

x86: Universal Serial Bus Architecture Modular DeBugger Not Configured Automatically When Only New Framework Is Loaded (4982529)

The Universal Serial Bus Architecture (USBA) Modular DeBugger (mdb) commands might not be automatically configured on some x86 systems.

Workaround: To access the USBA mdb commands, run the following command to load the usba mdb module manually after starting mdb:


> ::load usba

After the usba mdb module is loaded, you can obtain a list of all the USB commands by running the following command:


> ::dcmds ! grep usb

Problems Reading and Writing DVDs Greater Than 4-Gbytes on Solaris 9 4/04 Software (4908624, 4987026)

Problems are encountered when reading and writing DVDs that are greater than 4-Gbytes on the Solaris 9 4/04 software.

Note –

These problems occur on both SPARC 32-bit and x86 platforms. These problems do not occur on either of these platforms for DVDs with less than 4-Gbytes of data or on the 64–bit SPARC platform.

The same data seemingly repeats itself every 4-Gbytes. These DVDs can be mounted for reading, but some files might appear to be corrupted, while other files might be inaccessible. In addition, writes to offsets that are greater than 4-Gbytes might lead to corruption of the existing data on the DVD.

Workaround: None.

lucreate Command Fails When Mounted Storage Device Name Is a Subset of Another Mounted Storage Device or a Storage Device Used for a New Boot Environment (4912890)

When using the lucreate command to create a new boot environment, the command fails in the following instances:

The following misleading error messages are displayed:


The file system creation utility /usr/lib/fs/ufsufs/mkfs is not available.
 

Unable to create all required file systems for boot-environment.
 

Cannot make file systems for boot-environment

Workaround: Ensure that there are no file systems in use on storage devices that have device names which are subsets of other storage devices on file systems that are also in use.

If any name ambiguity exists among the mounted file systems, rename the existing Solaris Volume Management metadevices.

In the following workaround, d10 and d100 are used as an example only. Other examples of ambiguous device names could be d20 and d200, or d377 and d37, where d20 matches d200, and d377 matches d37.

  1. Become superuser.

  2. Use the metarename command to rename one of the ambiguous metadevice names.


    # metarename d10 d300

    The metadevice d10 is renamed to d300.

Note –

The file system on d10 must be unmounted before using the metarename command.

While the file system is unmounted, edit the /etc/vfstab file. Also, edit any other appropriate configuration file that contains the name of the metadevice you are renaming. Change any references of the old metadevice name to the new metadevice name.

If a process is accessing data on the file system, take the system down to single-user mode to unmount the file system. Reboot the system after making the changes.

Existence of /etc/named.conf File Causes Solaris Management Console Operations on User and Group Accounts to Fail (4777931)

If you use Solaris Management Console to perform operations on a User or Group account on a system that serves as a Domain Name Service (DNS) server, errors occur. These errors occur if the /etc/named.conf file exists on that system.

The following errors occur when you perform these operations from the graphical user interface (GUI) or when you use smuser and smgroup, which are command-line interfaces for the console.

The console launches a new dialog box or the smuser command exits with the following error messages when operated on a User:


"The attempt to view Users or Roles has failed due to an unexpected
error.
        This was caused by the following error: CIM_ERR_FAILED."

The console launches a new dialog box or the smgroup command exits with the following error message when operated on a Group:


"Attempted Read of Group IDs failed with unexpected CIM error:
        CIM_ERR_FAILED."operations from the GUI or command-line interface.

Workaround: Choose from one of the following workarounds:

For more information, see the smuser(1M) and the smgroup(1M) man pages.

x86: Pressing the F4 Key During BIOS Bootup Fails to Boot the Service Partition (4782757)

You are booting a Sun LX50 which has a Service partition and the Solaris 9 4/04 (x86 Platform Edition) software 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.

UltraSPARC II CP Event Message Not Always Produced (4732403)

In the Solaris 9 4/04 release, on UltraSPARC II based systems, the CP Event message that accompanies some Uncorrectable Memory Error messages is not always produced. The following systems are included:

The result is that some information needed to identify a failing CPU might not always be present.

Workaround: For the latest information, check the SunSolveSM web site at http://sunsolve.sun.com.

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.


# /etc/init.d/init.wbem stop

# /etc/init.d/init.wbem start
Note –

If you use the javax API to develop your provider, you do not need to stop and restart the Solaris WBEM Services 2.5 daemon. The Solaris WBEM Services 2.5 daemon dynamically recognizes javax providers.

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 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:

Method Invocation 

Error Message 

CIMClient.close()

NullPointerException

CIMClient.execQuery()

CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED

CIMClient.getInstance()

CIM_ERR_FAILED

CIMClient.invokeMethod()

XMLERROR: ClassCastException

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:

CIM_ERR_LOW_ON_MEMORY Error Occurs When Trying to Add Data With WBEM (4312409)

The following error message is displayed when memory is low:


CIM_ERR_LOW_ON_MEMORY

You cannot add more entries when the CIM Object Manager is low on memory. You must reset the CIM Object Manager Repository.

Workaround: To reset the CIM Object Manager Repository, follow these steps:

  1. Become superuser.

  2. Stop the CIM Object Manager.


    # /etc/init.d/init.wbem stop

  3. Remove the JavaSpacesTM log directory. 


    # /bin/rm -rf /var/sadm/wbem/log

  4. Restart the CIM Object Manager. 


    # /etc/init.d/init.wbem start
    Note –

    When you reset the CIM Object Manager Repository, you lose any proprietary definitions in your data store. You must recompile the MOF files that contain those definitions by using the mofcomp command. See the following example:


    # /usr/sadm/bin/mofcomp -u root -p root-password your-mof-file

Solaris Volume Manager Issue

The following Solaris Volume Manager issue applies to the Solaris 9 4/04 release.

Solaris Volume Manager metattach Command Might Fail

If 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:


can't attach labeled submirror to an unlabeled mirror

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 9 4/04 Installation Guide.

Solaris Volume Manager Bugs

The following Solaris Volume Manager bugs apply to the Solaris 9 4/04 release.

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 you might encounter include, but are not limited to, the following:

Solaris Volume Manager metahs -e Command Fails on Copper Cable Storage Boxes When Failed Hot Spare Disk Has Been Swapped Out (4644106)

The metahs -e command might fail if you encounter the following circumstances:

  1. A hot-spare device encounters a problem, such as an induced error, when using the metaverify test utility.

  2. Solaris Volume Manager software attempts to activate the hot spare when an error occurs on a metadevice. The hot spare is marked broken.

  3. The system is brought down. The failed disk that contains the hot spare is replaced with a new disk at the same location.

  4. When the system is booted, Solaris Volume Manager software does not recognize the new hot spare.

  5. The metahs -e command is used to enable the hot spare on the new disk.

The following message is displayed:


WARNING: md: d0: open error of hotspare (Unavailable)

The failure occurs because the Solaris Volume Manager software does not internally recognize the new hot-spare disk that was swapped into the same physical location. The Solaris Volume Manager software continues to display the device ID of the disk that is no longer in the system.

Note –

This failure is not known to occur on a Photon or storage enclosures where the device number changes when a disk is replaced.

Workaround: Choose one of the following workarounds:

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 Photon, 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:


Unnamed device detected. Please run 'devfsadm && metadevadm -r to resolve.
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:


Open Error

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.


# metareplace dx mirror or RAID 5 old_soft_partition new_soft_partition

Networking Bug

The following Networking bug applies to the Solaris 9 4/04 release.

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 Bugs

The following Security bugs apply to the Solaris 9 4/04 release.

Unlocking CDE Screenlock Removes Kerberos Version 5 Credentials (4674474)

If you unlock a locked CDE session, all your cached Kerberos version 5 (krb5) credentials might be removed. The result is you might not be able to access various system utilities. This problem occurs under the following conditions:

If this problem occurs, the following error message is displayed:


lock screen: PAM-KRB5 (auth): Error verifying TGT with host/host-name:
Permission denied in replay cache code

Workaround: Add the following non-pam_krb5 dtsession entries to the /etc/pam.conf file:


dtsession auth requisite pam_authtok_get.so.1
dtsession auth required  pam_unix_auth.so.1

With these entries in the /etc/pam.conf file, the pam_krb5 module does not run by default.

cron, at, and batch Cannot Schedule Jobs for Locked Accounts (4622431)

In the Solaris 9 4/04 release, locked accounts are treated in the same way as expired or nonexistent accounts. As a result, the cron, at, and batch utilities cannot schedule jobs on locked accounts.

Workaround: To enable locked accounts to accept cron, at, or batch jobs, replace the password field of a locked account (*LK*) with the string NP, for no password.

Additional Software Bug

The following is an additional software bug that applies to the Solaris 9 4/04 release.

SPARC: Veritas Volume Manager Might Fail on Systems Running Solaris 9 4/04 Software (4642114)

If you try to perform various tasks with Veritas Volume Manager on a system that is running the Solaris 9 4/04 software, the following utilities might produce a core dump:

Workaround: Follow these steps:

  1. Become superuser.

  2. Verify that the /var/ld/ld.config file and /usr/bin/crle utility exist on the system.

  3. Type the following commands in a terminal window:


     # /usr/bin/cp /var/ld/ld.config /var/ld/ld.config.save
 # /usr/bin/crle -E LD_LIBRARY_PATH=/usr/lib
 # appropriate-vxddladm-command
 # /usr/bin/mv /var/ld/ld.config.save /var/ld/ld.config

Documentation CD Issues

The following Documentation CD issues apply to the Solaris 9 4/04 release.

iPlanet Directory Server 5.1 Documentation Links Do Not Work Properly

In the iPlanetTM Directory Server 5.1 Collection (Solaris Edition), links titled DocHome do not work. In addition, links between separate books do not work. If you select these links, your browser displays a Not Found error.

Workaround: To navigate between iPlanet Directory Server 5.1 documents on your system, go to the iPlanet Directory Server 5.1 Collection (Solaris Edition) page at http://docs.sun.com. Click the link to the document you want to view.

SUNWsdocs Package Needed to Remove Other Documentation Packages

If you remove the SUNWsdocs package, then try to remove other documentation packages, the removal fails. This problem occurs because the SUNWsdocs package is installed with any collection and provides the browser entry point.

Workaround: If you removed the SUNWsdocs package, reinstall the SUNWsdocs package from the documentation media and then remove the other documentation packages.

Documentation CD Bugs

The following Documentation CD bugs apply to the Solaris 9 4/04 release.

European Locale PDF Documents Available Only Through C Locale (4674475)

In the Solaris 9 4/04 software and other systems based on UNIX, PDF documents on the Solaris 9 4/04 Documentation 1 of 2 CD are not accessible in the following European locales:

This problem occurs because of a limitation with Adobe Acrobat Reader. For more information on this problem, see the Adobe Technote site at http://www.adobe.com:80/support/techdocs/294de.htm.

Workaround: Choose one of the following workarounds.

Removing Solaris 9 4/04 Documentation Packages Might Unexpectedly Uninstall Some Solaris 9 4/04 Documentation Collections (4641961)

Some Solaris 9 4/04 documentation collections might be unexpectedly removed from your system under the following circumstances:

  1. You install both the Solaris 9 4/04 Documentation 1 of 2 and 2 of 2 CDs on your system.

  2. You then use the prodreg utility or the Solaris 9 4/04 Documentation CD installer program to remove certain documentation packages.

The Solaris 9 4/04 Documentation CD 1 of 2 and 2 of 2 have three collections in common. If you remove the packages that contain these collections from either of the Solaris 9 4/04 Documentation 1 of 2 or 2 of 2 CD installations, the package is removed for both installations.

The following table lists the packages that might be removed unexpectedly:

Table 2–1 Solaris 9 4/04 Documentation Packages Contained on Both Solaris 9 4/04 Documentation CDs

HTML Package Names 

PDF Package Names 

Collection Description 

SUNWaadm

SUNWpaadm

Solaris 9 System Administrator Collection 

SUNWdev

SUNWpdev

Solaris 9 Developer Collection 

SUNWids

SUNWpids

iPlanet Directory Server 5.1 Collection 

Workaround: Choose one of the following workarounds:

Localization Issue

The following is a Localization issue that applies to the Solaris 9 4/04 release.

Hardware for Estonian Keyboard Type 6, French Canadian Keyboard Type 6, and Polish Programmers Keyboard Type 5 Not Available

Software support for three additional keyboard layouts has been added to the Solaris 9 software for this release: 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:

Localization Bugs

The following Localization bugs apply to the Solaris 9 4/04 release.

SPARC: Shift-U Does Not Work as Expected in Arabic Locales (4303879)

To generate the diacritic character in Arabic locales, type the Arabic character, then Shift-U.

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.


# echo $LC_COLLATE
>  es_ES.UTF-8
# LC_COLLATE=es_ES.IS08859-1
# export LC_COLLATE

Then start sorting.

Sun ONE Application Server Bugs

The following Sun ONE Application Server bugs apply to the Solaris 9 4/04 release.

Default Browser Is Incompatible With Sun ONE Application Server 7 (4741123)

When you attempt to use the Sun ONE Application Server Administrative UI with the Solaris 9 4/04 software default browser, the following error message is displayed:


Unsupported Browser: Netscape 4.78

It is recommended that you upgrade your browser to Netscape 4.79 or 
Netscape 6.2 (or later) to run the Sun One Application Server 
Administrative UI. Those who choose to continue and not upgrade may
notice degraded performance or unexpected behavior.
Note –

If you are running the version of Sun ONE Application Server Administrative UI that is included in the Solaris 9 4/04 release, use Netscape 4.79 or Netscape 7.0 software.

Workaround: Use /usr/dt/appconfig/SUNWns/netscape instead of /usr/dt/bin/netscape.

Sun ONE Application Server Security Bug

The following Sun ONE Application Server Security bug applies to the Solaris 9 4/04 release.

The Application Server Starts All Instances as Root Allowing Nonroot Users Root Access (4780076)

Several issues are associated with Application Server startup when the Sun ONE Application Server is installed as part of a Solaris installation:

During the installation of the Sun ONE Application Server, the /etc/init.d/appserv script and symbolic links to the S84appserv and K05appserv scripts in the /etc/rc*.d/ directories are installed. These scripts cause all application server instances and administrative server instances, defined as part of the application server installation, to be started and stopped automatically during Solaris system startup and shutdown.

The /etc/init.d/appserv script contains the following section of code:

case "$1" in
'start')
    /usr/sbin/asadmin start-appserv
    ;;
'stop')
    /usr/sbin/asadmin stop-appserv
    ;;

Execution of the asadmin start-appserv command causes the administration server instance and all application server instances, defined in all administrative domains, to be started during Solaris system startup. Because the system startup and shutdown scripts are executed as root, the startup script for each application server and administrative server instance is also executed as root. The instance-level startup script is named startserv and is located at instance-dir/bin/startserv. Because instances can be owned by users other than root, the startserv scripts could be modified by the nonroot user to execute commands as the root user.

If an instance is using a privileged network port, the instance's startserv script must be executed as root. However, run as user is typically set in the instance's configuration. The purpose is to force the instance to run as the specified user after the instance has been initially started by the root user.

Workaround: Perform one of the following workarounds, depending on your environment:

Startup Considerations: When modifying the Solaris software startup scripts to automatically start either specific application server administrative domains or specific application server instances, consider the following:

For more information on thestartup and shutdown commands that are available through the asadmin command-line interface, see the Sun ONE Application Server 7 Administrator's Guide at http://docs.sun.com/db/prod/s1.asse.

Sun ONE Directory Server (Formerly iPlanet Directory Server) Issues

The following issues pertains to the Sun ONE Directory Server processes and tasks.

Setup Issue

When typing a Distinguished Name (DN) during installation, use the UTF-8 character set encoding. Other encodings are not supported. Installation operations do not convert data from local character set encoding to UTF-8 character set encoding. Lightweight Directory Interchange Format (LDIF) files that are used to import data must also use UTF-8 character set encoding. Import operations do not convert data from local character set encoding to UTF-8 character set encoding.

Schema Issues

The schema provided with the Sun Open Net Environment (Sun ONE) Directory Server (formerly iPlanet Directory Server) 5.1 differs from the schema that is specified in RFC 2256 for the groupOfNames and groupOfUniquenames object classes. In the schema provided, the member and uniquemember attribute types are optional. RFC 2256 specifies at least one value for these types must be present in the respective object class.

The aci attribute is an operational attribute that is not returned in a search, unless you explicitly request the attribute.

Replication Issue

Multimaster replication over a wide area network (WAN) is currently not supported.

Server Plug-In Issues

Sun ONE Directory Server 5.1 provides the user identification number (UID) Uniqueness plug-in. By default, the plug-in is not activated. To ensure attribute uniqueness for specific attributes, create a new instance of the Attribute Uniqueness plug-in for each attribute. For more information on the Attribute Uniqueness plug-in, refer to the iPlanet Directory Server 5.1 Administrator's Guide at http://docs.sun.com.

The Referential Integrity plug-in is now off by default. To avoid conflict resolution loops, the Referential Integrity plug-in should only be enabled on one master replica in a multimaster replication environment. Before enabling the Referential Integrity plug-in on servers that issue chaining requests, analyze your performance resource, time, and integrity needs. Integrity checks can consume significant memory and CPU resources.

Roles and Class of Service Issue

The nsRoleDN attribute is used to define a role. This attribute should not be used for evaluating role membership in a user's entry. When evaluating role membership, look at the nsrole attribute.

Indexing Issue

If virtual list view (VLV) indexes encompass more than one database, the VLV indexes do not work correctly.

Sun ONE Directory Server Bugs

The following Sun ONE Directory Server bugs apply to the Solaris 9 4/04 release.

Cannot Inactivate Users Through Console (4521017)

If you launch the Sun ONE Directory Server 5.1 Console and create a new user or new role as inactive, the newly created user or newly created role is not inactivated. Users and roles cannot be created through the Console as inactive.

Workaround: To create an inactive user or inactive role, follow these steps:

  1. Create the new user or new role.

  2. Double-click the newly created user or newly created role. Or, select the newly created user or newly created role. Click the Properties item from the Object menu.

  3. Click the Account tab.

  4. Click the Inactivate button.

  5. Click OK.

The newly created user or newly created role is inactivated.

Cannot Configure Directory With a Root Suffix That Contains Spaces (4526501)

If you specify a base DN that contains a space, for example, o=U.S. Government,C=US at Sun ONE Directory Server 5.1 configuration time, the resulting DN is truncated to Government,C=US. At configuration time, the DN should be typed as o=U.S.%20Government,C=US.

Workaround: To correct the base DN entry, follow these steps:

  1. Select the top directory entry in the left side of the navigation pane of the Servers and Applications tab on the Console.

  2. Edit the suffix in the User directory subtree field.

  3. Click OK.

Password Policy Information Is Not Synchronized Between Servers (4527608)

If you update a nonmaster directory server with password policy information, the information is not replicated to all other servers. This information includes account lockouts.

Workaround: Manage password policy information manually on each server.

Account Lockout Remains Effective After the User Password Is Changed (4527623)

If Account Lockout is effective and the user password is changed, Account Lockout remains effective.

Workaround: Reset the accountUnlockTime, passwordRetryCount, and retryCountResetTime lockout attributes to unlock the account.

Console Backup Done Immediately After Installation Fails (4531022)

If you install the Sun ONE Directory Server 5.1, start the console, initialize the directory with an LDIF file, and then back up the server, the Console reports the backup was successful. However, the backup has actually failed.

Workaround: Perform the following tasks from the Console after you initialize the database:

  1. Stop the server.

  2. Restart the server.

  3. Perform the backup.

Server Ignores Case-Sensitive Syntax When Normalizing DN Attributes (4630941)

You cannot use the LDAP naming services to create automount path names that are identical, with the exception of case results in nonunique path names. The directory server does not allow creation of entries if the naming attribute is defined with case-sensitive syntax, and an entry already exists with the same name, but a different case.

For example, /home/foo and /home/Foo paths cannot coexist.

If entry attr=foo,dc=mycompany,dc=com exists, the server does not allow the creation of attr=Foo,dc=mycompany,dc=com. A corollary of this problem is when LDAP naming services are used, automount path names have to be unique, regardless of their case.

Workaround: None.

Stopping the Server During Export, Backup, Restore, or Index Creation Crashes the Server (4678334)

If the server is stopped during export, backup, restore or index creation, the server crashes.

Workaround: Do not stop the server during these types of operations.

Replication Unable to Use Self-Signed Certificate (4679442)

If you attempt to configure replication over SSL with certificate-based authentication, replication does not work if either of the following conditions exist:

Workaround: None.

UFS File System Issue

The following UFS File System issue applies to the Solaris 9 4/04 release.

SPARC: Do Not Create a UFS File System on VxVM Volumes Greater Than 2 Tbytes in Size

If you attempt to create a UFS file system on a Veritas Volume Manager (VxVM) volume that is of 2 Tbytes or greater, you produce an error state. The outcome is a file system that is the size of the VxVM volume modulo 2 Tbytes. For example, a VxVM volume 8.4 Tbytes in size would produce a .4 Tbyte file system.

No warning message is displayed.

Workaround: None.

UFS File System Bug

The following UFS File System bug applies to the Solaris 9 4/04 release.

SPARC: Using fssnap on a Multiterabyte UFS File System Does Not Work (4836824)

Using the fssnap command to create a snapshot of a UFS file system that is greater than 1 Tbyte in size is not supported in the Solaris 9 4/04 release. The following error message is displayed:


fssnap: Fatal: File system /dir/snapshot0 support large files.

Workaround: None.