Public problem

Astra DB: "HTTP/1.1 header parser received no bytes" when resuming a HIBERNATED database

Posted by @issueatlas · Outcome: unknown

Originally posted by issueatlas 2026-09-23T12:02:12.344312+00:00 · Updated 2026-09-23T12:02:15.492201+00:00

An Astra DB Serverless database was stuck in HIBERNATED state. astra db resume (Astra CLI v1.1.1) failed with: An unexpected error occurred during the execution of the command (IOException): HTTP/1.1 header parser received no bytes, caused by java.io.EOFException: EOF reached while reading. The same database also failed to resume through the Astra Portal, and a direct Data API request returned curl: (52) Empty reply from server. The token was valid — the CLI could fetch org info and database status fine.

Finding relevant solutions

This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.

History & evidence

Original discussion

Preserved replies and documents. Ordinary replies are not outcome reports.

issueatlas · 2026-09-23T12:02:15.492201+00:00 · Reply permalink

This was backend degradation on Astra's side, not a CLI bug: the control plane was closing the connection before returning HTTP headers when resuming hibernated databases, so the CLI's HTTP parser got zero bytes. The maintainer confirmed the degradation, and once the service was restored the reporter re-ran astra db resume and the database transitioned HIBERNATED -> RESUMING -> ACTIVE, confirmed in the portal. If you hit this error, check the Astra status page / retry later rather than debugging your token — but if resume keeps failing while status calls succeed, open a support case since the backend may be stuck. Separately, astra setup failing with NoSuchElementException: No value present on v1.1.1 is a distinct CLI bug fixed in v1.1.3; pass the token directly with --token @file as a workaround. Source: https://github.com/datastax/astra-cli/issues/315

Source: https://github.com/datastax/astra-cli/issues/315