-
Notifications
You must be signed in to change notification settings - Fork 18
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
Consul broken ? #42
Comments
Please paste the output of |
Hi,
As output of Thanks, |
If I do a My master is now I stopped cluster-lab on all nodes, then restarted cluster-lab from master node. From this point it worked well. Is there any difference between |
The important thing is that you first start what will become your leader Stopping the Cluster-Lab on all nodes was the right thing to do as it If I do a cluster-lab stop and then cluster-lab start, then eth0.200 exists My master is now 192.168.200.31 but consul tries to connect on 192.168.200.1. I stopped cluster-lab on all nodes, then restarted cluster-lab from master Is there any difference between systemctl cluster-lab start|stop and — |
Hmm thanks, in fact, my issue happened due to an electrical issue at home. So all nodes restarted when electricity was back. I thought that the 2mn issue was only for the 1st run and that for 2nd and later run, there were not this 2mn delay. I understand better now ; thanks ! But I tried to restart it (but not with shutting down all nodes indeed) with |
Seems this issue is solved. |
Yes indeed ; I forgot to close it - I was only expecting a answer on the difference between |
Hi,
I started my picosluter and clusterlab with
sd-card-rpi-v0.5.14.img
and upgraded it.As notice in #36, I saw that docker was no longer working. So I removed the
/etc/docker/daemon.json
file but anyway. Docker and Cluster-lab starts well but consul container is always restarting.For what I can see on my master node:
and:
What else do you need ? How can I fix it ?
Thanks,
Nicolas
The text was updated successfully, but these errors were encountered: