Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

readyness probe fails #2

Open
durandom opened this issue Nov 3, 2017 · 2 comments
Open

readyness probe fails #2

durandom opened this issue Nov 3, 2017 · 2 comments

Comments

@durandom
Copy link

durandom commented Nov 3, 2017

I havent dug deeper into the why, but with the readyness probe enabled I was not able to deploy the app container (db worked fine)
Then I removed the readyness probe and deployment went through

@douzl
Copy link

douzl commented Apr 17, 2018

the readyness and liveness require updated, I used http replace https and set the timeout as 3 second, the deployment worked well.

@GrahamCP
Copy link

Deploying on Minishift: both liveness and readiness probes failed consistently (5 attempts); see event log below. Fixed by increasing probes' timeout to 120 seconds (but looks like 2 seconds might be enough).

Scheduled               default-scheduler        Successfully assigned my-wordpress-site-1-tlwqq to localhost
SuccessfulMountVolume   kubelet, localhost       MountVolume.SetUp succeeded for volume "pv0040" 
SuccessfulMountVolume   kubelet, localhost       MountVolume.SetUp succeeded for volume "default-token-h66lk" 
Pulling                 kubelet, localhost       pulling image "172.30.1.1:5000/wordpress/my-wordpress-site-img@sha256:54e381ef5a90399980568f72add78a36ab8e3c1f18ed5add7a0363564717cbf9"
Pulled                  kubelet, localhost       Successfully pulled image "172.30.1.1:5000/wordpress/my-wordpress-site-img@sha256:54e381ef5a90399980568f72add78a36ab8e3c1f18ed5add7a0363564717cbf9"
Created                 kubelet, localhost       Created container
Started                 kubelet, localhost       Started container
Unhealthy               kubelet, localhost       Liveness probe failed: Get http://172.17.0.6:8080/wp-admin/install.php: dial tcp 172.17.0.6:8080: getsockopt: connection refused
Unhealthy               kubelet, localhost       Readiness probe failed: Get http://172.17.0.6:8080/wp-admin/install.php: dial tcp 172.17.0.6:8080: getsockopt: connection refused
Unhealthy               kubelet, localhost       Liveness probe failed: Get http://172.17.0.6:8080/wp-admin/install.php: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Unhealthy               kubelet, localhost       Readiness probe failed: Get http://172.17.0.6:8080/wp-admin/install.php: net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Killing                 kubelet, localhost       Killing container with id docker://wordpress:Container failed liveness probe.. Container will be killed and recreated.
BackOff                 kubelet, localhost       Back-off restarting failed container

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants