Service states

EGO services are by default your system services.

EGO services can have one of the following states:
Table 1. EGO service states
State Description
Defined The service definition is loaded or created by the API without syntax error. This state persists only if you defined a service to be started manually or if you have disabled it by API.
Init The service is being initialized and dependencies are being checked. A transitional state before becoming ALLOCATING.
Allocating Allocating resources to the service. A transitional state before becoming TENTATIVE or STARTED.
The service state is ALLOCATING when T, R, and H together is greater than the minInstances value specified in the service profile, where:
  • R is the number of instances in RUN state
  • T is the number of instances in TENTATIVE state (if Job Monitor is defined)
  • H is the number of instances in HOLD state
Tentative
The service state is TENTATIVE when R is less than the value of the minInstances value specified in the service profile, and R and T together are greater than or equal to the minInstances value, where:
  • R is the number of instances in RUN state
  • T is the number of instances in TENTATIVE state
Note: If Job Monitor is not defined, the service skips this state.
Started The service is started. Service instances are running or on hold.
Frozen The service has been frozen by the user in preparation for a temporary shutdown. This state prevents reassignment of an application's resources.
Error An error has been detected. Needs manual debugging.
Deallocating The service has been disabled by the system. Cleanup is occurring. A transitional state before becoming DEFINED.