This chapter describes error, warning, and informational messages for
the
dupatch
utility.
The following information is provided
for each message:
Source:
The function that generates the message.
Problem:
A brief description of possible causes
for the message.
Causes:
A summary of situations that cause the
message.
Action:
General recovery guidance.
Output:
A sample of the message.
The following sections describe messages you might see when running
the
dupatch
preinstallation check or installation functions.
Source:
Problem:
The installation of a specific patch
is blocked due to an existing system file that is unknown.
Cause:
Generally this situation occurs when system
files are placed on the system through manual intervention.
For example this
may have been the result of installing a prerelease patch received from Compaq
Services or a system administrator's customization of a Tru64 UNIX file.
Until you confirm otherwise, the unknown system files should be viewed
as intentional customizations that are important for proper system operation.
As such, care should be taken to understand why the system files have been
customized.
Action:
Determine the origin of the existing
unknown system files.
The steps you take will be determined by the reason
your system files were manually changed.
See
Section 2.6
for more information.
Output:
Checking patch prerequisites and patch file applicability...
dupatch
preinstallation
check or installation.
(depending upon the number of patches you select, this may take a while)
-------------------------------------------------------------------------
Problem installing:
- DIGITAL_UNIX_V4.0D / Common Desktop Environment (CDE) Patches:
Patch 0326.00 - CDE Login Correction
./usr/dt/bin/dtwm:
its origin cannot be identified.
This patch will not be installed.
-------------------------------------------------------------------------
* Following patch(es) failed in prerequisite/file applicability check:
- DIGITAL_UNIX_V4.0D / Common Desktop Environment (CDE) Patches:
Patch 0326.00 - CDE Login Correction
Source:
Problem:
Installation of a specific patch is
blocked due to missing system file.
Causes:
Generally this situation occurs when
a system file that was installed with
Action:
Determine why the system file is missing
and whether it is safe to enable
Output:
Checking patch prerequisites and patch file applicability...
dupatch
preinstallation
check or installation.
setld
is manually
removed from the system.
The file is marked as installed in the system inventory
records.
dupatch
to install the
blocked patch.
See
Section 2.6
for more information.
(depending upon the number of patches you select, this may take a while)
-------------------------------------------------------------------------
Problem installing:
- DIGITAL_UNIX_V4.0D / Commands, Shells, & Utility Patches:
Patch 0236.00 - vi Editor Correction
./usr/bin/vedit:
does not exist on your system,
however, it is in the inventory of installed subsets.
This patch will not be installed.
-------------------------------------------------------------------------
* Following patch(es) failed in prerequisite/file applicability check:
- DIGITAL_UNIX_V4.0D / Commands, Shells, & Utility Patches:
Patch 0236.00 - vi Editor Correction
Source:
Problem:
The installation of a specific patch
is blocked due to an existing system file that is installed by a layered product.
Causes:
A small set of layered products deliver
updated Tru64 UNIX operating system files.
Action:
To resolve this situation contact the
Product Customer Services representative for your layered product or Compaq
Services if you have purchased Business Critical Services.
Output:
Checking patch prerequisites and patch file applicability...
dupatch
preinstallation
check or installation.
(depending upon the number of patches you select, this may take a while)
-------------------------------------------------------------------------
Problem installing:
- DIGITAL_UNIX_V4.0D / Network Patches:
Patch 0182.00 - xti/streams Interface Module Correction
./sys/BINARY/xtiso.mod:
is installed by:
BLTLPCONFLICTTEST410
and can not be replaced by this patch.
This patch will not be installed.
-------------------------------------------------------------------------
* Following patch(es) failed in prerequisite/file applicability check:
- DIGITAL_UNIX_V4.0D / Network Patches:
Patch 0182.00 - xti/streams Interface Module Correction
Source:
dupatch preinstallation check or installation.
Problem:
The installation of a specific patch
is blocked due to its dependency on other uninstalled patches.
Causes:
Generally this occurs when you miss the
selection of all dependent patches.
Action:
Through the
Reselect the patches including the noted dependent patch and
attempt reinstallation; dupatch will notify you of other missing dependent
patches
Select all patches and proceed with patch installation
Output:
SAMPLE OUTPUT:
dupatch
Installation Menu, take one of the following actions:
Checking patch prerequisites and patch file applicability...
(depending upon the number of patches you select, this may take a while)
-------------------------------------------------------------------------
Problem installing:
- DIGITAL_UNIX_V4.0D / Security Related Patches:
Patch 0579.01 - Security, Various Kernel Fixes (SSRT0482U)
requires the existence of the following un-installed/un-selected subset(s):
- TruCluster_V1.5 / Filesystem Patches:
Patch 0037.00 - Support For New AdvFS Mount Option "-o noatimes"
- TruCluster_V1.5 / ASE Availability Manager (AM) Patches:
Patch 0033.00 - Kern Mem Fault And simple_lock Panic Correction
This patch will not be installed.
-------------------------------------------------------------------------
* Following patch(es) failed in prerequisite/file applicability check:
- DIGITAL_UNIX_V4.0D / Security Related Patches:
Patch 0579.01 - Security, Various Kernel Fixes (SSRT0482U)
Source:
Problem:
A specific patch cannot be installed
because the product software subset is not installed on your system.
Causes:
Generally this is a informational message
and no further action is required.
However, this message may also occur due
to an internal patch kit error that results in an incorrectly specified patch
dependencies.
Action:
If the specific patch being blocked is
the only patch being blocked you can assume this is an informational message.
It may be an internal patch kit error, if there are other patches whose installation
is blocked by the patch whose subset is not installed.
As a workaround, if
you need one of the other patches whose installation is blocked, you can install
the optional Tru64 UNIX or TCR release subset and reinstall the patches
Output:
Checking patch prerequisites and patch file applicability...
dupatch
preinstallation
check or installation.
(depending upon the number of patches you select, this may take a while)
-------------------------------------------------------------------------
Problem installing:
- TruCluster_V1.5 / Cluster Kernel Patches:
Patch 0035.00 - rm_spur Driver Correction
requires the existence of the following un-installed/un-selected subset(s):
- TruCluster_V1.5 - subset: TCRMCA141
This patch will not be installed.
-------------------------------------------------------------------------
* Following patch(es) failed in prerequisite/file applicability check:
- TruCluster_V1.5 / Cluster Kernel Patches:
Patch 0035.00 - rm_spur Driver Correction
Source:
Problem:
The system disk did not have enough
space to install patches.
Causes:
There is not enough disk space in
Action:
Provide the necessary disk space and
reinstall patches.
If you cannot provide enough system disk space through
other means, you may want to make
Output:
Checking patch prerequisites once more...
dupatch
preinstallation
check or installation.
/,
/var, or
/usr
partitions
for
dupatch
to archive the existing system files and move
the patched files into place.
/var/adm/patch/backup
a symbolic link to or NFS-mount another file system that is not related to
the
/,
/var, or
/usr
partitions.
(depending upon the number of patches you select, this may take a while)
./usr/lbin/fitset:
file system /whd needs 65829 Kbytes more to install the software specified.
There is not enough file system space to install all the patches.
you have selected.
Please press RETURN to start another selection.
.
.
.
This section describes messages you might see when running the
dupatch
patch deletion function.
Source:
Problem:
An attempt to remove a specific patch
or all patches fails because the backup of the prepatch system files is not
available to
Causes:
The
Action:
Ensure that
Output:
Checking patch dependency...
dupatch
deletion.
dupatch.
/var/adm/patch/backup
area does not contain the prepatch system files.
dupatch
can access the/var/adm/patch/backup
area and that the area
is set up as it was when the patches were installed.
For example, if you were
using
/var/adm/patch/backup
as a mount point
for another file system, make sure that file system is mounted.
Once
you have solved the
/var/adm/patch/backup
access or content
problem, remove patches through the dupatch Delete Menu.
(depending upon the number of patches you select, this may take a while)
-------------------------------------------------------------------------
- DIGITAL_UNIX_V4.0D / Commands, Shells, & Utility Patches:
Patch 0019.00 - quota Command Correction
cannot be deleted.
Can not find the backup copy for this patch in /var/adm/patch/backup.
-------------------------------------------------------------------------
* Following patch(es) failed in dependency check:
- DIGITAL_UNIX_V4.0D / Commands, Shells, & Utility Patches:
Patch 0019.00 - quota Command Correction
Source:
Problem:
A specific patch cannot be removed because
of its dependency on other installed patches.
Causes:
Generally this occurs when you miss the
selection of all dependent patches.
Action:
Through the
Output:
Checking patch dependency...
dupatch
deletion.
dupatch
Delete Menu, reselect the patches including the noted dependent patch and
try to remove them.
The program will notify you of any other dependent patches
you might have missed.
(depending upon the number of patches you select, this may take a while)
-------------------------------------------------------------------------
- DIGITAL_UNIX_V4.0D / Library Patches:
Patch 0262.00 - libm Corrections
can not be deleted unless the following patches are also selected or
deleted first:
- DIGITAL_UNIX_V4.0D / Library Patches:
Patch 0676.00 - libm Corrections
-------------------------------------------------------------------------
* Following patch(es) failed in dependency check:
- DIGITAL_UNIX_V4.0D / Library Patches:
Patch 0262.00 - libm Corrections
Source:
Problem:
The removal of a specific patch results
in no original system files being restored.
Causes:
This occurs when a patch delivers files
to your system that were not shipped in the initial release of the product.
For example, the sample output shows the removal of DIGITAL UNIX 4.0D Patch
314.00; the patch delivers files that were not shipped with the initial release
of DIGITAL UNIX 4.0D.
Action:
This is a informational message and no
further action is required.
Output:
=== Deleting "Digital UNIX V4.0D":
dupatch
deletion.
Deleting "Patch: AdvFS Command Correction " (OSFPAT00031400425).
-------------------------------------------------------------------------
Patch OSFPAT00031400425 delivered all new files to your system
so there are no original files to be restored.
No user action is necessary.
-------------------------------------------------------------------------