| Red Hat Cluster Manager: The Red Hat Cluster Manager Installation and Administration Guide | ||
|---|---|---|
| Prev | Chapter 4. Service Configuration and Administration | Next |
The cluster puts a service into the disabled state if it is unable to successfully start the service. A disabled state can be caused by various problems, such as a service start did not succeed, and the subsequent service stop also failed.
Be sure to carefully handle failed services. If service resources are still configured on the owner system, starting the service on the other cluster system may cause significant problems. For example, if a file system remains mounted on the owner system, and you start the service on the other cluster system, the file system will be mounted on both systems, which can cause data corruption. If the enable fails, the service will remain in the disabled state.
It is possible to modify a service that is in the disabled state. It may be necessary to do this in order to correct the problem that caused the disabled state. After modifying the service, it will be enabled on the owner system, if possible, or it will remain in the disabled state. The following list details steps to follow in the event of service failure:
Modify cluster event logging to log debugging messages. See the Section called Modifying Cluster Event Logging in Chapter 8 for more information.
Use the cluadmin utility to attempt to enable or disable the service on the cluster system that owns the service. See the Section called Disabling a Service and the Section called Enabling a Service for more information.
If the service does not start or stop on the owner system, examine the /var/log/messages log file, and diagnose and correct the problem. You may need to modify the service to fix incorrect information in the cluster database (for example, an incorrect start script), or you may need to perform manual tasks on the owner system (for example, unmounting file systems).
Repeat the attempt to enable or disable the service on the owner system. If repeated attempts fail to correct the problem and enable or disable the service, reboot the owner system.
If still unable to successfully start the service, verify that the service can be manually restarted outside of the cluster framework. For example, this may include manually mounting the filesystems and manually running the service start script.