Prometheus in CrashloopBackOff for corrupted blocks in RHOCP 4
Issue
-
Prometheus pod is in CrashLoopBackOff with the error:
$ oc logs <prometheus pod> -c prometheus ... level=error ts=2020-02-07T08:51:28.789897822Z caller=main.go:582 err="Opening storage failed unexpected end of JSON input" ... -
Or when the
meta.jsonis not present with the error:level=error ts=2023-11-13T17:25:52.827Z caller=main.go:764 err="opening storage failed: block dir: \"/data/01HF45D5YH28HW056J1P3Z4Y6G\": open /data/01HF45D5YH28HW056J1P3Z4Y6G/meta.json: no such file or directory" -
Metrics older than 2 hours cannot be seen in the Openshift Console.
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 3.11
- Red Hat OpenShift Container Platform (RHOCP)
- 4
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.