Slaves do not join the cluster

[jhagai]

Hello, I just cloned and ran the project using docker compose.
However, the only node in my cluster (displayed in the management UI is rabbit1@rabbit1).
All the containers are started (I can see them with docker ps and execute commands on them).
Any idea?

[jhagai]

I run docker desktop 2.3.0.3 (on macos)
Docker engine 19.03.8
Compose: 1.25.5

[nadley]

Hi @jhagai,

I run on the same issue, from my first investigation it is related to the random delay the node will wait before proceeding registration.

rabbit1_1  | 2020-07-15 14:30:44.445 [info] <0.269.0> Will wait for 59474 milliseconds before proceeding with registration...

Assuming that the other nodes have a lower delay :

rabbit2_1  | 2020-07-15 14:30:45.466 [info] <0.269.0> Will wait for 20277 milliseconds before proceeding with registration...
rabbit3_1  | 2020-07-15 14:30:45.494 [info] <0.269.0> Will wait for 13363 milliseconds before proceeding with registration...

So when they try to reach the cluster rabbit1 is not yet ready to handle cluster initialization and we have the following logs :

rabbit3_1  | 2020-07-15 14:30:58.862 [warning] <0.269.0> Could not auto-cluster with node rabbit@rabbit1: {badrpc,nodedown}
rabbit3_1  | 2020-07-15 14:30:58.865 [warning] <0.269.0> Could not auto-cluster with node rabbit@rabbit2: {badrpc,nodedown}
rabbit3_1  | 2020-07-15 14:30:58.868 [warning] <0.269.0> Could not auto-cluster with node rabbit@rabbit3: {badrpc,nodedown}

rabbit2_1  | 2020-07-15 14:31:05.748 [warning] <0.269.0> Could not auto-cluster with node rabbit@rabbit1: {badrpc,nodedown}
rabbit2_1  | 2020-07-15 14:31:05.753 [warning] <0.269.0> Could not auto-cluster with node rabbit@rabbit2: {badrpc,nodedown}
rabbit2_1  | 2020-07-15 14:31:05.757 [warning] <0.269.0> Could not auto-cluster with node rabbit@rabbit3: {badrpc,nodedown}

For the moment I'm looking for a solution but I haven't yet found one, if I found one I'll share it with you ;-)

[myung16]

running into the same issue! any suggestions would be appreciated

[robertofalk]

HI @nadley , @jhagai ,

did you manage to find a solution for this problem?
Thanks!

[robertofalk]

HI @nadley , @jhagai ,

I manage to reproduce the problem. When running docker-compose up, everything works as expected, but when using the new docker compose up (since docker compose is now in the Docker CLI), I get random behaviour, since as mentioned above, rabbit1 is still not running when rabbit2 and rabbit3 try to connect.