rabbitmqctl错误:无法连接到节点rabbit @ myserver nodedown

Question

我在Windows 2008 R2上运行带有Erlang OTP 17.1的RabbitMQ v3.3.5.我的Dev和QA环境是独立的.我的登台和生产环境是集群的.

我发现RabbitMQ服务正在运行时经常出现这个问题,RabbitMQ管理控制台正在查看所有内容,但是当我尝试从命令行运行rabbitmqctl时,它失败并显示节点已关闭的错误(在本地和在远程服务器).

如果我重新启动Windows服务,则会解决此问题.

我在RabbitMQ错误日志中看不到任何错误消息.最后一条消息表明节点已启动.

下面是我最近在登台窗口集群的节点2上遇到的问题的示例输出:

PS C:\Program Files (x86)\RabbitMQ Server\rabbitmq_server-3.3.5\sbin> .\rabbitmqctl.bat status
Status of node rabbit@MYSERVER2 ...
Error: unable to connect to node rabbit@MYSERVER2: nodedown

DIAGNOSTICS
===========

attempted to contact: [rabbit@MYSERVER2]

rabbit@MYSERVER2:
  * connected to epmd (port 4369) on MYSERVER2
  * epmd reports: node 'rabbit' not running at all
                  no other nodes on MYSERVER2
  * suggestion: start the node

current node details:
- node name: rabbitmqctl2199771@MYSERVER2
- home dir: C:\Users\RabbitMQ
- cookie hash: mn6OaTX9mS4DnZaiOzg8pA==

此时我重新启动RabbitMQ服务,然后再试一次

PS C:\Program Files (x86)\RabbitMQ Server\rabbitmq_server-3.3.5\sbin> .\rabbitmqctl.bat status
Status of node rabbit@MYSERVER2...
[{pid,3784},
 {running_applications,
     [{rabbitmq_management_agent,"RabbitMQ Management Agent","3.3.5"},
      {rabbit,"RabbitMQ","3.3.5"},
      {os_mon,"CPO  CXC 138 46","2.2.15"},
      {mnesia,"MNESIA  CXC 138 12","4.12.1"},
      {xmerl,"XML parser","1.3.7"},
      {sasl,"SASL  CXC 138 11","2.4"},
      {stdlib,"ERTS  CXC 138 10","2.1"},
      {kernel,"ERTS  CXC 138 10","3.0.1"}]},
 {os,{win32,nt}},
 {erlang_version,
     "Erlang/OTP 17 [erts-6.1] [64-bit] [smp:4:4] [async-threads:30]\n"},
 {memory,
     [{total,35960208},
      {connection_procs,2704},
      {queue_procs,5408},
      {plugins,111936},
      {other_proc,13695792},
      {mnesia,102296},
      {mgmt_db,0},
      {msg_index,21816},
      {other_ets,884704},
      {binary,25776},
      {code,16672826},
      {atom,602729},
      {other_system,3834221}]},
 {alarms,[]},
 {listeners,[{clustering,25672,"::"},{amqp,5672,"::"},{amqp,5672,"0.0.0.0"}]},
 {vm_memory_high_watermark,0.4},
 {vm_memory_limit,3435787059},
 {disk_free_limit,50000000},
 {disk_free,74911649792},
 {file_descriptors,
     [{total_limit,8092},
      {total_used,4},
      {sockets_limit,7280},
      {sockets_used,2}]},
 {processes,[{limit,1048576},{used,139}]},
 {run_queue,0},
 {uptime,5}]
...done.

是否有什么原因以及如何自动检测情况？

这是在Windows上运行RabbitMQ时特别存在的问题吗？

Answer 1

当您尝试解析主机名时,主机名不区分大小写.例如,LOCALHOST并且localhost是相同的主机.

但是,当Erlang构造节点的名称时(例如rabbit@<hostname>,在RabbitMQ的情况下),此名称区分大小写.所以rabbit@LOCALHOST并且rabbit@localhost是两个不同的节点名称,即使它们在同一主机上运行.

最近,我们(RabbitMQ团队)发现,在Windows上,为RabbitMQ构建的节点名称不一致.因此,有时,RabbitMQ启动时可能会命名为Windows服务,rabbit@MYHOST但rabbitmqctl会尝试触及rabbit@myhost并失败.

从RabbitMQ 3.6.0开始,节点名称应该是一致的.