ES /docs

QMAws::startTask | ECS failures - job_id: 1025611, task_definition: cupix-pano-postprocessor-product

Service
cupixworks-any-compute-agent
Occurrences
244
Status
Fixing
Confidence
80%
Actionability
44%
Cluster ID
c6afd4dc-ea88-48a7-84ae-0792b3296d3b
First Seen
2026-04-07 11:23 UTC
Last Seen
2026-08-04 21:51 UTC
Actions
현재 상태 fixing 에서는 실행할 액션이 없습니다.

QMAws::startTask | ECS failures - job_id: 1025611, task_definition: cupix-pano-postprocessor-product

What Happened#

2026-04-20 23:25:44 UTC에 cupixworks-any-compute-agent 서비스에서 ECS startTask API 호출 시 container instance의 ECS agent 연결 문제로 인해 task 배치가 실패했다. 해당 job(1025611)은 약 3분 후 동일 container instance에서 재시도되어 성공적으로 실행되었다.

Quick Facts#

Field Value
exception.class ECS StartTask Failure
exception.message failures: [{"arn":"...100968f2df2748a8920b1944be34a4cf","reason":"AGENT"}]
top_frame qmAws.ts:197
env production, us-west-2

Timeline#

  1. 2026-04-20T23:25:44Z — Job 1025611 첫 번째 runTask 시도. container instance 100968f2 선택 (ACTIVE, memory 30940 MiB, running 0, pending 0). startTask 호출 시 reason: "AGENT" failure 반환.
  2. 2026-04-20T23:25:44Z — 같은 시각 다른 container instances (e8ca99cf, 6c72fa66)도 평가되었으나 pendingTasksCount == 1이어서 건너뜀. SQS 메시지 삭제되지 않음.
  3. 2026-04-20T23:27:23Z — 두 번째 재시도. 동일 상황 — 다른 instances에 pending tasks 존재하여 task size 0으로 종료.
  4. 2026-04-20T23:29:07Z — 세 번째 시도. container instance 100968f2가 이제 정상 복구됨 (running 0, pending 0). startTask 성공, task ARN ae3c04e78ef9... 할당.

Scoring#

Confidence 80% · Actionability 44%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 11 code refs, 4 log queries
Code path explicitness 3/3 11 file:line refs
Log evidence 2/3 section, query
RCA structure 3/3 3/3 sections
Revision history 0/3 0 revision(s)
Agent execution 3/3 success

Actionability#

Dimension Score Detail
Fix complexity 5/5 trivial
Affected files 1/5 9 file(s)
Single repo 1/3 2 service(s)
Immediate actions 0/3 absent
Testability 0/3 no test info
External dependency 1/3 external deps found
Data migration 3/3 no migration