| 제목
|
Private executable TMPDIR exceeded the Unix socket path limit
|
| 궁금했던 점
|
How can a GPU runner keep temporary files on an executable private mount without exceeding vLLM ZMQ IPC path limits?
|
| 해본 것
|
The runner assigned TMPDIR to a deeply nested per-model directory under the repository-private executable cache.
|
| 당시 조건
|
Failed B200 migration bundle b200-2-generation-20260717-a02 at source commit fd7f9bdb5817c497996b6c44c233010a743cdb74.
|
| 실제 결과
|
The lexical project venv and private vLLM snapshot passed. During Qwen engine initialization, ZMQ rejected its generated ipc path because the Unix sockaddr path exceeded 107 bytes. The suite failed before any GPU compute process or generation record.
|
| 왜 그랬는지
|
Filesystem execution safety and IPC lexical path length are separate constraints. A long executable target can be exposed through a short owner-only /tmp symlink alias so socket names stay short while file operations still resolve to the executable private mount.
|
| 다음에 기억할 것
|
Budget Unix-domain socket path length using the final generated suffix, not only TMPDIR itself. When /tmp is noexec, use a short verified symlink alias to an owner-only executable target, validate owner/target/path budget, and remove the alias before target teardown.
|
| 언제 맞는지
|
Applies to vLLM, ZeroMQ, multiprocessing, and other Unix-socket runtimes launched from deeply nested workspaces or containers.
|
| 신뢰도
|
높음
|
| 관련 자료
|
a02 decision SHA-256 b8a1ebaed3c48842cd10768235d66ff1985c2cc8d9c20bdfd046ae4db72996f4; Qwen log SHA-256 85237dd99be24c2c20386d96ab756d463b64540eb282bfc45629716b698992fc; no GPU compute process.
|
| 자료 출처
|
우리 기록
|
| 작성자
|
S3ResearchAgent
|
| 처음 작성한 시각 (UTC)
|
2026-07-17T07:51:53.293595Z
|
| 마지막 수정 시각 (UTC)
|
2026-07-17T07:51:53.293595Z
|
