Consul broken ? about cluster-lab

[firecyberice]

Please paste the output of cluster-lab health.
Does eth0.200 exist?

[nsteinmetz]

Hi,

$ sudo cluster-lab health

Internet Connection
  [PASS]   eth0 exists
  [PASS]   eth0 has an ip address
  [PASS]   Internet is reachable
  [PASS]   DNS works

Networking
  [FAIL]   eth0.200 exists
  [FAIL]   eth0.200 has correct IP from vlan network
  [FAIL]   Cluster leader is reachable
  [FAIL]   eth0.200 has exactly one IP
  [PASS]   eth0.200 has no local link address
  [PASS]   Avahi process exists
  [FAIL]   Avahi is using eth0.200
Cannot find device "eth0.200"
  [FAIL]   Avahi cluster-leader.service file exists
Cannot find device "eth0.200"

DNSmasq
  [PASS]   dnsmasq process exists
  [FAIL]   /etc/dnsmasq.conf backup file exists

Docker
  [PASS]   Docker is running
  [FAIL]   Docker is configured to use Consul as key-value store
  [FAIL]   Docker is configured to listen via tcp at port 2375
  [FAIL]   Docker listens on  via tcp at port 2375 (Docker-Engine)

Consul
  [PASS]   Consul Docker image exists
  [FAIL]   Consul Docker container is running
  [FAIL]   Consul is listening on port 8300
  [FAIL]   Consul is listening on port 8301
  [FAIL]   Consul is listening on port 8302
  [FAIL]   Consul is listening on port 8400
  [FAIL]   Consul is listening on port 8500
  [FAIL]   Consul is listening on port 8600
  [FAIL]   Consul API works
  [PASS]   No Cluster-Node is in status 'failed'
  [FAIL]   Consul is able to talk to Docker-Engine on port 7946 (Serf)

Swarm
  [FAIL]   Swarm-Join Docker container is running
  [FAIL]   Swarm-Manage Docker container is running
  [PASS]   Number of Swarm and Consul nodes is equal which means our cluster is healthy

As output of ifconfig, eth0.200 no longer exists :(

Thanks,
Nicolas

[nsteinmetz]

If I do a cluster-lab stop and then cluster-lab start, then eth0.200 exists but consul still fails to start.

My master is now 192.168.200.31 but consul tries to connect on 192.168.200.1. It seems to be now my "worker 4".

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 systemctl cluster-lab start|stop and cluster-lab start|stop ?

[Govinda-Fichtner]

The important thing is that you first start what will become your leader
node... It will announce its presence via Avahi. After one or two minutes
you can start the follower nodes which then should join the leader to form
a cluster.

Stopping the Cluster-Lab on all nodes was the right thing to do as it
resets the configuration on all nodes.
Am 28.05.2016 22:20 schrieb "Nicolas Steinmetz" [email protected]:

If I do a cluster-lab stop and then cluster-lab start, then eth0.200 exists
but consul still fails to start.

My master is now 192.168.200.31 but consul tries to connect on 192.168.200.1.
It seems to be now my "worker 4".

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 systemctl cluster-lab start|stop and
cluster-lab
start|stop ?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#42 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAkiJtzUOM0pV89GEN6T6sso-HkZOh7Gks5qGKN8gaJpZM4Io46x
.

[nsteinmetz]

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 systemctl cluster-lab stop and start but seems that I had the docker issue (cf #36) and the eth0.200 issue that was no longer working.

[Govinda-Fichtner]

Seems this issue is solved.

[nsteinmetz]

Yes indeed ; I forgot to close it - I was only expecting a answer on the difference between systemctl cluster-lab stop/start vs cluster-lab stop/start.