This appendix
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.
A.1 Patch Preinstallation Check and Installation Messages
The following sections describe messages you might see when running
the
dupatch
preinstallation check or installation functions.
A.1.1 Patch Installation Blocked by Unknown System File
Source:
Problem:
The installation of a specific patch
is blocked due to an existing system file that is unknown.
Cause:
This situation usually occurs when system
files are placed on the system through manual intervention.
For example, this
may have been the result of installing a Customer-Specific patch received
from HP 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:
dupatch
preinstallation
check or installation.
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.0F / 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:
- TRU64_UNIX_V4.0D / Common Desktop Environment (CDE) Patches:
Patch 0326.00 - CDE Login Correction
A.1.2 Patch Installation Blocked by Missing System File
Source:
Problem:
Installation of a specific patch is
blocked due to missing system file.
Causes:
This situation usually 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:
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.
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.0F / 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.0F / Commands, Shells, & Utility Patches:
Patch 0236.00 - vi Editor Correction
A.1.3 Installation Blocked by Layered Product Collision
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.
Output:
dupatch
preinstallation
check or installation.
Checking patch prerequisites and patch file applicability...
(depending upon the number of patches you select, this may take a while)
-------------------------------------------------------------------------
Problem installing:
- TRU_UNIX_V4.0F / 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.0F / Network Patches:
Patch 0182.00 - xti/streams Interface Module Correction
A.1.4 Patch Installation Blocked by Dependencies on Other Patches
Source:
Problem:
The installation of a specific patch
is blocked due to its dependency on other uninstalled patches.
Causes:
This usually occurs when you miss the
selection of all dependent patches.
Action:
Through the
Reselect the patches including the noted dependent patch and
attempt reinstallation;
Select all patches and proceed with patch installation.
Output:
dupatch
preinstallation
check or installation.
dupatch
Installation Menu, take one of the following actions:
dupatch
will notify you of other
missing dependent patches.
SAMPLE OUTPUT:
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.0F / 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.6 / Filesystem Patches:
Patch 0037.00 - Support For New AdvFS Mount Option "-o noatimes"
- TruCluster_V1.6 / 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:
- TRU64L_UNIX_V4.0F / Security Related Patches:
Patch 0579.01 - Security, Various Kernel Fixes (SSRT0482U)
A.1.5 Patch Installation Blocked by Missing Product Subset
Source:
Problem:
A specific patch cannot be installed
because the product software subset is not installed on your system.
Causes:
This is usually 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:
dupatch
preinstallation
check or installation.
Checking patch prerequisites and patch file applicability...
(depending upon the number of patches you select, this may take a while)
-------------------------------------------------------------------------
Problem installing:
- TruCluster_V1.6 / Cluster Kernel Patches:
Patch 0035.00 - rm_spur Driver Correction
requires the existence of the following un-installed/un-selected subset(s):
- TruCluster_V1.6 - subset: TCRMCA141
This patch will not be installed.
-------------------------------------------------------------------------
* Following patch(es) failed in prerequisite/file applicability check:
- TruCluster_V1.6 / Cluster Kernel Patches:
Patch 0035.00 - rm_spur Driver Correction
A.1.6 Patch Installation Blocked by Disk Space
Source:
Problem:
The system disk did not have enough
space to install patches.
Causes:
This occurs when 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:
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.
Checking patch prerequisites once more...
(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.
.
.
.
A.1.7 Patch Installation Blocked by Installed Patch or Subset
Source:
Problem:
The patch you are trying to install
is built so it cannot supersede the later revision patch or subset that is
installed on your system.
Causes:
This applicability feature is used to
ensure that your system is not regressed through the installation of older
code.
Action:
If the situation is caused by a Release
patch being blocked by a layered product or other subsets, contact your service
provider.
Output:
dupatch
preinstallation
check or installation.
Problem installing:
- DIGITAL_UNIX_V4.0D / Filesystem Patches:
Patch 00016.01 - System Run Level Correction
./sbin/.new..bcheckrc:
is installed by:
- DIGITAL_UNIX_V4.0D:
Patch C 00484.01
and can not be replaced by this patch.
This patch will not be installed.
A.1.8 Patch Installation Blocked by an Existing CSP
Source:
Problem:
Release patches will not automatically
supersede a Customer-Specific patch (CSP).
Causes:
A file you are trying to update with
a Release patch has been previously updated through the installation of a
CSP.
The Release patch does not have any knowlege as to whether it contains
fixes contained in CSPs.
Action:
Determine if the CSP is included in
the Release Patch Kit:
If yes, then you can safely remove the CSP (via
If no, contact your service provider to determine how to proceed.
Output:
dupatch
preinstallation
check or installation.
dupatch) and reinstall the Release patch .
Problem installing:
- DIGITAL_UNIX_V4.0F / Commands, Shells, & Utility Patches:
Patch 00444.00 - Fixes sort problem when running in Japanese locale
./usr/bin/sort:
is installed by Customer Specific Patch (CSP):
- DIGITAL_UNIX_V4.0F:
Patch C 00187.00
and can not be replaced by this patch. To install this patch,
you must first remove the CSP using dupatch. Before performing
this action, you should contact your Compaq Service
Representative to determine if this patch kit contains the
CSP. If it does not, you may need to obtain a new CSP from
Compaq in order to install the patch kit and retain the CSP fix.
A.1.9 The dupatch Tools Are Outdated
Source:
Problem:
Patch tool set residing on system are
not the most recent version.
Causes:
If the
Action:
This is an informational message and
no further action is required.
Output:
dupatch
preinstallation
check or installation.
dupatch
utility
delivered with the patch kit determines that the tools residing on the system
are not consistent with the patch kit, it will copy over updated versions
of utilities used by
dupatch.
Patch tools need to be installed or updated on your system.
Please invoke the command as the super-user (root) first.
* A new version of patch tools required for patch management
is now being installed on your system.
A.1.10 Some Patches Must Be Made Reversible
Source:
Problem:
Patch tool set residing on system is
not the most recent version.
Causes:
The user tried to install a patch as
nonreversible; however, the patch in question must be installed as reversible.
Action:
This is an informational message and
no further action is required.
Output:
dupatch
preinstallation
check or installation.
* The following patch(es) are required to be reversible and
will be made reversible automatically:
- DIGITAL_UNIX_V4.0F / Commands, Shells, & Utility Patches:
Patch C 00187.00 - v 4.0f patch E C187.00
A.2 Patch Removal Messages
The following sections describe messages you might see when running
the
dupatch
patch deletion function.
A.2.1 Patch Removal Blocked by Missing Patch Backup Files
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:
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.
Checking patch dependency...
(depending upon the number of patches you select, this may take a while)
-------------------------------------------------------------------------
- DIGITAL_UNIX_V4.0F / 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.0F / Commands, Shells, & Utility Patches:
Patch 0019.00 - quota Command Correction
A.2.2 Patch Removal Blocked by Dependencies on Other Patches
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:
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.
Checking patch dependency...
(depending upon the number of patches you select, this may take a while)
-------------------------------------------------------------------------
- DIGITAL_UNIX_V4.0F / Library Patches:
Patch 0262.00 - libm Corrections
can not be deleted unless the following patches are also selected or
deleted first:
- DIGITAL_UNIX_V4.0F / Library Patches:
Patch 0676.00 - libm Corrections
-------------------------------------------------------------------------
* Following patch(es) failed in dependency check:
- DIGITAL_UNIX_V4.0F / Library Patches:
Patch 0262.00 - libm Corrections
A.2.3 No Original Files Restored When Patch Is Removed
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 Tru64 UNIX 4.0F Patch
314.00; the patch delivers files that were not shipped with the initial release
of Tru64 UNIX 4.0F.
Action:
This is an informational message and
no further action is required.
Output:
dupatch
deletion.
=== Deleting "DIGITAL UNIX V4.0F":
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.
-------------------------------------------------------------------------
A.3 TruCluster Specific dupatch Messages
The following sections show the output of informational messages you
might see when running
dupatch
on a TruCluster system:
A.3.1 System Not Adequately Prepared
Output:
This system is part of a V5.0 cluster which has
not been prepared to do a rolling patch installation. Refer to the Patch
Installation Guide as to the proper procedure to start a
rolling patch.
A.3.2 Rolling Upgrade in Progress (Installation)
Output:
This system is part of a V5.0 cluster which
is currently in the process of being installed via the rolling upgrade/
rolling patch procedure. New patches cannot be installed on the system
until the rolling installation procedure has completed on all cluster
members.
A.3.3 Rolling Upgrade in Progress (Baselining)
Output:
This Cluster is in the process of a roll. Baselining is not permitted
until the cluster is out of the roll.
A.3.4 Version 5.0 Wave 4 Cluster is Unsupported
Output:
This system is a Version 5.0 - Wave 4 Cluster. Dupatch cannot patch
this type of cluster. This is an unsupported operation and dupatch will
now exit.
A.3.5 Patch Removal Fails Because Needed File Is Unavailable
Source:
Problem:
An attempt to remove patches fails because
the file
Cause:
At least one of the patches selected for
deletion in
Action:The
Contact your Customer Service Representative for assistance.
Output:
dupatch
deletion.
/var/adm/patch/versionswitch.txt
is not available
to
dupatch.
dupatch
has a version switch associated with
it (defined by having the attribute PATCH_REQUIRES_VERSION_SWITCH set to "Y"
in its
patch.ctrl
file).
The
versionswitch.txt
file is necessary to determine whether the version switch has been
thrown.
dupatch
utility
returns to the main menu.
In order to proceed with the delete operation,
you need to determine if the version switch was updated.
If it has been thrown,
you must run the undo script included with the patch to enable patch deletion
(see
Section 5.7).
If the switch has not been
thrown, you can enable the deletion of this patch by reconstructing the
versionswitch.txt
file.
You can also reselect patches for deletion,
omitting the patch containing the version switch.
/var/adm/patch/versionswitch.txt file not found!
Cannot delete patches selected since patch_ID requires a version switch.
Please reselect patches or resolve missing /var/adm/patch/versionswitch.txt
Please contact your Customer Service Representative for assistance.
A.3.6 Patch Removal Fails Because of a Version Switch
Source:
Problem:
The deletion of a patch containing a
version switch has been blocked because the switch has been thrown.
Action:The
Output:
dupatch
deletion.
dupatch
utility
returns to the main menu.
In order to proceed with the delete operation,
you need to determine if the version switch was indeed updated.
You can also
reselect patches for deletion, omitting the patch containing the version switch.
Version switch thrown for patch patch_ID
You cannot delete patch patch_ID
Please refer to the Patch Kit Release Notes for
instructions on allowing the patch deletion to proceed.
A.3.7 dupatch Cannot Create Needed File
Source:
Patch installation
Problem:
The
Cause:
At least one of the patches selected for
installation contains a version switch.
Action:
Verify that the file
Output:
dupatch
utility
cannot create the file
/var/adm/patch/versionswitch.txt
because it cannot obtain the version switch state from
/etc/sysconfigtab.
dupatch
records
the current version switch state in the file
/var/adm/patch/versionswitch.txt.
In order to facilitate the installation of this patch, this file
must be created.
While attempting to create this file,
dupatch
could not read the
/etc/sysconfigtab
file
/etc/sysconfigtab contains the entry
new_vers_low.
Cannot obtain version switch info from system files!
Cannot create versionswitch.txt file
Please contact your Customer Service Representative for assistance.
A.3.8 Insufficient Free Space (File System Full)
Source:
Problem:
The rolling upgrade cannot proceed because
required space allocations are not met.
Causes:
The
Action:
Run the
Output:
clu_upgrade setup
stage of the rolling upgrade procedure.
/,
/usr,
/var, and/or
/i18n
file
systems do not have the required amount of free space.
clu_upgrade -undo setup
command, free up enough space in the affected file systems to meet
the requirements listed in
Section 5.2.1, and
rerun the
clu_upgrade -undo setup
command.
*** Error ***
The tar commands used to create tagged files in the '/' file system have
reported the following errors and warnings:
NOTE: CFS: File system full: /
tar: sbin/lsm.d/raid5/volsd : No space left on device
tar: sbin/lsm.d/raid5/volume : No space left on device