Installation guide

<fs ref="web_fs"/>
<ip ref="127.143.131.100"/>
<apache ref="example_server"/>
</service>
<service autostart="0" domain="example_pri" exclusive="0"
name="example_apache2" recovery="relocate">
<fs name="web_fs2" device="/dev/sdd3" mountpoint="/var/www"
fstype="ext3"/>
<ip address="127.143.131.101" monitor_link="yes"
sleeptime="10"/>
<apache config_file="conf/httpd.conf" name="example_server2"
server_root="/etc/httpd" shutdown_wait="0"/>
</service>
</rm>
</cluster>
8.3. Managing High-Availabilit y Services
You can manage high-availability services using the Clu st er St at u s Ut ilit y, cl ustat, and the
Clu st er User Service Ad min ist rat io n Ut ilit y, cl usvcad m. cl ustat displays the status of a
cluster and cl usvcad m provides the means to manage high-availability services.
This section provides basic information about managing HA services using the cl ustat and
cl usvcad m commands. It consists of the following subsections:
Section 8.3.1, “Displaying HA Service Status with cl ustat”
Section 8.3.2, “ Managing HA Services with cl usvcad m”
8.3.1. Displaying HA Service St at us with cl ustat
cl ustat displays cluster-wide status. It shows membership information, quorum view, the state of all
high-availability services, and indicates which node the cl ustat command is being run at (Local).
Table 8.1, “ Services Status” describes the states that services can be in and are displayed when
running cl ustat. Example 8.3, “ cl ustat Display” shows an example of a cl ustat display. For
more detailed information about running the cl ustat command refer to the clustat man page.
T ab le 8.1. Services St at u s
Services St at u s Descrip t io n
St art ed The service resources are configured and available on the cluster system
that owns the service.
Reco verin g The service is pending start on another node.
Disab led The service has been disabled, and does not have an assigned owner. A
disabled service is never restarted automatically by the cluster.
St o p p ed In the stopped state, the service will be evaluated for starting after the next
service or node transition. This is a temporary state. You may disable or
enable the service from this state.
Red Hat Ent erprise Linux 6 Clust er Administ rat ion
14 2