Node-collector-machine-sections pod CrashLoopBack

Troubleshooting
, ,
1

CMK version:
2.1.0

OS version:
Kubernetes 1.23.3

Error message:

image
image1337×284 42.7 KB

NAME READY STATUS RESTARTS AGE
cluster-collector-78cd76fdc6-46kgz 1/1 Running 0 26m
node-collector-container-metrics-2f22q 2/2 Running 0 26m
node-collector-container-metrics-4dpsj 2/2 Running 0 26m
node-collector-container-metrics-dpwc9 2/2 Running 0 26m
node-collector-machine-sections-m2m95 0/1 CrashLoopBackOff 9 (2m42s ago) 25m
node-collector-machine-sections-msdpl 0/1 CrashLoopBackOff 9 (2m34s ago) 25m
node-collector-machine-sections-t558v 0/1 CrashLoopBackOff 6 (3m3s ago) 9m57s

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
cluster-collector ClusterIP 10.102.207.187 80/TCP 27m
cluster-collector-nodeport NodePort 10.101.68.24 30950:30950/TCP 27m

Is there anything else we need to configure to get this going ?

Node-collector-machine-sections Pods getting in CrashbackLoopOff in Kubernetes
2

Is this Kubernetes setup on-premise or managed ?
What is the container runtime used in your setup?
Are the node-collector-machine-sections always in CrashLoopBackOff status ?
Did you installed the cluster-collector and node-collector as mentioned in this article?

https://kb.checkmk.com/display/KB/Debugging+the+kubernetes+-+k8s+special+agent#Debuggingthekubernetesk8sspecialagent-InstallationofCheckmkClusterCollectors(a.k.aCheckmkKubernetesagent)

3

Hi

No, we did not use the helm chart, we used the howto on the docs section. I will try the helm chart.

k8s is on prem

We use containerd

4

Ok, please usethe steps in this video: Episode 26: Monitoring Kubernetes with Checkmk - YouTube

5

Thanks, howto worked and all is good with helm.

I do get this warning FYI:
W0525 15:42:08.537912 1050697 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0525 15:42:08.538715 1050697 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
W0525 15:42:08.538743 1050697 warnings.go:70] policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+

6

That’s just a warning. More info here: PodSecurityPolicy Deprecation: Past, Present, and Future | Kubernetes

2 Likes
7

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.