Installation Bugs That Occur During an Upgrade

Upgrading From Solaris 8 Operating Environment Might Create Redundant Kerberos Privacy Mechanisms (4672740)

In the Solaris 9 operating environment, the Kerberos Version 5 global mechanism includes privacy support, and the Kerberos domestic mechanism is not needed. If you installed the Kerberos domestic mechanism (located in /usr/lib/gss/do/mech_krb.so.1) on a Solaris 8 system, it is recommended that you remove the Kerberos domestic mechanism before you upgrade the system to the Solaris 9 operating environment.

Workaround: Follow these steps before you upgrade to the Solaris 9 operating environment.

1. Type the following command to check to determine if the Kerberos domestic mechanism is installed on the system.

   % pkginfo | fgrep ' SUNWk5'

   • If the output of this command includes any SUNWk5 package names, the Kerberos domestic mechanism is installed on the system. Go to step 2.

   • If the output does not include any SUNWk5 package names, the Kerberos domestic mechanism is not installed on the system. Skip the rest of these steps and upgrade the system.

2. Back up the /etc/nfssec.conf and /etc/gss/qop files by typing the following command.

   % tar -cf /var/tmp/krb_config_files.tar /etc/nfssec.conf /etc/gss/qop

3. Verify that the files are backed up by typing the following command.

   % tar -tf /var/tmp/krb_config_files.tar

4. Remove each package listed in the output of step 1.

   % pkgrm package-name package-name package-name

5. Upgrade to the Solaris 9 operating environment.

   The upgrade program updates the global Kerberos mechanism code and enables Kerberos privacy support.

6. In a text editor, change the following lines in the /etc/gss/mech file.

   • Uncomment the following line.

     kerberos_v5 1.2.840.113554.1.2.2 gl/mech_krb5.so gl_kmech_krb5

     If necessary, add the previous line to the /etc/gss/mech file.

   • Remove the following line.

     kerberos_v5 1.2.840.113554.1.2.2 do/mech_krb5.so do_kmech_krb5

   • Restore the /etc/nfssec.conf and /etc/gss/qop files by typing the following command.

     % tar -xf /var/tmp/krb_config_files.tar

Upgrading to Solaris 9 Operating Environment Might Disable Existing Secure Shell Daemon (sshd) (4626093)

If you upgrade to the Solaris 9 operating environment on a system that is running a third party Secure Shell (for example, OpenSSH) from the /etc/init.d/sshd daemon, the upgrade disables the existing Secure Shell daemon. During an upgrade, the Solaris 9 upgrade software overwrites the contents of /etc/init.d/sshd.

Workaround: Choose one of the following workarounds.

• If you do not want the Secure Shell protocol server program on your system, do not install the SUNWsshdr and SUNWsshdu packages during the upgrade.

• If you do not want the Secure Shell protocol server or client programs on your system, do not install the Secure Shell Cluster (SUNWCssh) during the upgrade.

Upgrade Fails if /export Is Near Capacity (4409601)

If the /export directory is near full capacity and you upgrade to the Solaris 9 operating environment, the space requirements for /export are miscalculated and the upgrade fails. The problem commonly occurs if a diskless client is installed, or if third-party software is installed in /export. The following message is displayed:

WARNING: Insufficient space for the upgrade.

Workaround: Before you upgrade, choose one of the following workarounds.

• Temporarily rename the /export directory until the upgrade is completed.

• Temporarily comment out the /export line in the /etc/vfstab file until the upgrade is completed.

• If /export is a separate file system, then unmount /export before you perform the upgrade.

Upgrading Diskless Client Servers and Clients (4363078)

If your system currently supports diskless clients that were installed with the AdminSuite 2.3 Diskless Client tool, you must first delete all existing diskless clients that are the same Solaris version and architecture as the server. Then, install or upgrade to the Solaris 9 operating environment. For specific instructions, see System Administration Guide: Basic Administration.

If you attempt to install the Solaris 9 operating environment over existing diskless clients, the following error message might appear:

The Solaris Version (Solaris version-number) on slice <xxxxxxxx> cannot 
be upgraded. 
There is an unknown problem with the software configuration installed 
on this disk.

In this error message, version-number refers to the Solaris version that is currently running on your system. <xxxxxxxx> refers to the slice that is running this version of the Solaris operating environment.

Upgrading the JavaSpaces Data Store to Prevent WBEM Data Loss (4365035)

If you are upgrading from the Solaris 8, Solaris 8 6/00, or Solaris 8 10/00 operating environments to the Solaris 9 operating environment (Solaris WBEM Services 2.5), you must convert any proprietary custom Managed Object Format (MOF) data to the new Reliable Log repository format that is used with Solaris WBEM Services 2.5. Failure to convert the data results in data loss.

See "Upgrading the CIM Object Manager Repository" in Solaris WBEM Services Administration Guide for specific instructions on how to convert your WBEM data.