Solaris 9 4/04 Release Notes

Installation Bugs That Occur During an Upgrade

The following installation bugs occur during an upgrade to the Solaris 9 4/04 release.

Update Fails When Installing a Solaris Flash Differential Archive (4997302)

If you are installing a Solaris Flash archive, a file appears to be new and causes the update to fail. The Solaris Flash software verifies that the files on the clone system are an exact duplicate of the master system. The reboot_processing script is not deleted at reboot. As a result, this file is recognized by the Flash software as a new file.

The following error message is displayed:

New files detected:  /etc/init.d/flash_reboot_processing

Workaround: To avoid encountering this problem, choose from one of the following workarounds:

Delete the flash_reboot_processing file before you install the Solaris Flash archive on the clone system.
When installing the differential archive, you can use the custom JumpStart forced_deployment keyword to force the installation. The new files that are detected on the clone are deleted during the installation, and the installation completes.
When installing the differential archive, you can use the custom JumpStart no_content_check keyword in the profile to turn off file checking. The software performs no file checking, no files are deleted, and the installation completes.
You can exclude the file when you create the differential archive. During the archive creation, this file is added to a file filter. The file is then ignored during the archive installation. Follow these steps:
1. Boot the master system.
2. To exclude the /etc/init.d/flash_reboot_processing file during the archive creation, type the following command:
  # flarcreate -n archive-name -A unchanged-master-image-dir-x \ /etc/init.d/flash-reboot-processing path/filename
During the creation of a differential archive, you can use the -M option to switch off file checking. No file manifest is created. As a result, the files on the clone system are not checked. Follow these steps:
1. Boot the master system.
2. To use the -M option to switch off file checking, type the following command:
  # flarcreate -n archive-name -A unchanged_master_image_dir -M path/filename

archive-name – Is the name you give the archive.
-A option – Is the unchanged-master-image-dir, which creates a differential archive by comparing a new system image with the image that is specified by the unchanged-master-image-dir argument.
path – Is the path to the directory in which you want to save the archive file. If you do not specify a path, the flarcreate command saves the archive file in the current directory.
filename – Is the name of the archive file.

For more information, see the Solaris 9 4/04 Installation Guide.

Installer Text Display Problem When Using Solaris Live Upgrade (4736488)

When using the Solaris Live Upgrade luupgrade(1M) command with the -i option to complete an upgrade of an inactive boot environment, the text that the installers display might be unreadable in some languages. The text is corrupted when the installers request fonts that do not exist on the older release that is on the current boot environment.

Workaround: Choose one of the following workarounds:

Use a combined network installation image to do the installation.
Enable the C locale by setting the environment variable on your system.
- If you are using the Bourne shell or Korn shell, follow these steps:
  1. Set the C locale.
    # LANG=C; export LANG
  2. Begin the installation.
- If you are using the C shell, follow these steps:
  1. Type the following:
    # csh
  2. Set the C locale.
    # setenv LANG C
  3. Begin the installation.

SPARC: Removal of `SUNWjxcft` Package Records Error During Upgrade (4525236)

When you upgrade from the Solaris 8 software to the Solaris 9 or the Solaris 9 4/04 release, a problem is encountered when the SUNWjxcft package is removed. The following error message is recorded in the upgrade_log file:

Removing package SUNWjxcft:
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.upr
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.scale
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.alias
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.upr
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.scale
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.alias
Removal of <SUNWjxcft> was successful

Workaround: Ignore the error message.

Upgrading to Solaris 9 4/04 Release Might Disable Existing Secure Shell Daemon (`sshd`) (4626093)

If you upgrade to the Solaris 9 4/04 release on a system that is running a third-party Secure Shell, such as OpenSSH from the /etc/init.d/sshd daemon, the upgrade disables the existing Secure Shell daemon. During an upgrade, the Solaris 9 4/04 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` Directory Is Near Capacity (4409601)

If the /export directory is near full capacity when you upgrade to the Solaris 9 4/04 release, space requirements for /export are miscalculated. The upgrade then fails. This problem commonly occurs if a diskless client is installed. Another instance of when the problem occurs is when third-party software is installed in the /export directory. The following message is displayed:

WARNING: Insufficient space for the upgrade.

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

Rename the /export directory temporarily, 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 Solstice AdminSuite^TM 2.3 Diskless Client tool, you must perform the following two steps:

Delete all existing diskless clients that are the same Solaris version and architecture as the server.
Install or upgrade to the Solaris 9 4/04 release.

For specific instructions, see the System Administration Guide: Basic Administration.

If you attempt to install the Solaris 9 4/04 software over existing diskless clients, the following error message might be displayed:

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 software.