Disabling the Cluster Software

Red Hat Cluster Suite: Configuring and Managing a Cluster
Prev | Chapter 4. Cluster Administration | Next

# 4.8. Disabling the Cluster Software

It may become necessary to temporarily disable the cluster software on a cluster member. For example, if a cluster member experiences a hardware failure, you may want to reboot that member, but prevent it from rejoining the cluster to perform maintenance on the system.

Use the `/sbin/chkconfig` command to stop the member from joining the cluster at boot-up as follows:

    chkconfig --level 2345 rgmanager off
    chkconfig --level 2345 gfs off
    chkconfig --level 2345 clvmd off
    chkconfig --level 2345 fenced off
    chkconfig --level 2345 lock_gulmd off
    chkconfig --level 2345 cman off
    chkconfig --level 2345 ccsd off

Once the problems with the disabled cluster member have been resolved, use the following commands to allow the member to rejoin the cluster:

    chkconfig --level 2345 rgmanager on
    chkconfig --level 2345 gfs on
    chkconfig --level 2345 clvmd on
    chkconfig --level 2345 fenced on
    chkconfig --level 2345 lock_gulmd on
    chkconfig --level 2345 cman on
    chkconfig --level 2345 ccsd on

You can then reboot the member for the changes to take effect or run the following commands in the order shown to restart cluster software:

1. `service ccsd start`

2. `service lock_gulmd start` or `service cman start` according to the type of lock manager used

3. `service fenced start` (DLM clusters only)

4. `service clvmd start`

5. `service gfs start`, if you are using Red Hat GFS

6. `service rgmanager start`

Prev | Home | Next
Changing the Cluster Name | Up | Diagnosing and Correcting Problems in a Cluster