ES /docs

ENOENT: no such file or directory, stat '/tmp/workspace/pointcloud/230110/raw/pointcloud_230110_voxe

Service
cupixworks-any-voxel-agent
Occurrences
1,107
Status
Reported
Confidence
85%
Actionability
28%
Cluster ID
97104612-616d-4be0-b14d-2a7f5519114c
First Seen
2026-06-24 05:32 UTC
Last Seen
2026-08-05 04:22 UTC
Datadog↗ Slack↗
Actions

ENOENT: no such file or directory, stat '/tmp/workspace/pointcloud/230110/raw/pointcloud_230110_voxe

What Happened#

cupixworks-any-voxel-agent (production, ap-southeast-2)가 pointcloud 230110 메시지를 처리하던 중 VoxelManager::calculateVoxels가 voxelCount: NaN으로 종료된 직후 ENOENT: no such file or directory, stat '/tmp/workspace/pointcloud/230110/raw/pointcloud_230110_voxels.csv' 에러를 발생시켰다. 동일 패턴이 같은 날 다수의 pointcloud / capture에서 반복적으로 관측되므로 단발성 환경 문제가 아니라 코드 경로상의 결함이다.

Quick Facts#

Field Value
exception.class Error (ENOENT)
exception.message ENOENT: no such file or directory, stat '/tmp/workspace/pointcloud/230110/raw/pointcloud_230110_voxels.csv'
top_frame applications/agents/packages/cupix-tesla-voxel-agent/src/util/voxel-writer.ts:34
runtime Node.js (TypeScript agent), cupix-tesla-voxel-agent package
env production, region ap-southeast-2, tenant cupix

Affected Teams#

Team / Domain Error Count Impact
endeavourgroup (this cluster, pointcloud 230110) 1 Voxel state는 Error로 마킹되며, 해당 pointcloud의 voxel 산출물이 S3에 업로드되지 않음
같은 서비스 전체 (지난 24h, ENOENT voxels.csv) 20+건 (Datadog) 다수의 capture/pointcloud 처리 실패 — voxelCount: NaN을 동반함

Timeline#

  1. 2026-06-24 14:32:24 KST — BaseService::runByMessage | id: 230110 (SQS 메시지 수신)
  2. 2026-06-24 14:32:25 KST — CPRealityCapture::setCaptureVoxelsParams | pointcloud ID: 230110 - voxelSize: 1, potreeLevelThreshold: 3
  3. 2026-06-24 14:32:25 KST — VoxelManager::calculateVoxels | finished - pointcloud ID: 230110, voxelCount: NaN, numNodes: NaN, numLeaves: NaN
  4. 2026-06-24 14:32:25 KST — ENOENT: no such file or directory, stat '/tmp/workspace/pointcloud/230110/raw/pointcloud_230110_voxels.csv' (cluster first/last seen)

Scoring#

Confidence 85% · Actionability 28%

Confidence#

Dimension Score Detail
Evidence completeness 5/5 15 code refs, 8 log queries
Code path explicitness 3/3 15 file:line refs
Log evidence 3/3 section, query, pattern
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 1/5 critical
Affected files 1/5 15 file(s)
Single repo 1/3 8 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