tinyhumansai/openhuman · error
{} worker failed to start: {}
Error message
{} worker failed to start: {} What it means
The worker completed the handshake but reported ready=false with its own error string — a startup failure inside the worker process (failed dependency load, bad config) surfaced verbatim. The message after the colon comes from the worker, not the supervisor.
Source
Thrown at src/openhuman/runtime/pool/worker.rs:184
)
};
let mut lines = BufReader::new(reader).lines();
let ready_line = match tokio::time::timeout(HANDSHAKE_TIMEOUT, lines.next_line()).await {
Ok(Ok(Some(line))) => line,
Ok(Ok(None)) => bail!(
"{} worker exited before readiness handshake",
launch.lang.id()
),
Ok(Err(error)) => {
return Err(error).context("reading worker handshake");
}
Err(_) => bail!("{} worker readiness handshake timed out", launch.lang.id()),
};
let ready: PoolReadyLine = serde_json::from_str(&ready_line)
.with_context(|| format!("parsing worker ready line: {ready_line}"))?;
if !ready.ready {
bail!(
"{} worker failed to start: {}",
launch.lang.id(),
ready.error.unwrap_or_else(|| "unknown".to_string())
);
}
if ready.protocol != Some(PROTOCOL_VERSION) {
bail!(
"{} worker protocol mismatch: expected {}, got {:?}",
launch.lang.id(),
PROTOCOL_VERSION,
ready.protocol
);
}
if ready.protocol_token != expected_token {
bail!("{} worker protocol authentication failed", launch.lang.id());
}
tracing::info!(lang = launch.lang.id(), "[runtime_pool] worker ready");
View on GitHub (pinned to 7491200858)
Solutions
- Read the worker-supplied error text to identify the failing step
- Fix the underlying cause (missing package, bad env) and relaunch the pool
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at src/openhuman/runtime/pool/worker.rs:184 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of tinyhumansai/openhuman@7491200858 (2026-08-17).
Data as JSON: /api/errors/94e32f56485b1fa9.
Report an issue: GitHub.