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

The system is not configured properly for cluster creation.
Please fix the previously reported problems, and then rerun the
'clu_create' command.
If you see these messages, enter the following command:
# ls -tlr /usr/.smdb./*PAT*.sts
If this command returns a file with 000000 in its name, you will have to run the clu_create
command with the -f option to force the creation of your cluster. The problem is caused by the
cluster software misinterpreting the existence of some patches and will be corrected in a future
patch kit.
If the command does not return a file with 000000 in its name, you will need to contact HP
support to determine the cause of the problem.
4.1.12 When Taking a Cluster Member to Single-User Mode, First Halt the Member
To take a cluster member from multiuser mode to single-user mode, first halt the member and
then boot it to single-user mode. For example:
# shutdown -h now
>>> boot -fl s
Halting and booting the system ensures that it provides the minimal set of services to the cluster
and that the running cluster has a minimal reliance on the member running in single-user mode.
When the system reaches single-user mode, enter the following commands:
# /sbin/init s
# /sbin/bcheckrc
# /usr/sbin/lmf reset
4.1.13 Login Failure Possible with C2 Security Enabled
Login failures may occur as a result of a rolling upgrade on systems with Enhanced Security
(C2) enabled. The failures may be exhibited in two ways:
With the following error message:
Can't rewrite protected password entry for user
With the following set of error messages:
login: Ignoring log file: /var/tcb/files/dblogs/log.00001: magic number 0, not 8
login: log_get: read: I/O error
Can't rewrite protected password entry for user
The problem may occur after the initial reboot of the lead cluster member or after the rolling
upgrade is completed and the clu_upgrade switch procedure has been run. The following
sections describe the steps you can take to prevent the problem or correct it after it occurs.
4.1.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:
4.1 Release Notes 151