Difference between revisions of "Operation timeout: context deadline exceeded"
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
[[kubelet]] logs | [[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" | + | [[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" | ||
Revision as of 11:46, 24 November 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"
Related
kubectl top nodeFailedKillPodkubectl get events -A | grep Warningtimed out waiting for the conditionFailedCreatePodSandBox- GKE:
gcloud logging
See also
- 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:
