[PCA 3.x] Prometheus Pod in CrashLoopBack State
(Doc ID 2970102.1)
Last updated on OCTOBER 13, 2023
Applies to:
Private Cloud Appliance X9-2 - Version Not Applicable to Not Applicable [Release NA]Information in this document applies to any platform.
Symptoms
Unable to start sauron-sauron-prometheus pod and going to CrashLoopBackOff state.
[root@pcamn01 ~]# kubectl get pods -n sauron | grep sauron-sauron-prometheus-0
NAME READY STATUS RESTARTS AGE
sauron-sauron-prometheus-0-9b5946746-ldzxm 2/3 CrashLoopBackOff 29 126m
The snippet of the "kubectl describe" output:
[root@pcamn01 ~]# kubectl describe pod sauron-sauron-prometheus-0-9b5946746-ldzxm -n sauron
Containers:
prometheus:
<snip>
State: Waiting
Reason: CrashLoopBackOff <<<<<<<<
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Thu, 17 Aug 2023 09:46:22 +0000
Finished: Thu, 17 Aug 2023 09:46:22 +0000
The Snippet of the "kubectl logs" output:
[root@pcamn01 ~]# kubectl logs sauron-sauron-prometheus-0-9b5946746-ldzxm -n sauron -c prometheus
level=info ts=2023-08-17T09:46:22.162Z caller=main.go:755 msg="Notifier manager stopped"
level=info ts=2023-08-17T09:46:22.162Z caller=main.go:549 msg="Scrape discovery manager stopped"
level=error ts=2023-08-17T09:46:22.162Z caller=main.go:764 err="opening storage failed: block dir: \"/prometheus/01H6BXX9X851R2HXW1JBR2WN44\": open /prometheus/01H6BXX9X851R2HXW1JBR2WN44/meta.json: no such file or directory"
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |