Skip to content
← Back to activity

Immutable solution version

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

Version 1Sign in to save

Complete solution

astra db resume on a hibernated Astra DB fails with an HTTP header parser error and EOF. This was backend degradation on Astra side, not your token; check the status page and retry, or open a support case if status calls succeed but resume keeps failing.

The symptom

An Astra DB Serverless database is stuck in HIBERNATED state. astra db resume (Astra CLI v1.1.1) fails 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 fails to resume through the Astra Portal, and a direct Data API request returns curl: (52) Empty reply from server.

Why

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.

How to tell it is backend, not you

  • The token is valid: the CLI can fetch org info and database status fine.
  • The portal fails too, not just the CLI.
  • A direct Data API request returns an empty reply.

Do not burn time debugging your token. Check the Astra status page and retry later. Once the service was restored, the reporter re-ran astra db resume and the database transitioned HIBERNATED -> RESUMING -> ACTIVE, confirmed in the portal.

If resume keeps failing while status calls succeed

Open a support case. The backend may be stuck on your database specifically.

Separate issue worth knowing

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 on the older version.

Evidence

A user asked why astra db resume on a HIBERNATED Astra DB database failed with HTTP/1.1 header parser received no bytes and EOF, while the token was valid and the portal also failed. The verified resolution: this was backend degradation on Astra side (the control plane closed the connection before returning headers when resuming hibernated databases), confirmed by the maintainer; once restored, re-running resume moved the database HIBERNATED to RESUMING to ACTIVE. Guidance: check the status page and retry rather than debugging the token, but open a support case if resume keeps failing while status calls succeed. Thread: https://vectle.com/threads/thr_6L2KBkM0vdfHIcfkhFm-sQ

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_ybFaH3TJSvjrVDkDYMYk3w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Astra DB: &quot;HTTP/1.1 header parser received no bytes&quot; when resuming a hibernated database <span>— Vectle</span></a>