HP Tru64 UNIX Technical Updates for the Version 5.1B and Higher Operating System and Patches (February 2010)

14. Start the prpasswdd daemon on every node in the cluster:
# /sbin/init.d/prpasswd start
15. Re-enable logins on the cluster by deleting the file /etc/nologin:
# rm /etc/nologin
16. Check to see if the problem has been resolved. If it has not, contact HP support.
New Response to Message Suggested (Feb. 2005)
Section 2.1.3.6 in the Patch Summary and Release Notes for Patch Kit 4 document says that you can
ignore an error message about a missing ladebug.cat file and the warning message that
follows. We now suggest that if you see these messages during the setup stage, that you verify
that the tagged files were properly created when you execute the preinstall stage.
In cases where the tagged files are not created, you can repeat the setup stage.
During the preinstall stage of a rolling upgrade you have the option of checking tagged files. We
suggest that you override the default setting and select the check tag option.
Do Not Install Prior NHD Kits on a Patched System (Feb. 2005)
Do not install the NHD–5 or NHD–6 kits on your TruCluster system if you have installed this
patch kit or earlier patch kits. Doing so may cause an incorrect system configuration. The
installation code for these new hardware delivery kits does not correctly preserve some cluster
subset files.
Turning on the TruCluster Server Sticky Connection Feature (Oct. 2004)
The sticky connection feature included in this kit enables cluster members to remember the
servicing cluster member of a connection requested from a specific client. Whenever a new
connection comes from an existing client, the cluster router recognizes the client and dispatches
that packet to the same member that was previously servicing this client. In this way, all
connections from a single client are serviced on a single cluster member.
By default, the sticky connection feature is disabled. You enable it by specifying the following
tuning attribute in the /etc/sysconfigtab file:
clua: sticky_net_enabled=1
When enabled, this feature is configured to perform per connection port. You can then configure
each port by specifying the “sticky” option in the /etc/clua_services file. For example, the
following line in the /etc/clua_services file configures TCP port 3000 to be a sticky port:
echome 3000/tcp in_multi,static,sticky
This feature is described in the clua_services(4) and sys_attrs_clua(5) reference pages, which you
can download by clicking on the following link:
sticky_manpages.tar
Save this file to a directory of your choice; for example, /tmp. The tar file contains both reference
pages in gzip format.
To install them on your system, untar the file and move the gzip files to the appropriate reference
page location. The default location is /usr/share/man/man4 and /usr/share/man/man5.
The procedure is as follows:
1. Change directories to the directory where you downloaded the sticky_manpage.tar
file. For example:
# cd /tmp
2. Untar the file:
# tar -xvf sticky_manpage.tar
blocksize = 40
Patch Kit Updates 17