HP Tru64 UNIX and TruCluster Server Version 5.1.B-4 Patch Summary and Release Notes (13156)

4.1.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.1.9 Relocating AutoFS During a Rolling Upgrade on a Cluster
This note applies only to performing rolling upgrades on cluster systems that use AutoFS.
During a cluster rolling upgrade, each cluster member is singly halted and rebooted several
times. The Patch Kit Installation Instructions direct you to manually relocate applications under
the control of Cluster Application Availability (CAA) prior to halting a member on which CAA
applications run.
Depending on the amount of NFS traffic, the manual relocation of AutoFS may sometimes fail.
Failure is most likely to occur when NFS traffic is heavy. The following procedure avoids that
problem.
At the start of the rolling upgrade procedure, use the caa_stat command to learn which member
is running AutoFS. For example:
# caa_stat -t
Name Type Target State Host
------------------------------------------------------------
autofs application ONLINE ONLINE rye
cluster_lockd application ONLINE ONLINE rye
clustercron application ONLINE ONLINE swiss
dhcp application ONLINE ONLINE swiss
named application ONLINE ONLINE rye
To minimize your effort in the following procedure, perform the roll stage last on the member
where AutoFS runs.
When it is time to perform a manual relocation on a member where AutoFS is running, follow
these steps:
1. Stop AutoFS by entering the following command on the member where AutoFS runs:
# /usr/sbin/caa_stop -f autofs
2. Perform the manual relocation of other applications running on that member:
# /usr/sbin/caa_relocate -s current_member -c target_member
After the member that had been running AutoFS has been halted as part of the rolling upgrade
procedure, restart AutoFS on a member that is still up. (If this is the roll stage and the halted
member is not the last member to be rolled, you can minimize your effort by restarting AutoFS
on the member you plan to roll last.)
1. On a member that is up, enter the following command to restart AutoFS. (The member
where AutoFS is to run, target_member, must be up and running in multi-user mode.)
4.1 Release Notes 149