Difference between revisions of "Unhealthy"
Jump to navigation
Jump to search
| (7 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
| − | |||
| − | [[Readiness]] probe failed: Waiting for elasticsearch cluster to become ready (request params: "wait_for_status=green&timeout=1s" ) Cluster is not yet ready (request params: "wait_for_status=green&timeout=1s" ) | + | [[Readiness]] probe failed: Waiting for elasticsearch cluster to become ready (request params: "wait_for_status=green&timeout=1s" ) [[Cluster is not yet ready]] (request params: "wait_for_status=green&timeout=1s" ) |
| − | + | "message": "(service your-service) (port 1236) is unhealthy in ([[target-group]] arn:aws:elasticloadbalancing:eu-west-1:***:targetgroup/your-tg/de945c5123456) due to (reason [[Health checks]] failed).", "id": "bab160d2-b5d5-4170-91a1-73e92f34b563", "createdAt": 1676632404.784 | |
| − | + | === kubectl describe pods | grep Unhealthy === | |
| + | [[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) | ||
| − | + | your_namespace 26m Warning [[Unhealthy]] pod/elasticsearch-master-1 [[Readiness probe failed]]: Waiting for elasticsearch cluster to become ready (request params: "wait_for_status=green&timeout=1s" )... | |
| − | [[ | + | 13s [[Warning]] Unhealthy pod/[[metrics-server]]-7f4db5fd87-5lwkg [[Readiness probe failed]]: [[HTTP probe failed with statuscode]]: 500 |
| − | |||
| − | |||
| − | |||
== ECS == | == ECS == | ||
| − | service your-service port 3000 is unhealthy in target-group your-tg due to ([[reason Health checks failed with these codes]]: [404]). | + | service your-service port 3000 [[is unhealthy in target-group]] your-tg due to ([[reason Health checks failed with these codes]]: [404]). |
== Related == | == Related == | ||
* <code>[[kubectl get events -A]] | grep [[ClusterUnhealthy]]</code> | * <code>[[kubectl get events -A]] | grep [[ClusterUnhealthy]]</code> | ||
* <code>[[--kubelet-insecure-tls]]</code> | * <code>[[--kubelet-insecure-tls]]</code> | ||
| + | * <code>[[Reason]]</code> | ||
| + | * <code>[[FailedKillPod]]</code> | ||
| + | * <code>[[Killing]]</code> | ||
== See also == | == See also == | ||
| + | * {{kubectl describe pods}} | ||
| + | * {{K8s probes}} | ||
* {{K8s tr}} | * {{K8s tr}} | ||
[[Category:K8s]] | [[Category:K8s]] | ||
Latest revision as of 09:40, 1 May 2024
kubectl get events -A | grep Warning kubectl describe pods | grep Unhealthy
Readiness probe failed: Waiting for elasticsearch cluster to become ready (request params: "wait_for_status=green&timeout=1s" ) Cluster is not yet ready (request params: "wait_for_status=green&timeout=1s" )
"message": "(service your-service) (port 1236) is unhealthy in (target-group arn:aws:elasticloadbalancing:eu-west-1:***:targetgroup/your-tg/de945c5123456) due to (reason Health checks failed).", "id": "bab160d2-b5d5-4170-91a1-73e92f34b563", "createdAt": 1676632404.784
kubectl describe pods | grep Unhealthy[edit]
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)
your_namespace 26m Warning Unhealthy pod/elasticsearch-master-1 Readiness probe failed: Waiting for elasticsearch cluster to become ready (request params: "wait_for_status=green&timeout=1s" )...
13s Warning Unhealthy pod/metrics-server-7f4db5fd87-5lwkg Readiness probe failed: HTTP probe failed with statuscode: 500
ECS[edit]
service your-service port 3000 is unhealthy in target-group your-tg due to (reason Health checks failed with these codes: [404]).
Related[edit]
See also[edit]
kubectl describe pods- K8s probes:
readinessProbe, livenessProbe, StartupProbe, exec, gRPC, HttpGet, tcpSocket, TerminationGracePeriodSeconds - 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
Advertising:
