cube-js/cube · error
cannot parse status probe address
Error message
cannot parse status probe address
What it means
A hard expect() panic while starting the HTTP status probe server: the configured probe address string (from the Cube Store status-probe configuration, e.g. CUBESTORE_STATUS_PROBE_ADDRESS) could not be parsed as a SocketAddr. The process aborts during serve_status_probes startup because the health endpoints cannot bind.
Source
Thrown at rust/cubestore/cubestore/src/http/status.rs:33
None => return,
};
let p = match RouterProbes::try_new(c) {
Some(p) => p,
None => return,
};
let pc = p.clone();
let l = warp::path!("livez").and_then(move || {
let pc = pc.clone();
async move { status_probe_reply("liveness", pc.is_live().await) }
});
let r = warp::path!("readyz").and_then(move || {
let p = p.clone();
async move { status_probe_reply("readiness", p.is_ready().await) }
});
let addr: SocketAddr = addr.parse().expect("cannot parse status probe address");
match warp::serve(l.or(r)).try_bind_ephemeral(addr) {
Ok((addr, f)) => {
log::info!("Serving status probes at {}", addr);
tokio::spawn(f);
}
Err(e) => {
log::error!("Failed to serve status probes at {}: {}", addr, e);
}
}
}
pub fn status_probe_reply(probe: &str, r: Result<(), CubeError>) -> Result<StatusCode, Infallible> {
match r {
Ok(()) => Ok(StatusCode::OK),
Err(e) => {
log::warn!("{} probe failed: {}", probe, e.display_with_backtrace());
Ok(StatusCode::INTERNAL_SERVER_ERROR)
}View on GitHub (pinned to 7d981676b3)
Solutions
- Set the probe address to a valid ip:port or host:port value such as 0.0.0.0:3306
- Check for typos or missing ports in the status probe address configuration
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at rust/cubestore/cubestore/src/http/status.rs:33 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of cube-js/cube@7d981676b3 (2026-09-02).
Data as JSON: /api/errors/3c579b0a276210d2.
Report an issue: GitHub.