HP XC System Software Release Notes for Version 3.1

info: Executing C11avail nconfigure
/bin/mknod: `/dev/pidentd': File exists
/bin/mknod: `/dev/deadman': File exists
/etc/rc.d/init.d/cmcluster.init: line 107: let: +: syntax
error: operand expected (error token is "+")
cmviewconf: Either binary file does not exist, or the user
doesn't have access to view the cluster configuration.
You might also see errors about uninitialized variables in AdapterMap.pm at or near lines 711
and 713. You can safely ignore these messages.
7.9.3 Known Limitation if Nagios is Configured for Improved Availability
When Nagios is configured for improved availability, by default, the head node acts as the Nagios
master and the other node in the availability set acts as a Nagios monitor.
The known limitation is that you cannot use the /sbin/service command to restart the Nagios
monitor on the non-head node in the availability set because of new functionality provided by
the /sbin/service script.
Issue the following command to restart the Nagios monitor service on the non-headnode of the
availability set:
# /etc/init.d/nagios restart
Running /sbin/service nagios restart on the non-headnode in the availability set causes
the nagios master to fail over.
7.9.4 Network Restart Command Negatively Affects Serviceguard
If a node is actively participating in a Serviceguard cluster, the Serviceguard tool manages some
HP XC services and their aliases. Because Serviceguard handles relocating these aliases after a
node dies, there are no network scripts defined for the aliases. Therefore, when you issue the
/sbin/service network restart command on a node in a Serviceguard cluster, the aliases
managed by Serviceguard are removed and never re-created. The services will not function
correctly and due to the HP XC configuration of Serviceguard, Serviceguard will not detect the
failure.
Follow this procedure of the head node to restart the network:
1. Transfer control of the database from Serviceguard to HP XC
# transfer_from_avail
2. Restart the network:
# /sbin/service network restart
3. Return control of the database to Serviceguard:
# transfer_to_avail
7.9.5 Problem Failing Over Database Package Under Serviceguard
Occasionally, when the head node is running with Serviceguard and the head node becomes
unresponsive, the database package fails to start up successfully on the other node in the
availability set with the head node.
Serviceguard reports that the database package is running and that any other packages that are
dependent upon the database, namely lvs and nagios, will be down. However, the database
may not have actually started correctly.
Run the service mysqld status command to verify whether the database is running . If
the mysqld service is not running and to recover from this scenario, use the following commands
to restart the service under Serviceguard :
1. cmhaltpkg dbserver.{nodename}
2. cmrunpkg -n {other node in avail set} dbserver.{nodename}
58 System Administration and Management