What order do I need to start/stop the cluster services in?

Solution Verified - Updated

Environment

  • Red Hat Cluster Suite 4+
  • Red Hat Enterprise Linux Server 5 (with the High Availability or Resilient Storage Add on)
  • Red Hat Enterprise Linux Server 6 (with the High Availability or Resilient Storage Add on)

Issue

  • I want to gracefully remove a node from a cluster for updates or maintenance.
  • In What order do I start/stop cluster services in to keep the node from being fenced?
  • How do I restart cluster services in a Red Hat Enterprise Linux high availability cluster?
  • What order should services be stopped or started when restarting a Red Hat Enterprise Linux high availability cluster?
  • I need to reboot a cluster node. How can I make sure that the node leaves the cluster cleanly before the reboot?
  • Cluster restart sequence.
  • Stop/Sart sequence for cluster nodes.

Resolution

Any service not used in the cluster in question can be skipped. For more information about the available services, review the following documents: What services/daemons are available for Red Hat Enterprise Linux Cluster?.

This content is not included.Red Hat Enterprise Linux 6:


Starting order

# service cman start
# service cmirrord start     <-- optional
# service clvmd start        <-- optional
# service gfs2 start         <-- optional
# service rgmanager start    <-- optional
# service ricci start        <-- optional
# service luci start         <-- optional

Stopping order

# service luci stop
# service ricci stop
# service rgmanager stop
# service gfs2 stop
# service clvmd stop
# service cmirrord stop

NOTE: Stopping cman will cause a decrease in available votes for any nodes remaining in the cluster, which can cause a loss of quorum. If this is acceptable and expected, stop cman normally with:

# service cman stop

To avoid a loss of quorum, stop cman with:

# service cman stop remove

This content is not included.Red Hat Enterprise Linux 5:


Starting order

# service cman start
# service cmirror start       <-- optional
# service scsi_reserve start  <-- optional
# service qdiskd start        <-- optional
# service clvmd start         <-- optional
# service gfs start           <-- optional
# service gfs2 start          <-- optional
# service rgmanager start     <-- optional
# service ricci start         <-- optional

Stopping order

# service ricci stop
# service rgmanager stop
# service gfs2 stop
# service gfs stop
# service clvmd stop
# service qdiskd stop
# service scsi_reserve stop
# service cmirror stop
# service cman stop

This content is not included.Red Hat Enterprise Linux 4:


Starting order

# service ccsd start
# service cman start
# service cmirror start       <-- optional
# service scsi_reserve start  <-- optional
# service qdiskd start        <-- optional
# service fenced start
# service clvmd start         <-- optional
# service gfs start           <-- optional
# service rgmanager start     <-- optional
# service ricci start         <-- optional

Stopping order

# service ricci stop       
# service rgmanager stop
# service gfs stop
# service clvmd stop
# service fenced stop
# service qdiskd stop
# service scsi_reserve stop
# service cmirror stop
# service cman stop
# service ccsd stop
SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.