RHEL8本地服务器执行sudo rabbitmqctl status报错的解决方法

在本地部署的RHEL8服务器上执行sudo rabbitmqctl status命令时，出现以下错误：

Error: unable to perform an operation on node 'rabbit@xxxxx'. Please see diagnostics information and suggestions below.
 
Most common reasons for this are:
 
* Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)

* CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)

* Target node is not running
 
In addition to the diagnostics info below:
 
* See the CLI, clustering and networking guides on https://rabbitmq.com/documentation.html to learn more

* Consult server logs on node rabbit@xxxxxx

* If target node is configured to use long node names, don't forget to use --longnames with CLI tools
 
DIAGNOSTICS

===========
 
attempted to contact: ['rabbit@xxxxx']
 
rabbit@xxxxx:

  * connected to epmd (port 4369) on xxxxxxx

  * epmd reports node 'rabbit' uses port 25672 for inter-node and CLI tool traffic

  * can't establish TCP connection to the target node, reason: timeout (timed out)

  * suggestion: check if host 'xxxxxxxx' resolves, is reachable and ports 25672, 4369 are not blocked by firewall
 
Current node details:

* node name: 'rabbitmqcli-401-rabbit@xxxxx'

* effective user's home directory: /var/lib/rabbitmq

* Erlang cookie hash: gvMlNMNDWrRk2xONh+tqWQ==

 Documentation: Table of Contents
 — RabbitMQ

当前环境：

• Erlang版本：Erlang/OTP 25
• RabbitMQ版本：3.12.12

已完成验证：

• 用nc命令测试端口25672、4369、5671、15672的TCP连接均成功
• 主机名/IP地址ping可达

• 检查Erlang Cookie一致性
  这是此类问题的核心诱因之一，操作步骤：

  1. 定位RabbitMQ节点的Erlang Cookie文件，默认路径为/var/lib/rabbitmq/.erlang.cookie
  2. 对比当前执行sudo rabbitmqctl的用户（root）的Cookie文件/root/.erlang.cookie，确保两者内容完全一致
  3. 若不一致，同步Cookie并修正权限：

     sudo cp /var/lib/rabbitmq/.erlang.cookie /root/.erlang.cookie
     sudo chmod 400 /root/.erlang.cookie
     

  4. 重启RabbitMQ服务：sudo systemctl restart rabbitmq-server

• 验证节点名称与参数匹配
  确认RabbitMQ运行节点的名称格式：

  1. 查看RabbitMQ日志/var/log/rabbitmq/rabbit@xxxxx.log，确认节点使用的是短名称还是长名称（FQDN）
  2. 若节点使用长名称，执行命令时需添加--longnames参数：

     sudo rabbitmqctl --longnames status
     

• 排查SELinux限制
  RHEL8默认启用的SELinux可能拦截RabbitMQ内部通信：

  1. 临时关闭SELinux测试：sudo setenforce 0，再次执行rabbitmqctl status验证
  2. 若问题解决，添加SELinux规则放行相关端口：

     sudo semanage port -a -t amqp_port_t -p tcp 25672
     sudo semanage port -a -t epmd_port_t -p tcp 4369
     

  3. 恢复SELinux状态：sudo setenforce 1

• 确认主机名解析准确性
  确保主机名解析的IP与RabbitMQ绑定IP一致：

  1. 查看RabbitMQ配置文件/etc/rabbitmq/rabbitmq.conf中的listeners.tcp.default项，确认绑定的IP地址
  2. 检查/etc/hosts文件，确保xxxxx对应的IP为RabbitMQ绑定的IP（而非仅回环地址）

• 分析RabbitMQ日志细节
  从日志中获取更精准的错误线索：

  sudo tail -n 50 /var/log/rabbitmq/rabbit@xxxxx.log
  

  日志中通常会记录连接失败的具体原因，如权限不足、绑定地址异常等

内容的提问来源于stack exchange，提问作者Adedamola Ajibola