Solaris 8 Maintenance Update 3 Installation Guide

# Chapter 5. Error Messages

The screen messages displayed during the execution of `install_mu` and `backout_mu` do not include all errors that might have occurred. Therefore, check the detail log file for additional information about any patches or packages that were not installed or backed out.

    # more /var/sadm/install_data/log_file.mu_version_name.date_time

In this example:

- log_file is the name of the log file for the process you completed. For install, it is `Maintenance_Update_log`. For backout, it is `MU_Backout_log`.

- mu_version_name is the name of the MU (it is `Solaris_8MU3` for MU3).

- date_time is the designated date and time copied from `date +%y%m%d%H%M%S` ( yyyymmddHHMMSS or year-month-day-hour-minute-second).

> Note - `/var/sadm/install_data/log_file` is a symbolic link to the most recent MU log file.

> Note - You will see only the error text when the message appears, not the error code number included here. The error code numbers are included here in case you are writing a script that calls the `install_mu` or `backout_mu` and your script needs to know the return values for the failure conditions.

``

Error Code 1:

signal detected.

install_mu (backout_mu) is terminating.

> Explanation and recommended action: You interrupted `install_mu` (or `backout_mu`) by pressing `Control-C`. Reinvoke the program. If you reinvoke `install_mu`, error messages about previously applied patches will appear in the log file. Ignore the error messages.

``

Error Code 2:

install_mu (backout_mu) is unable to find the INST_RELEASE file for the target file system. This file must be present for install_mu (backout_mu) to function correctly.

> Explanation and recommended action: The program cannot find the file `/var/sadm/system/admin/INST_RELEASE` in the client's root area. The client was not created properly or has become corrupted. Back up the client, then remove and re-create it.

``

Error Code 3:

ERROR: Cannot find $xcommand which is required for proper execution of install_mu (backout_mu).

> Explanation and recommended action: `install_mu` and `backout_mu` require certain system utilities (for example `awk, sed, grep`) to be present in the server's `/usr/bin` and `/usr/sbin` directories. One of these utilities is missing. Contact your system administrator for assistance.

``

Error Code 4:

The -B and -d arguments are mutually exclusive.

> Explanation and recommended action: The -d option requests that no backout data be saved. The -B option specifies a directory to store backout data. You cannot use these two options together. Reinvoke `install_mu` with only one of these options.

``

Error Code 5:

The -p parameter must be a directory. $uPATCHDIR is not a directory.

> Explanation and recommended action: You selected the -p option and supplied a path that is not a valid directory. Reinvoke `install_mu` (or `backout_mu`) with a valid path to the -p option.

``

Error Code 6:

The -B parameter must be a directory. $1 is not a directory.

> Explanation and recommended action: You supplied an option to -B that is not a directory. Reinvoke `install_mu` (or `backout_mu`) with a valid path to the -B option.

``

Error Code 7:

Permissions on backout directory $BACKOUTDIR not adequate.

> Explanation and recommended action: You supplied an option to -B that is not a writable directory. Contact your system administrator for assistance.

``

Error Code 10:

Invalid option.

> Explanation and recommended action: You selected an unrecognized option. Read the usage message displayed and reinvoke `install_mu` (or `backout_mu`).

``

Error Code 11:

Can't write to Log File: $LOGFILE

> Explanation and recommended action: `install_mu` and `backout_mu` need to write its log into the `/var/sadm/install_data` directory. Check that the `install_data` directory is writable, then reinvoke `install_mu` (or `backout_mu`).

``

Error Code 12:

SUNWcar (core architecture root) package does not exist in /var/sadm/pkg.

> Explanation and recommended action: The `/var/sadm/pkg/SUNWcar` directory is missing in the client or server's root area. Your client or server has become corrupted. Contact your system administrator for assistance.

``

Error Code 13:

install_mu (backout_mu) only supports sparc and i386 architectures. install_mu (backout_mu) has detected ARCH=$LPROC.

> Explanation and recommended action: You ran `install_mu` (or `backout_mu`) on a system whose architecture is not SPARC or i386. Reinvoke `install_mu` (or `backout_mu`) on a supported platform.

``

Error Code 14:

-p parameter does not point to a directory containing a .order file. Looked in $uPATCHDIR and in $uPATCHDIR/$MU_TOP/$LPROC/Patches.

> Explanation and recommended action: You provided a path to a patch directory but `install_mu` could not find a `.order` file in that directory, which it needs to determine the correct patch installation order. `install_mu` (or `backout_mu`) looked in $path_you_specified and in $path_you_specified`/MU/`$arch`/``Patches`, where $arch is either "sparc" or "i386." Check for the existence of a `.order` file and reinvoke `install_mu` (or `backout_mu`).

``

Error Code 15:

install_mu cannot locate patch order (.order) file. Paths searched: ./$LPROC/Patches, $MU_TOP/$LPROC/Patches, /cdrom/cdrom0/$LPROC/Patches, ./$uPATCHDIR, and ./$uPATCHDIR/$MU_TOP/$LPROC/Patches.

> Explanation and recommended action: You did not supply `install_mu` (or `backout_mu`) with the -p option to identify the patch directory and `install_mu` (or `backout_mu`) could not locate the patch directory. Reinvoke `install_mu` (or `backout_mu`) with the -p option.

``

Error Code 16:

You must be root to execute this script.

> Explanation and recommended action: You need root privileges to run `install_mu` or `backout_mu` because only user root can apply and remove patches. Reinvoke the program as root.

``

Error Code 17:

install_mu (backout_mu) can only patch version 2.8 systems. Target system is version $TrgOSVers.

> Explanation and recommended action: You asked `install_mu` to apply patches to a server or client not running Solaris 8, or you asked `backout_mu` to back out patches from a server or client not running Solaris 8. `install_mu` and `backout_mu` must be run on a Solaris 8 system.

``

Error Code 22:

Not enough disk space to apply entire patch set.

> Explanation and recommended action: `install_mu` analyzed your system and determined that not enough disk space was on one or more file systems to install the entire patch set. Make disk space available in the deficient file systems reported and reinvoke `install_mu`. If you believe that you have enough disk space to apply the Maintenance Update, reinvoke `install_mu` with the -f option.

``

Error Code 23:

Not enough disk space to save patch backout data.

> Explanation and recommended action: `install_mu` analyzed your system and determined that not enough disk space was in the backout directory to save patch backout data. Select a backout directory with enough space, then reinvoke `install_mu`. If you believe that you really have enough disk space in the backout directory, reinvoke `install_mu` with the -f option.

``

Error Code 24:

Dry run disk space check failed.

> Explanation and recommended action: `install_mu` invokes `pkgadd` with a special option to check for sufficient disk space. `pkgadd` failed, probably because `/` or `/var` is very low on disk space or because your system has become corrupted. Contact your system administrator for assistance.

``

Error Code 25:

The -f and -D options are mutually exclusive.

> Explanation and recommended action: The -f option instructs `install_mu` to skip the dry-run disk space calculation phase. The -D option requests that only the dry-run calculations be made. Choose one option, but not both.

``

Error Code 27:

Cannot find state file. Looked for a file of the form $ROOTDIR/var/sadm/install_data/.mu_state.{$root_or_usr.date_time}.

> Explanation and recommended action: `backout_mu` requires a file containing a list of the patches `install_mu` applied in order to know which patches to back out. If this file is missing, `backout_mu` cannot function. To remove the MU3 patch set, run the `backout_mu` program from the MU3 software distribution.

Installation Bugs |  | Solaris 8 Maintenance Update Contents