Troubleshooting service error states

About this task

If you receive a service error message, or a message indicating that a service cannot transition out of the Allocating state, there are steps you can perform to troubleshoot the issue.

There are two types of service messages:

Service error messages: Normally, EGO attempts to start a service multiple times, up to the maximum threshold set in the service profile XML file (containing the service definition). If the service cannot start, you receive a service error message.
Allocating service messages: Allocating is a transitional service state before the service starts running. If your service remains in this state for some time without transitioning to Started, or cycles between Defining and Allocating, you want to discover the cause of the delay.

Procedure

Respond to service error messages:
1. Try stopping and then restarting the service.
2. Review the appropriate service instance log file to discover the cause of the error.
  
  System service log files include those for the session director (SD), service director (ServiceDirector), web service gateway (WebServiceGateway), cluster management console (WEBGUI), repository service (RS), reporting framework purger (purger), loader controller (plc), and the reporting framework derby database service (derbydb). If you have defined your own non-system services, you may have other log files you need to review, depending on the service that is triggering the error.
Respond to allocating service messages
1. If you are the cluster administrator, review the allocation policy.
2. Open the service profile from the cluster management console. In the sc:AllocationSpecification section, review the consumer for which the service is expected to run.
3. Ensure that a proper resource plan is set for that consumer.
  
  During a service's allocation period, EGO attempts to find an appropriate resource on which to run the service. If it cannot find the required resource, the service does not start.