kube-ops-view icon indicating copy to clipboard operation
kube-ops-view copied to clipboard

Published 20 hours ago • verified publisher icon hjacobs

Pod restarting due to liveness failure

Open steven-ellis opened this issue 5 years ago • 1 comments

I'm seeing the following at an OpenShift level for the kube-ops-view pod

Liveness probe failed: Get http://10.130.4.158:8080/health: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

Looking at the pods logs I can see the health requests and then a graceful exit 10.130.4.1 - - [2019-10-01 03:04:45] "GET /health HTTP/1.1" 200 115 0.000597 10.130.4.1 - - [2019-10-01 03:04:48] "GET /health HTTP/1.1" 200 117 0.000535 INFO:kube_ops_view.main:Received TERM signal, shutting down.. I'm running this on OpenShift 4.1.3

steven-ellis avatar Oct 01 '19 03:10 steven-ellis

Hi! I have the same problem on EKS (ubuntu 18.04 nodes). CPU and memory usage seems to be OK. What could be the reason for the TERM signal followed by 503 health checks?

ivaanko avatar Jul 10 '20 15:07 ivaanko