Difference between revisions of "Kubelet logs: /var/log/kubelet.log"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 12: | Line 12: | ||
* <code>[[Started: Started container]]</code> | * <code>[[Started: Started container]]</code> | ||
* <code>[[Killing: Stopping container]]</code> | * <code>[[Killing: Stopping container]]</code> | ||
| − | * [[Karpenter logs]] | + | * <code>[[Karpenter logs]]</code> |
| − | * [[Kubernetes troubleshooting]] | + | * <code>[[Kubernetes troubleshooting]]</code> |
| − | * [[DNSConfigForming]] | + | * <code>[[DNSConfigForming]]</code> |
| + | * <code>[[docker logs kubelet]]</code> | ||
== See also == | == See also == | ||
Latest revision as of 11:56, 28 February 2024
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.
E1122 21:44:49.860990 2153 remote_runtime.go:334] "ContainerStatus from runtime service failed" err="rpc error: code = DeadlineExceeded desc = context deadline exceeded" containerID="54f47d9bd75961b31d996d3e1d01d366467750e8b2d9b21af2f528ed2eead846"
kubelet is posting ready status. AppArmor enabled
Related[edit]
NodeHasDiskPressureEvictionThresholdMetNodeHasInsufficientMemoryrebootedStarted: Started containerKilling: Stopping containerKarpenter logsKubernetes troubleshootingDNSConfigFormingdocker logs kubelet
See also[edit]
- Kubernetes log files,
/var/log/kubelet.log, kube-apiserver.log, kubelet.log, kube-scheduler.log, kube-proxy.log kubelet, Pod Lifecycle Event Generator (PLEG), Kubelet conditions,/etc/kubernetes/kubelet.conf, /var/log/kubelet.log, Kubelet Container Runtime Interface (CRI),crictl,context deadline exceeded, E1122, E1124, Starting kubelet, NodeHasDiskPressure, NodeHasInsufficientMemory, rebooted, Node-pressure Eviction, Kubelet logs,manager: kubelet
Advertising:
