Difference between revisions of "Operation timeout: context deadline exceeded"
Jump to navigation
Jump to search
| (28 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{lc}} | ||
| + | error killing pod: failed to "KillContainer" for "you-container" with KillContainerError: "rpc error: code = Unknown desc = [[operation timeout]]: context deadline exceeded" | ||
| − | + | [[Failed to create pod sandbox]]: [[rpc error]]: code = Unknown desc = [[failed to create a sandbox]] for pod "gitlab-runner-[[gitlab-runner]]-6577898d44-r88q6": [[operation timeout: context deadline exceeded]] | |
| + | [[kube-system]] 42m Warning [[Unhealthy]] pod/tiller-deploy-68bb9fb75-kw5r5 Liveness probe failed: Get "http://10.32.0.15:44135/liveness": [[context deadline exceeded]] (Client.Timeout exceeded while awaiting headers) | ||
| + | |||
| + | |||
| + | [[kubelet]] logs | ||
| + | [[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" | ||
| + | |||
| + | [[E1124]] 11:34:32.209953 2159 remote_runtime.go:334] "ContainerStatus from runtime service failed" err="rpc error: code = DeadlineExceeded desc = [[context deadline exceeded]]" containerID="6c91eeec598adb1ad40755e52e819c189c274ad2b38cfd3015ebfd0c558305d3" | ||
| + | |||
| + | [[gitlab-runner]] 49m Warning [[Failed]] pod/runner-zfsetzy9-project-8482115-concurrent-5csbkz [[Error: context deadline exceeded]] | ||
| + | |||
| + | |||
| + | [[containerd]] .../... error="[[failed to stop container]]: context deadline exceeded: unknown" | ||
| + | |||
| + | == Related == | ||
| + | * <code>[[kubectl get events -A]] | grep [[Warning]]</code> | ||
| + | * <code>[[kubectl top node]]</code> | ||
| + | * <code>[[NodeNotReady]]</code> | ||
| + | * <code>[[UnAvailableLoadBalancer]]</code> | ||
| + | * <code>[[FailedKillPod]]</code> | ||
| + | * <code>[[timed out waiting for the condition]]</code> | ||
| + | * <code>[[FailedCreatePodSandBox]]</code> | ||
| + | * [[GKE]]: <code>[[gcloud logging]]</code> | ||
| + | * [[blocked for more than]] | ||
| + | * <code>[[gcloud logging read projects/your-project/logs/kubelet]]</code> | ||
== See also == | == See also == | ||
| + | * {{kubelet}} | ||
* {{K8s tr}} | * {{K8s tr}} | ||
| + | * {{kubectl get events}} | ||
[[Category:K8s]] | [[Category:K8s]] | ||
Latest revision as of 12:57, 14 December 2022
error killing pod: failed to "KillContainer" for "you-container" with KillContainerError: "rpc error: code = Unknown desc = operation timeout: context deadline exceeded"
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create a sandbox for pod "gitlab-runner-gitlab-runner-6577898d44-r88q6": operation timeout: context deadline exceeded
kube-system 42m Warning Unhealthy pod/tiller-deploy-68bb9fb75-kw5r5 Liveness probe failed: Get "http://10.32.0.15:44135/liveness": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
kubelet logs 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"
E1124 11:34:32.209953 2159 remote_runtime.go:334] "ContainerStatus from runtime service failed" err="rpc error: code = DeadlineExceeded desc = context deadline exceeded" containerID="6c91eeec598adb1ad40755e52e819c189c274ad2b38cfd3015ebfd0c558305d3"
gitlab-runner 49m Warning Failed pod/runner-zfsetzy9-project-8482115-concurrent-5csbkz Error: context deadline exceeded
containerd .../... error="failed to stop container: context deadline exceeded: unknown"
Related[edit]
kubectl get events -A | grep Warningkubectl top nodeNodeNotReadyUnAvailableLoadBalancerFailedKillPodtimed out waiting for the conditionFailedCreatePodSandBox- GKE:
gcloud logging - blocked for more than
gcloud logging read projects/your-project/logs/kubelet
See also[edit]
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- K8s troubleshooting:
kubectl logs, kubectl top, kubectl get events -A, kubectl describe pod, Liveness, Readiness,Kubernetes events, Pulling image, OOMKilled, ProbeWarning, Reason,FailedScheduling,errImagePull, ImagePullBackOff, Kubelet conditions:MemoryPressure, DiskPressure, KubeletHasSufficientPID, KubeletReady, kubectl [ debug | attach | exec ] kubectl cluster-info dump, SimKube, KWOK kubectl get events, OOMKilling, FailedKillPod, SuccessfulDelete, SuccessfulCreate, NoPods, Warning, Critical, NodeSysctlChange, FailedAttachVolume, FailedMount, UnAvailableLoadBalancer, FailedCreatePodSandBox, InvalidDiskCapacity, Scheduled, NetworkNotReady, Evict, Killing, SuccessfulReconcilied, FailedToUpdateEndpointSlices, BackendNotFound, FailedScheduling, ProvisioningFailed
Advertising:
