- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Hello Jess,
The "MISSING" status for the task during describe-tasks
CLI operation occurs either when you provide an incorrect task ID or when ECS had already reaped your stopped task. To find out details about the task that has already been reaped, you can contact AWS Premium Support and they will be able to provide you with the information.
If your issue is consistent, you can re-create the task and find out the reason for the task failure right after it has moved to STOPPED state. You can also find the reason for the task failure in ECS service events as explained in this doc.
I hope this information is helpful to you. Please reply if you have further questions related to this issue.
i'm using app mesh and cloud map (ApiGW => vpc link => NLB => virtual GW task => web app task) envoy image public.ecr.aws/appmesh/aws-appmesh-envoy:v1.21.1.0-prod health check with : curl -s http://localhost:9901/server_info | grep state | grep -q LIVE
the web task that contain x-ray, envoy and myapp containers fails each couple of hours
tasks fail around midnight
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
Did you run this command just when the task stop? Or after a while? Could you please share the task ID?