Log Store Unavailable
URI: https://docs.ankatech.co/errors/log-store-unavailable
HTTP Status: 502 Bad Gateway
When you see this
A platform log search was admitted, but the platform log store did not return a usable answer, so no log line is returned. The search is still recorded in the platform audit trail, with the outcome LOG_STORE_UNAVAILABLE. The response names the log store and nothing else: it relays no message, host, index or credential from the store.
The Admin API answers this when the log store:
- could not be reached;
- presented a certificate that does not verify against the platform CA for the log store's name, a valid certificate for another name included;
- answered with any status other than 200;
- did not answer within 10 seconds;
- answered with more than 8 MiB.
The Admin API itself stays ready: every other endpoint answers as before.
Common Causes
- The log store is restarting, for example while an upgrade is applied.
- The log store's credential for the Admin API was re-minted and not yet reconciled into the store.
- A very broad search over a busy window took longer than 10 seconds.
Response Example
{
"type": "https://docs.ankatech.co/errors/log-store-unavailable",
"title": "Log Store Unavailable",
"status": 502,
"detail": "The platform log store did not return a usable answer; no log entry was returned. Retry later.",
"instance": "/api/v3/admin/platform/logs",
"timestamp": 1760348487,
"extensions": {
"requestId": "7c9e6679-7425-40de-944b-e07fc1f90ae7"
}
}
Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.
How to Resolve
- Retry after a short wait; a restart of the log store ends on its own.
- If it persists, run
envctl.sh <env> health: its log-pipeline section reports whether the store answers and whether it is still receiving lines. The nextenvctl.sh <env> upreconciles the store's users with their secrets. - Narrow a search that may be timing out: a shorter window, a service or a level.
Operations that emit it
| Method | Endpoint |
|---|---|
| GET | /api/v3/admin/platform/logs |
GET /api/v3/admin/platform/logs/sources does not emit it: when the store cannot be read it answers 200 with discoveryComplete: false.
Related Errors
- Log Search Audit Unavailable (503) - the search could not be recorded in the audit trail
- Upstream Service Unavailable (502) - another internal upstream failed
For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.