Troubleshooting
SUSE Observability Self-hosted
Last updated
SUSE Observability Self-hosted
Last updated
Here is a quick guide for troubleshooting the startup of SUSE Observability:
Check that the install completed successfully and the release is listed:
Check that all pods in the SUSE Observability namespace are running:
In a first deployment it can be that containers in several pods restart a few times, because they are waiting for other pods to start up and be in the ready
state. This can be delayed due to scheduling and docker image pulling delays.
Pods that are in pending
state are usually an indication of a problem:
The pod is unschedulable due to lack of resources in the cluster. If a cluster auto-scaler is active it will often be able to resolve this automatically, otherwise manual intervention is needed to add more nodes to the cluster
The pod is unschedulable, there are nodes it would fit on, but those nodes have taints
that the pod doesn not tolerate. To solve this more nodes can be added that don't have the taints, but SUSE Observability can also be to tolerate certain taints and run on the tainted nodes.
The pod is waiting for the Persistent Volumes (PVs) to be mounted. A cause can be that the SUSE Observability Helm chart doesn't specify a storageClassName
but relies on the cluster having a default storage class. When there is no default for the cluster it's required to via the Helm values of SUSE Observability.
For pods with state ImagePullBackOff
also check the exact error message, common causes are:
An incorrect username/password used to pull the images
Connecting to the docker registry failed, this can be due to authentication issues or connectivity issues (firewalls, air-gapped installations)
A typo in the overridden docker image registry URL
To find out a more detailed cause for the Pending
, ImagePullBackOff
or CrashLoopBackOff
states use this command:
The output contains an event
section at the end which usually contains the problem. It also has a State
section for each container that has more details for termination of the container.
When you are a prime customer, reach out to SUSE Observability support at to get help setting up SUSE Observability in your local cluster. Use to collect information about your instance for the support team.
In case the above steps did not resolve the issue, there is an available.