3.4.2. Service States

The following list defines the states of services managed by RGManager.
  • disabled — The service will remain in the disabled state until either an administrator re-enables the service or the cluster loses quorum (at which point, the autostart parameter is evaluated). An administrator may enable the service from this state.
  • failed — The service is presumed dead. This state occurs whenever a resource's stop operation fails. Administrator must verify that there are no allocated resources (mounted file systems, and so on) prior to issuing a disable request. The only action which can take place from this state is disable.
  • stopped — When in the stopped state, the service will be evaluated for starting after the next service or node transition. This is a very temporary measure. An administrator may disable or enable the service from this state.
  • recovering — The cluster is trying to recover the service. An administrator may disable the service to prevent recovery if desired.
  • started — If a service status check fails, recover it according to the service recovery policy. If the host running the service fails, recover it following failover domain and exclusive service rules. An administrator may relocate, stop, disable, and (with virtual machines) migrate the service from this state.


Other states, such as starting and stopping are special transitional states of the started state.