openai/codex · error · anyhow::Error

timed out waiting for pid lock {}

Error message

timed out waiting for pid lock {}

What it means

Error "timed out waiting for pid lock {}" thrown in openai/codex.

Source

Thrown at codex-rs/app-server-daemon/src/backend/pid.rs:385

        };
        drop(reservation_lock);
        Ok(state)
    }

    async fn acquire_reservation_lock(&self) -> Result<fs::File> {
        let reservation_lock = fs::OpenOptions::new()
            .create(true)
            .truncate(false)
            .write(true)
            .open(&self.lock_file)
            .await
            .with_context(|| {
                format!("failed to open pid lock file {}", self.lock_file.display())
            })?;
        let lock_deadline = tokio::time::Instant::now() + START_TIMEOUT;
        while !try_lock_file(&reservation_lock)? {
            if tokio::time::Instant::now() >= lock_deadline {
                bail!(
                    "timed out waiting for pid lock {}",
                    self.lock_file.display()
                );
            }
            sleep(STOP_POLL_INTERVAL).await;
        }
        Ok(reservation_lock)
    }

    #[cfg(unix)]
    async fn open_stderr_log(&self) -> Result<fs::File> {
        let stderr_log_file = stderr_log_file_for_pid_file(&self.pid_file);
        fs::OpenOptions::new()
            .create(true)
            .truncate(true)
            .write(true)
            .open(&stderr_log_file)
            .await

View on GitHub (pinned to 339751715c)

When it happens

Trigger: Thrown at codex-rs/app-server-daemon/src/backend/pid.rs:385 when the library encounters an invalid state.

Common situations: See trigger scenarios.

Understand the failure class

• Timeouts: ETIMEDOUT, deadlines, and hung requests — what actually expires when a request times out.

AI-assisted analysis of openai/codex@339751715c (2026-08-25). Data as JSON: /api/errors/0fe70b47b0612b9d. Report an issue: GitHub.