| www.sun.com | docs.sun.com |

| Chapter 5 # Error Messages The screen messages that are 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, the following applies: log_file is the name of the log file for the process you completed. For install, the name is `Maintenance_Update_log`. For backout, the name is `MU_Backout_log`. mu_version_name is the name of the MU (it is `Solaris_9MU2` for MU2). date_time is the designated date and time that was 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 see only the error text when the message is displayed. You cannot see the error code number that is included here. The error code numbers have been included here for reference. You might write a script that calls the `install_mu` or `backout_mu`. Your script then needs to check the return values for the failure conditions. `signal detected.` `install_mu (backout_mu) is terminating.` Explanation and recommended action: (Error Code 1) 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 are displayed in the log file. Ignore the error messages. `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: (Error Code 2) The program cannot find the file `/var/sadm/system/admin/INST_RELEASE` on the system. The system has become corrupted. The system must be reinstalled. `ERROR: Cannot find $xcommand which is required for proper execution of install_mu (backout_mu).` Explanation and recommended action: (Error Code 3) `install_mu` and `backout_mu` require certain system utilities (for example `awk, sed, grep`) to be present in the `/usr/bin` and `/usr/sbin` directories. One, of these utilities, is missing. Contact your system administrator for assistance. `The -B and -d arguments are mutually exclusive.` Explanation and recommended action: (Error Code 4) 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. `The -p parameter must be a directory. $uPATCHDIR is not a directory.` Explanation and recommended action: (Error Code 5) 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. `The -B parameter must be a directory. $1 is not a directory.` Explanation and recommended action: (Error Code 6) 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. `Permissions on backout directory $BACKOUTDIR not adequate.` Explanation and recommended action: (Error Code 7) You supplied an option to `-B` that is not a writable directory. Contact your system administrator for assistance. `Invalid option.` Explanation and recommended action: (Error Code 10) You selected an unrecognized option. Read the usage message displayed and reinvoke `install_mu` (or `backout_mu`). `Can't write to Log File: $LOGFILE` Explanation and recommended action: (Error Code 11) `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`). `SUNWcar (core architecture root) package does not exist in /var/sadm/pkg.` Explanation and recommended action: (Error Code 12) The `/var/sadm/pkg/SUNWcar` directory is missing on the system. Your system has become corrupted. Contact your system administrator for assistance. `install_mu (backout_mu) only supports the sparc architecture. install_mu (backout_mu) has detected ARCH=$LPROC` Explanation and recommended action: (Error Code 13) You ran `install_mu` (or `backout_mu`) on a system that is not based on SPARC™ architecture. Reinvoke `install_mu` (or `backout_mu`) on a SPARC platform. `-p parameter does not point to a directory containing a `.order` file. Looked in $uPATCHDIR and in $uPATCHDIR/MU/sparc/Patches.` Explanation and recommended action: (Error Code 14) You provided a path to a patch directory. However, `install_mu` could not find a `.order` file in that directory, which it needs to determine the correct patch installation order. `install_mu` checked the $path_you_specified and in the $path_you_specified`/MU/sparc/Patches`. Check for the existence of a `.order` file and reinvoke `install_mu`. `install_mu cannot locate patch order (`.order`) file. Paths searched: ./sparc/Patches, MU/sparc/Patches, ./$uPATCHDIR/MU/sparc/Patches.` Explanation and recommended action: (Error Code 15) 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. `You must be root to execute this script.` Explanation and recommended action: (Error Code 16) 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. `install_mu (backout_mu) can only patch version 2.9 systems. Target system is version $TrgOSVers.` Explanation and recommended action: (Error Code 17) You asked `install_mu` to apply patches to a system not running Solaris 9, or you asked `backout_mu` to back out patches from a system not running Solaris 9. `install_mu` and `backout_mu` must be run on a Solaris 9 system. `Not enough disk space to apply entire patch set.` Explanation and recommended action: (Error Code 22) `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. `Not enough disk space to save patch backout data.` Explanation and recommended action: (Error Code 23) `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. `Dry run disk space check failed.` Explanation and recommended action: (Error Code 24) `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. `The -f and -D options are mutually exclusive.` Explanation and recommended action: (Error Code 25) 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. `Cannot find state file. Looked for a file of the form /var/sadm/install_data/.mu_state.{$root_or_usr.date_time}.` Explanation and recommended action: (Error Code 27) `backout_mu` requires a file that contains 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 MU2 patch set, run the `backout_mu` program from the MU2 software distribution. |