Viewing Service Events
During the whole lifecycle of a service, every key event is automatically recorded. You can view the events on the details page of the service at any time.
This helps you better understand the process of deploying a service and locate faults more accurately when a task exception occurs. The following table lists the available events.
| Type | Event (xxx should be replaced with the actual value.) | Solution |
| Normal | The service starts to deploy. Start to deploy service. | - |
| Abnormal | Insufficient resources. Wait until idle resources are sufficient. Lack of resources, transform state to waiting. | Wait until the resources are released and try again. |
| Abnormal | Insufficient xxx. The scheduling failed. Supplementary information: xxx %s %s Schedule failed due to insufficient resources. Retry later. %s nodes are available: %s Insufficient memory. | Learn about resource insufficiency details based on the supplementary information. For details, see FAQ. |
| Normal | The image starts to create. Start to build image. | - |
| Abnormal | Failed to create model image xxx. For details, see logs :\nxxx. Failed to build image for model (%s %s), docker build log:\n%s. | Locate and rectify the fault based on the build logs. |
| Abnormal | Failed to create the image. Failed to build image. | Contact technical support. |
| Normal | The image created. Image built successfully. | - |
| Abnormal | Service xxx failed. Error: xxx Failed to %s service, retry later. Error message: %s | Locate and rectify the fault based on the error information. |
| Abnormal | Failed to update the service. Perform a rollback. Failed to update service, rollback it. | Contact technical support. |
| Normal | The service is being updated. Updating service. | - |
| Normal | The service is being started. Starting service. | - |
| Normal | The service is being stopped. Stopping service. | - |
| Normal | The service has been stopped. Service stopped. | - |
| Normal | Auto stop has been disabled. Auto-stop switched off. | - |
| Normal | Auto stop has been enabled. The service will stop after xs. Auto-stop switched on, service will be stopped in %d %s. | - |
| Normal | The service stops when the auto stop time expires. Service stopped automatically because due time is reached. | - |
| Abnormal | The service is stopped because the quota exceeds the upper limit. Service stopped automatically because over quota. | Contact technical support. |
| Abnormal | Failed to automatically stop the service. Error: xxx Failed to stop service automatically, error message: %s | Locate and rectify the fault based on the error information. |
| Abnormal | Failed to start the edge service. Failed to start service. | For details about how to locate and rectify the fault, see FAQ. |
| Abnormal | Failed to stop the edge service. Failed to stop service. | Contact technical support. |
| Normal | [%d] of the edge model quota has been used. Consume [%d] edge model quotas. | Contact technical support. |
| Normal | [%d] of the edge model quota has been released. Return [%d] edge model quotas. | - |
| Abnormal | Failed to deploy or update the service in edge pool xxx. Error: xxx Failed to deploy/update model in node(%s), %s | Locate and rectify the fault based on the error information. |
| Normal | Service instances deleted from resource pool xxx. Model in node(%s) deleted. | - |
| Normal | Service instances stopped in resource pool xxx. Model in node(%s) stopped. | - |
| Abnormal | An error occurred in the edge service. Error: Abnormal edge pool or edge node xxx Update service status to abnormal, the edge node/group(%s) may be abnormal. | Check whether the edge pool or edge node is normal. |
| Abnormal | An error occurred in the edge service. Error: The instance does not exist. Update service status to abnormal, deployment is not exist. | Change the instance and try again. |
| Normal | The instance on the current edge node is in the xxx state. For details, see xxx. Instance is %s in node(%s), %s | - |
| Normal | The edge service is in the xxx state. Service status is %s. | - |
| Abnormal | The batch service failed. Try again later. Error: xxx Failed to %s batch service, retry later. Error message: %s. | Locate and rectify the fault based on the error information. |
| Normal | The service has been executed. Service stopped automatically after running. | - |
| Abnormal | Failed to stop the service. Error: xxx Failed to stopped service, error message: %s | Locate and rectify the fault based on the error information. |
| Normal | The subscription license xxx is to expire. Impending expiration notice: %s | - |
| Normal | Service xxx started. Service %s started successfully. | - |
| Abnormal | Failed to start service xxx. Service %s started failed. | For details about how to locate and rectify the fault, see FAQ. |
| Abnormal | Service deployment timed out. Error: xxx Deploying timeout, details: %s | Locate and rectify the fault based on the error information. |
| Abnormal | Failed to start the service. Error: xxx Service %s started failed, error message: %s | Locate and rectify the fault based on the error information. |
| Normal | Instance xxx deleted. Delete service instance %s success | - |
| Abnormal | Failed to delete instance xxx. Error: xxx Failed to delete service instance %s, error message: %s | Locate and rectify the fault based on the error information. |
| Normal | Failed to update the service. The update has been rolled back. Failed to update service, rollback succeeded. | - |
| Abnormal | Failed to update the service. The rollback failed. Failed to update service, rollback failed. | Contact technical support. |
During service deployment and running, key events can both be manually and automatically refreshed.
Viewing Events
- In the left navigation pane of the ModelArts management console, choose Service Deployment > Real-Time Services or Batch Services or Edge Services. In the service list, click the name or ID of the target service to go to its details page.
- View the events on the Events tab page.
Last Article: Starting, Stopping, Deleting, or Restarting a Service
Next Article: Inference Specifications
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.