Novell LINUX ENTERPRISE 11 - HIGH AVAILABILITY, Руководство пользователя, Страница: 58 / 298

If you do not configure resource monitoring, resource failures after a successful start
will not be communicated, and the cluster will always show the resource as healthy.
If the resource monitor detects a failure, the following takes place:
• Log file messages are generated, according to the configuration specified in the
logging
section of
/etc/ais/openais.conf
(by default, written to syslog,
usually
/var/log/messages
).
• The failure is reflected in the Linux HA Management Client, the crm_mon
tools,
and in the CIB status section. To view them in the Linux HA Management Client,
click Management in the left pane, then in the right pane, select the resource whose
details you want to see.
• The cluster initiates noticeable recovery actions which may include stopping the
resource to repair the failed state and restarting the resource locally or on another
node. The resource also may not be restarted at all, depending on the configuration
and state of the cluster.
4.8 Starting a New Cluster Resource
NOTE: Starting Resources
When configuring a resource with the High Availability Extension, the same
resource should not be started or stopped manually (outside of the cluster).
The High Availability Extension software is responsible for all service start or
stop actions.
If a resource's initial state was set to
stopped
when being created (
target-role
meta attribute has the value
stopped
), it does not start automatically after being cre-
ated. To start a new cluster resource with the Linux HA Management Client, select
Management in the left pane. In the right pane, right click the resource and select Start
(or start it from the toolbar).
48 High Availability Guide