Charts: [stable/jenkins] Readiness Probe Failed

[salman-hayder]

While installing stable/jenkins, facing this error
Readiness probe failed: Get http://192.168.13.41:8080/login: net/http: request canceled (Client.Timeout exceeded while awaiting headers
Any idea how to resolve it?
I'm using kubernetes based remote cluster using kubectl.

[kddejong]

similar issue and I have what looks to be a weird readiness and liveness url.

Liveness:   http-get http://:http/login delay=90s timeout=5s period=10s #success=1 #failure=12
Readiness:  http-get http://:http/login delay=60s timeout=1s period=10s #success=1 #failure=3

Oops my mistake. Unrelated issue.

[yenchen-liu]

How much memory do you allocate? I solved this problem after allocating 1G memory.

[salman-hayder]

I allocated 8GB but still same issue...

[yenchen-liu]

Turn off HealthProbes to prevent from the pods being reset by k8s. Then observe the pod log and status.
Use describe nodes to check the memory settings

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[stale[bot]]

This issue is being automatically closed due to inactivity.

[NiuZhuang]

similar issue and I have what looks to be a weird readiness and liveness url.

Liveness:   http-get http://:http/login delay=90s timeout=5s period=10s #success=1 #failure=12
Readiness:  http-get http://:http/login delay=60s timeout=1s period=10s #success=1 #failure=3

Oops my mistake. Unrelated issue.

Same issue here. Failed to helm install jenkins. Did you fix it?

[ayk33]

I seem to be running across the same issue. Looking at events for my jenkins deployment just shows that the readiness probe failed. Anyone else figure out the root cause of this? Could this be an issue with latest? I didn't notice this issue happening before.

2m 2m 1 jenkins-858f9695d7-gdtsl.1574fd231f31c959 Pod spec.containers{jenkins} Warning Unhealthy kubelet, <node_name> Liveness probe failed: Get http://<ip of pod>:8080/login: read tcp <unknown ip>:34216-><pod_ip>:8080: read: connection reset by peer
2m 1d 3 jenkins-858f9695d7-gdtsl.1574966ff3338a7f Pod spec.containers{jenkins} Normal  Pulled    kubelet, <node_name> Successfully pulled image "jenkins/jenkins:lts"
2m 1d 3 jenkins-858f9695d7-gdtsl.1574966fffce0346 Pod spec.containers{jenkins} Normal  Started   kubelet, <node_name> Started container
2m 1d 3 jenkins-858f9695d7-gdtsl.1574966ff79ad2d7 Pod spec.containers{jenkins} Normal  Created   kubelet, <node_name> Created container
1m 1d 4 jenkins-858f9695d7-gdtsl.1574967eb4c32924 Pod spec.containers{jenkins} Warning Unhealthy kubelet, <node_name> Readiness probe failed: Get http://:8080/login: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

[coderiseio]

I have encountered the same error. After investigating, I found out that it's just a matter of waiting a few minutes until it extracts the war file to the mounted volume. This can sometimes take up to 5-10 minutes, depending upon disk iops. You can mount the same volume to a different container like busybox and run 'du -sh' to track progress. You can check the pod logs as well.