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.
Respond to service message Error
Respond to service message Allocating
Respond to service message Error
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.
Try stopping and then restarting the service.
Review the appropriate service instance log file to discover the cause of the error.
System service log files include those for the service director (ServiceDirector), web service gateway (WebServiceGateway), Platform Management Console (WEBGUI), respository service (RS), PERF purger (purger), PERF loader controller (plc), and the PERF 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 service message Allocating
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.
If you are the cluster administrator, review the allocation policy.
Open the service profile from the Platform Management Console. In the sc:AllocationSpecification section, review the consumer for which the service is expected to run.
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.