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

All pods in restart loop and status of Waiting: **CrashLoopBackOf** #32

Open
braytonstafford opened this issue Feb 26, 2017 · 1 comment

Comments

@braytonstafford
Copy link

I am running into a similar situation to what was reported in issue #21 where all of my pods for the 3 replicas, admin, and proxy are restarting and showing a status of :

Waiting: CrashLoopBackOf

When running a describe on the pods I'm getting the following warnings:

$ kubectl describe pod rethinkdb-replica-1-3259957792-gp4rv

spec.containers{rethinkdb}	Warning		Unhealthy	Readiness probe failed: 2017/02/26 02:32:04 gorethink: Wrong password

Warning	Unhealthy	Liveness probe failed: 2017/02/26 02:33:04 gorethink: Wrong password

Warning	FailedSync	Error syncing pod, skipping: failed to "StartContainer" for "rethinkdb" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=rethinkdb pod=rethinkdb-proxy-3903914381-mdj4n_default(2ab36348-fbcb-11e6-a270-42010af0007c)"

Any help is appreciated and if I need to provide more info i'll be happy to. I'm very new to kubernetes. Thanks in advance

@rosskukulinski
Copy link
Owner

@braytonstafford which image are you using? It looks like the Liveness/Readiness probes are failing due to a wrong password. In the newest images we added a go-binary for verifying the DB is actually working, but it doesn't support RethinkDB username/password login.

For now I would recommend changing the Liveness/Readiness probes from /probe to /ready-probe.sh.

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

2 participants