Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
 Contact HP
HP.com home
HP Tru64 UNIX Version 5.1B-2 and Higher: Patch Kit Installation Instructions > Appendix B Common Error, Warning, and Informational Messages

TruCluster Specific dupatch Messages

 

Table of Contents
Glossary
Index
Content starts here

The following sections show the output of informational messages you might see when running dupatch on a TruCluster system:

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.

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.

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.

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.

Patch Removal Fails Because Needed File Is Unavailable


 

Source: dupatch deletion.

Problem: An attempt to remove patches fails because the file /var/adm/patch/versionswitch.txt is not available to dupatch.

Cause: At least one of the patches selected for deletion in 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.

Action: The 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 “Removing Patches Installed During a Rolling Upgrade”). 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.

Contact your Customer Service Representative for assistance.

Output:

/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.

Patch Removal Fails Because of a Version Switch


 

Source: dupatch deletion.

Problem: The deletion of a patch containing a version switch has been blocked because the switch has been thrown.

Action: The 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.

Output:

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.

dupatch Cannot Create Needed File


 

Source: Patch installation

Problem: The dupatch utility cannot create the file /var/adm/patch/versionswitch.txt because it cannot obtain the version switch state from /etc/sysconfigtab.

Cause: At least one of the patches selected for installation contains a version switch. 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

Action: Verify that the file /etc/sysconfigtab contains the entry new_vers_low.

Output:

Cannot obtain version switch info from system files! 
Cannot create versionswitch.txt file
Please contact your Customer Service Representative for assistance.

Insufficient Free Space (File System Full)


 

Source: clu_upgrade setup stage of the rolling upgrade procedure.

Problem: The rolling upgrade cannot proceed because required space allocations are not met.

Causes: The root (/), /usr, /var, and/or /i18n file systems do not have the required amount of free space.

Action: Run the clu_upgrade -undo setup command, free up enough space in the affected file systems to meet the requirements listed in “Preparation Stage”, and rerun the clu_upgrade -undo setup command.

Output:

*** 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
Printable version
Privacy statement Using this site means you accept its terms
2006 Hewlett-Packard Development Company, L.P.