我已经用三个节点的Rabbitmq集群部署了openstack-ansible，它使用lxc在顶部运行Rabbitmq，当我执行rabbitmqctl status命令时，如果您注意到它说错了，我会在这里看到一个非常奇怪的错误节点ostack-controller-01是主机节点，而不是实际的Rabbitmq节点。
[root@ostack-controller-01-rabbit-mq-container-1bf6ede2 ~]# rabbitmqctl status
Status of node 'rabbit@ostack-controller-01' ...
Error: unable to connect to node 'rabbit@ostack-controller-01': nodedown
DIAGNOSTICS
===========
attempted to contact: ['rabbit@ostack-controller-01']
rabbit@ostack-controller-01:
* unable to connect to epmd (port 4369) on ostack-controller-01: address (cannot connect to host/port)
current node details:
- node name: 'rabbitmq-cli-06@ostack-controller-01-rabbit-mq-container-1bf6ede2'
- home dir: /var/lib/rabbitmq
- cookie hash: SssFdXBI7wTevePuCt5d9w==
如何解决此问题，并告诉Rabbitmq与正确的主机ostack-controller-01-rabbit-mq-container-1bf6ede2对话
我尝试过forget_cluster_node，但是没有运气，仍然抛出相同的错误。
[root@ostack-controller-01-rabbit-mq-container-1bf6ede2 ~]# rabbitmqctl forget_cluster_node rabbit@ostack-controller-01
Removing node 'rabbit@ostack-controller-01' from cluster ...
Error: unable to connect to node 'rabbit@ostack-controller-01': nodedown
DIAGNOSTICS
===========
attempted to contact: ['rabbit@ostack-controller-01']
rabbit@ostack-controller-01:
* unable to connect to epmd (port 4369) on ostack-controller-01: address (cannot connect to host/port)
current node details:
- node name: 'rabbitmq-cli-39@ostack-controller-01-rabbit-mq-container-1bf6ede2'
- home dir: /var/lib/rabbitmq
- cookie hash: SssFdXBI7wTevePuCt5d9w==
[root@ostack-controller-01-rabbit-mq-container-1bf6ede2 rabbitmq]# rabbitmqctl -n rabbit@ostack-controller-01-rabbit-mq-container-1bf6ede2 status
Status of node 'rabbit@ostack-controller-01-rabbit-mq-container-1bf6ede2' ...
[{pid,8720},
{running_applications,
[{rabbitmq_management,"RabbitMQ Management Console","3.6.9"},
{amqp_client,"RabbitMQ AMQP Client","3.6.9"},
{rabbitmq_management_agent,"RabbitMQ Management Agent","3.6.9"},
{rabbitmq_web_dispatch,"RabbitMQ Web Dispatcher","3.6.9"},
{rabbit,"RabbitMQ","3.6.9"},
{rabbit_common,
"Modules shared by rabbitmq-server and rabbitmq-erlang-client",
"3.6.9"},
{xmerl,"XML parser","1.3.14"},
{os_mon,"CPO CXC 138 46","2.4.2"},
{cowboy,"Small, fast, modular HTTP server.","1.0.4"},
{ranch,"Socket acceptor pool for TCP protocols.","1.3.0"},
{ssl,"Erlang/OTP SSL application","8.1.3.1.1"},
{public_key,"Public key infrastructure","1.4"},
{cowlib,"Support library for manipulating Web protocols.","1.0.2"},
{crypto,"CRYPTO","3.7.4"},
{inets,"INETS CXC 138 49","6.3.9"},
{compiler,"ERTS CXC 138 10","7.0.4.1"},
{asn1,"The Erlang ASN1 compiler version 4.0.4","4.0.4"},
{syntax_tools,"Syntax tools","2.1.1"},
{mnesia,"MNESIA CXC 138 12","4.14.3.1"},
{sasl,"SASL CXC 138 11","3.0.3"},
{stdlib,"ERTS CXC 138 10","3.3"},
{kernel,"ERTS CXC 138 10","5.2.0.1"}]},
{os,{unix,linux}},
{erlang_version,
"Erlang/OTP 19 [erts-8.3.5.4] [source] [64-bit] [smp:6:6] [async-threads:128] [hipe] [kernel-poll:true]\n"},
{memory,
[{total,64189296},
{connection_readers,179280},
{connection_writers,26568},
{connection_channels,124504},
{connection_other,127440},
{queue_procs,2832},
{queue_slave_procs,0},
{plugins,406280},
{other_proc,21056136},
{mnesia,500680},
{metrics,205984},
{mgmt_db,127256},
{msg_index,47416},
{other_ets,2692192},
{binary,1591656},
{code,24765630},
{atom,1033401},
{other_system,11505193}]},
{alarms,[]},
{listeners,
[{clustering,25672,"::"},
{amqp,5672,"::"},
{'amqp/ssl',5671,"::"},
{http,15672,"::"}]},
{vm_memory_high_watermark,0.4},
{vm_memory_limit,6662953369},
{disk_free_limit,50000000},
{disk_free,82822516736},
{file_descriptors,
[{total_limit,65436},
{total_used,5},
{sockets_limit,58890},
{sockets_used,3}]},
{processes,[{limit,1048576},{used,376}]},
{run_queue,0},
{uptime,14},
{kernel,{net_ticktime,60}}]
这很有趣...为什么后面的命令可以运行，但rabbitmqctl cluster_status却不起作用？
[root@ostack-controller-01-rabbit-mq-container-1bf6ede2 rabbitmq]# rabbitmqctl -n rabbit@ostack-controller-01-rabbit-mq-container-1bf6ede2 cluster_status
Cluster status of node 'rabbit@ostack-controller-01-rabbit-mq-container-1bf6ede2' ...
[{nodes,
[{disc,
['rabbit@ostack-controller-01-rabbit-mq-container-1bf6ede2',
'rabbit@ostack-controller-02-rabbit-mq-container-d510bdfc',
'rabbit@ostack-controller-03-rabbit-mq-container-c482ee13']}]},
{running_nodes,
['rabbit@ostack-controller-02-rabbit-mq-container-d510bdfc',
'rabbit@ostack-controller-03-rabbit-mq-container-c482ee13',
'rabbit@ostack-controller-01-rabbit-mq-container-1bf6ede2']},
{cluster_name,<<"openstack">>},
{partitions,
[{'rabbit@ostack-controller-02-rabbit-mq-container-d510bdfc',
['rabbit@ostack-controller-01-rabbit-mq-container-1bf6ede2',
'rabbit@ostack-controller-03-rabbit-mq-container-c482ee13']},
{'rabbit@ostack-controller-03-rabbit-mq-container-c482ee13',
['rabbit@ostack-controller-02-rabbit-mq-container-d510bdfc']}]},
{alarms,
[{'rabbit@ostack-controller-02-rabbit-mq-container-d510bdfc',[]},
{'rabbit@ostack-controller-03-rabbit-mq-container-c482ee13',[]},
{'rabbit@ostack-controller-01-rabbit-mq-container-1bf6ede2',[]}]}]
答案 0 :(得分：0)
首先，RabbitMQ 3.6.9较旧，您应该使用最新版本。
话虽如此，这不是问题。 echo $HOSTNAME的输出是这样的：
ostack-controller-01.foo.example.com
因此，当rabbitmqctl status运行时，它将使用this code来确定要连接的节点名称。由于设置了HOSTNAME变量，因此该变量用于确定节点名称，并且rabbitmqctl尝试使用rabbit@ostack-controller-01，但失败。
您可以继续使用-n rabbit@ostack-controller-01-rabbit-mq-container-1bf6ede2的{{1}}参数来解决此问题。或者，您可以使用以下内容创建rabbitmqctl文件：
/etc/rabbitmq/rabbitmq-env.conf然后，NODENAME=rabbit@ostack-controller-01-rabbit-mq-container-1bf6ede2
和其他rabbitmqctl status命令应该可以使用。然后，您将使用rabbitmqctl
注意： RabbitMQ团队监视the rabbitmq-users mailing list，并且有时仅在StackOverflow上回答问题。