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

Unable to get secondary node to join cluster. #393

pcon0718 opened this issue Aug 11, 2016 · 1 comment


None yet
1 participant
Copy link

commented Aug 11, 2016


I'm unable to get the second node in my cluster to auto join the cluster using the rabbitmq cookbook with my wrapper script.

The cookbook converges properly on node1 and creates the cluster (In my example: cluster name = cluster). The cookbook on node2 converges properly and attempts to join the cluster however I receive an error stating :

Recipe: rabbitmq::cluster
  * rabbitmq_cluster[[{"name":"rabbit@rabbit1","type":"disc"},{"name":"rabbit@rabbit2","type":"disc"}]] action join[2016-08-11T18:46:24-04:00] WARN: [rabbitmq_cluster] Node is already member of Joining cluster will be skipped.
 (up to date)
  * rabbitmq_cluster[[{"name":"rabbit@rabbit1","type":"disc"},{"name":"rabbit@rabbit2","type":"disc"}]] action set_cluster_name (up to date)
  * rabbitmq_cluster[[{"name":"rabbit@rabbit1","type":"disc"},{"name":"rabbit@rabbit2","type":"disc"}]] action change_cluster_node_type[2016-08-11T18:46:27-04:00] WARN: [rabbitmq_cluster] Skip changing cluster node type : trying to change to same cluster node type
 (up to date)
Recipe: rabbitmq::default
  * service[rabbitmq-server] action restart
    - restart service service[rabbitmq-server]

For some reason it sets the cluster name, but it's almost like it is forming it's own cluster called "cluster":

[root@rabbit2/]# rabbitmqctl cluster_status
Cluster status of node rabbit@rabbit2 ...
[{nodes,[{disc,[rabbit@rabbit2 ]}]},
 {running_nodes,[rabbit@rabbit2 ]},
 {alarms,[{rabbit@rabbit2 ,[]}]}]

If I reset the node, I can manually join the cluster on the rabbit1 server. Any idea on what could be going on here? Thanks.


This comment has been minimized.

Copy link

commented Aug 11, 2016

Figured it out.

I went ahead and stopped the node

rabbitmqctl stop_app

And reran chef-client.

The node joined right up to the cluster.

@pcon0718 pcon0718 closed this Aug 11, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.