Continentalclusters Version A.05.00 Release Notes, December 2004 (T2346-90006)

Continentalclusters Version A.05.00 Release Notes
Known Problems and Workarounds
Chapter 1 17
The directive order of order deny,allow or order allow,deny
specified in /etc/opt/cmom/cmomhosts does not allow any space
between “deny,allow” or “allow,deny”. If the file is not setup
properly, nodes that are running monitor packages will not be able to
obtain information from other nodes about the cluster status.
• What is the workaround?
After Continentalclusters configuration, before the first startup of
the monitor package, make sure that the file
/etc/opt/cmom/cmomhosts on all of the participating nodes contain
the correct directive order specification.
Persistent cmomd Processes
What is the problem? If the node where the monitor process
(cmclsentryd) is running goes down and then comes back up (as in a
power failure), the cmomd process will remain on one or more nodes in the
cluster that is being monitored. In these circumstances, the cmomd
process will continue on the system until terminated by a user. This can
become a significant problem if a monitoring node is powered off and on
several times, leaving several cmomd processes on the monitored cluster,
using system process table space as well as other system resources.
What is the workaround? After a failure of the monitoring node, kill the
unused cmomd processes.
Provider File Renaming
What is the problem? If the provider file, which is named
/opt/cmom/providers/cmprovider.omp by default, is copied to a
backup file by adding a prefix to the name (for example,
“bk_cmprovider.omp”), then Serviceguard will not be able to tell which
file is the correct one.
What is the workaround? Do not rename the provider file to a different
name by adding a prefix. As an alternative, you can store copies or
alternate versions of the file in a different directory.