Chapter 4 Known Problems

This chapter describes known problems relating to the installation and use of the Solaris 7 MU4 software.

Installation Bugs

install_mu Does Not Function Correctly When Starting It Using sh 4062334

Because of problems regarding the interactions between sh(1) and ksh(1), the install_mu utility may fail to install certain patches correctly when you start it using the following command from the command line or from an administrative script:

# /bin/sh ./install_mu arguments

Workaround: Execute install_mu from the command line or from an administrative script as follows:

# ./install_mu arguments

install_mu Leaves Files in the /tmp Directory 4108278

install_mu leaves files and working directories in /tmp. The files and directories could cause /tmp to become full, potentially leading to system problems. Files and directories left in /tmp are of the form install* and SUNW*.

Workaround: After install_mu has completed execution, check /tmp for files and directories named install* and SUNW*. If the files were created recently by root, remove them. Or, if the MU was applied to a stand alone machine or server, reboot the system.

Patchadd Displays an Error That It Is Terminating

One of the following benign messages may be displayed by install_mu:

One or more patch packages included in
XXXXXX-YY are not installed on this system.

Patchadd is terminating.

Or:

Installation of XXXXXX-YY failed:
  Attempting to patch a package that is not installed.

These messages indicate that patchadd could not find on your system any of the packages that it intended to patch, so it skipped the indicated patch.

The message is displayed when patchadd notices a discrepancy installing a patch of one architecture onto a system with a different architecture (for example, a sun4u patch on a sun4c system.)

This may also be the result of one or more missing packages. The package may have been removed by the administrator, or never installed, as in the case of installing a cluster smaller than the Entire Distribution. This is common with diskless clients and AutoClient systems.

Workaround: Ignore the message.

Backout Bugs

Diskless Clients Unable to Login to European ISO8859-15 Locales (4255087)

In a heterogeneous client/server environment, after backing out special patch 108081-01 or 108082-01, logging in to European ISO8859-15 locales from a diskless client causes dtlogin to hang. The European ISO8859-15 locales are:

After backing out special patch 108081-01 or 108082-01, the following errors appear on the screen:

Backing out patch 108082-01...

pkgadd: ERROR: unable to create package object </usr/openwin/share/locale/da.ISO
8859-15/props/da.ISO8859-15>.
pkgadd: ERROR: unable to create package object </usr/openwin/share/locale/da.ISO
8859-15/props/de.ISO8859-15>.
.....
pkgadd: ERROR: unable to create package object </usr/openwin/share/locale/pt.ISO
8859-15/props/sv.ISO8859-15>.

Workaround: Do not login to the European ISO8859-15 locales from diskless clients. You may login to these locales from a server.

If you have logged in to a European ISO8859-15 locale and your system is hung, complete these steps:

1. Remotely login to the client from another machine.

   # rlogin client_name

   where client_name is the host name of the diskless client.

2. Kill the dtlogin and dtsession jobs.

   # kill -9 PID PID

   where PID are the Process IDs of dtlogin and dtsession.

3. Restart the dtlogin.

   # /usr/dt/bin/dtlogin &