Installation guide

Section 4.8:Handling Services that Fail to Start 81
4.7 Deleting a Service
A cluster service can be deleted. Note that the cluster database should be backed up before deleting a
service. See Section 8.5, Backing Up and Restoring the Cluster Database for information.
To delete a service by using the cluadmin utility, follow these steps:
1. Invoke the cluadmin utility on the cluster system that is running the service, and specify the
service disable
service_name command. See Section 4.3, Disabling a Service for
more information.
2. Specify the service delete
service_name
command to delete the service.
For example:
cluadmin> service disable user_home
Are you sure? (yes/no/?) y
notice: Stopping service user_home ...
notice: Service user_home is disabled
service user_home disabled
cluadmin> service delete user_home
Deleting user_home, are you sure? (yes/no/?): y
user_home deleted.
cluadmin>
4.8 Handling Services that Fail to Start
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 sys-
tem, 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 sys-
tem, 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:
1. Modify cluster event logging to log debugging messages. See Section 8.6, Modifying Cluster
Event Logging for more information.