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

The following sections describe the steps you can take to prevent the problem or correct
it after it occurs.
4.2.13.1 Preventing the problem
You can prevent this problem by performing the following steps before beginning the
rolling upgrade:
1. Disable the prpasswdd daemon from running on the cluster:
# rcmgr -c set PRPASSWDD_ARGS \
"`rcmgr get PRPASSWDD_ARGS` -disable"
2. Stop the prpasswdd daemon on every node in the cluster:
# /sbin/init.d/prpasswd stop
3. Perform the rolling upgrade procedure through the clu_upgrade switch step
and reboot all the cluster members.
4. Perform one of the following actions:
• If PRPASSWDD_ARGS did not exist before this upgrade (that is, if rcmgr get
PRPASSWDD_ARGS at this point shows only -disable), then delete
PRPASSWDD_ARGS:
# rcmgr -c delete PRPASSWDD_ARGS
• If PRPASSWDD_ARGS existed before this upgrade, then reset PRPASSWDD_ARGS
to the original string:
# rcmgr -c set PRPASSWDD_ARGS \
"`rcmgr get PRPASSWDD_ARGS | sed 's/ -disable//'`"
5. Check that PRPASSWDD_ARGS is now set to what you expect:
# rcmgr get PRPASSWDD_ARGS
6. Start the prpasswdd daemon on every node in the cluster:
# /sbin/init.d/prpasswd start
7. Complete the rolling upgrade.
4.2.13.2 Correcting the problem
If you have already encountered the problem, perform the following steps to clear it:
1. Restart the prpasswdd daemon on every node in the cluster:
# /sbin/init.d/prpasswd restart
2. Reboot the lead cluster member.
3. Check to see if the problem has been resolved. If it has been resolved, you are
finished. If you still see the problem, continue to step 4.
4. Try to force a change to the auth database by performing the following steps:
4.2 Prior Release Notes 211