-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Client node remains in down state after restarting host #5589
Comments
@preetapan Just checked 0.9.1-rc1 - and yes, looks like bug has gone. |
Thanks for confirming @uzzz |
Facing a similar issue while doing it in vagrant-cluster, client went down just after restarting nomad. Created a host_volume inside client.hcl and restarted it. Can someone help, I'm new to using hashicorp tools? |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
0.9.0
Operating system and Environment details
Ubuntu 16.04.5 LTS with systemd
Issue
I have a single client node and after I restart server it never gets back to "ready" state. The only way to make it work again is to run "docker container prune" and then restart nomad again.
State after reboot:
Reproduction steps
docker ps -a
shows container(s) inExited
statedown
stateNomad Client logs
The text was updated successfully, but these errors were encountered: