HP Tru64 UNIX and TruCluster Server Version 5.1B-5 Patch Summary and Release Notes (March 2009)

During the install stage, clu_upgrade cannot tell whether the roll is going forward
or backward. This ambiguity incorrectly allows the clu_upgrade undo preinstall
stage to be run before clu_upgrade undo install. Refer to the Patch Kit Installation
Instructions for additional information on undoing a rolling patch.
4.2.7 clu_upgrade undo of Install Stage Can Result in Incorrect File Permissions
This note applies only when both of the following are true:
• You are using installupdate, dupatch, or nhd_install to perform a rolling
upgrade.
• You need to undo the install stage; that is, to use the clu_upgrade undo
install command.
In this situation, incorrect file permissions can be set for files on the lead member. This
can result in the failure of rsh, rlogin, and other commands that assume user IDs or
identities by means of setuid.
The clu_upgrade undo install command must be run from a nonlead member
that has access to the lead member's boot disk. After the command completes, follow
these steps:
1. Boot the lead member to single-user mode.
2. Run the following script:
#!/usr/bin/ksh -p
#
# Script for restoring installed permissions
#
cd /
for i in /usr/.smdb./$(OSF|TCR|IOS|OSH)*.sts
do
grep -q "_INSTALLED" $i 2>/dev/null && /usr/lbin/fverify -y <"${i%.sts}.inv"
done
3. Rerun installupdate, dupatch, or nhd_install, whichever is appropriate,
and complete the rolling upgrade.
For information about rolling upgrades, see the Patch Kit Installation Instructions and
the installupdate(8) and clu_upgrade(8) reference pages.
4.2.8 Missing Entry Messages Can Be Ignored During Rolling Patch
During the setup stage of a rolling patch, you might see a message like the following:
Creating tagged files.
............................................................
clubase: Entry not found in /cluster/admin/tmp/stanza.stdin.597530
clubase: Entry not found in /cluster/admin/tmp/stanza.stdin.597568
An Entry not found message will appear once for each member in the cluster. The
number in the message corresponds to a PID.
You can safely ignore this Entry not found message.
4.2 Prior Release Notes 207