Managing HP Serviceguard for Linux, Tenth Edition, September 2012

It is not necessary to halt the single node in this scenario, since the application is still
running, and no other node is currently available for package switching. (This is different
from the loss of the Serviceguard daemon in a multi-node cluster, which halts the node
(system reset), and causes packages to be switched to adoptive nodes.)
You should not try to restart Serviceguard, since data corruption might occur if another
node were to attempt to start up a new instance of the application that is still running on
the single node.
Instead of restarting the cluster, choose an appropriate time to shut down the applications
and reboot the node; this will allow Serviceguard to restart the cluster after the reboot.
Removing Serviceguard from a System
If you want to disable a node permanently from Serviceguard use, use the rpm -e
command to delete the software.
CAUTION: Remove the node from the cluster first. If you run the rpm -e command on
a server that is still a member of a cluster, it will cause that cluster to halt, and the cluster
to be deleted.
To remove Serviceguard:
1. If the node is an active member of a cluster, halt the node first.
2. If the node is included in a cluster configuration, remove the node from the
configuration.
3. If you are removing Serviceguard from more than one node, run rpm -eon one
node at a time.
288 Cluster and Package Maintenance