rabbitMQ启动失败

1.  执行命令systemctl status rabbitmq的现象

● rabbitmq.service - rabbitmq
   Loaded: loaded (/usr/lib/systemd/system/rabbitmq.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2022-05-19 17:12:36 CST; 4s ago
  Process: 17859 ExecStop=/home/fivea/env/rabbitmq_server-3.9.7/sbin/rabbitmqctl shutdown (code=exited, status=69)
  Process: 17783 ExecStart=/home/fivea/env/rabbitmq_server-3.9.7/sbin/rabbitmq-server -detached (code=exited, status=0/SUCCESS)
 Main PID: 17793 (code=exited, status=1/FAILURE)

 

 

 

 

2. 系统日志输出信息

May 19 17:13:24 237 systemd: Starting rabbitmq...
May 19 17:13:24 237 systemd: Started rabbitmq.
May 19 17:13:28 237 systemd: rabbitmq.service: main process exited, code=exited, status=1/FAILURE
May 19 17:13:28 237 rabbitmqctl: Error: unable to perform an operation on node 'rabbit@237'. Please see diagnostics information and suggestions below.
May 19 17:13:28 237 rabbitmqctl: Most common reasons for this are:
May 19 17:13:28 237 rabbitmqctl: * Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)
May 19 17:13:28 237 rabbitmqctl: * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)
May 19 17:13:28 237 rabbitmqctl: * Target node is not running
May 19 17:13:28 237 rabbitmqctl: In addition to the diagnostics info below:
May 19 17:13:28 237 rabbitmqctl: * See the CLI, clustering and networking guides on https://rabbitmq.com/documentation.html to learn more
May 19 17:13:28 237 rabbitmqctl: * Consult server logs on node rabbit@237
May 19 17:13:28 237 rabbitmqctl: * If target node is configured to use long node names, don't forget to use --longnames with CLI tools
May 19 17:13:28 237 rabbitmqctl: DIAGNOSTICS
May 19 17:13:28 237 rabbitmqctl: ===========
May 19 17:13:28 237 rabbitmqctl: attempted to contact: [rabbit@237]
May 19 17:13:28 237 rabbitmqctl: rabbit@237:
May 19 17:13:28 237 rabbitmqctl: * unable to connect to epmd (port 4369) on 237: badarg (unknown POSIX error)
May 19 17:13:28 237 rabbitmqctl: Current node details:
May 19 17:13:28 237 rabbitmqctl: * node name: 'rabbitmqcli-630-rabbit@237'
May 19 17:13:28 237 rabbitmqctl: * effective user's home directory: /home/fivea
May 19 17:13:28 237 rabbitmqctl: * Erlang cookie hash: cBgEFXcgZLfDimr2fkTIvg==
May 19 17:13:28 237 systemd: rabbitmq.service: control process exited, code=exited status=69
May 19 17:13:28 237 systemd: Unit rabbitmq.service entered failed state.
May 19 17:13:28 237 systemd: rabbitmq.service failed.

 

问题解决尝试：

1. 配置主机名解析：vi /etc/hosts 添加配置 127.0.0.1 237

 2. 防火墙开放管理界面的端口

3. 统一.erlang.cookie

4. 看到一个博主说主机名不能是数字，我的主机名字是数字，所以还尝试修改了主机名

正确的解决办法

1. 根据其他博主的提示，让rabbitMQ非后台启动

定位到错误信息：

[xxx@237 sbin]$ ./rabbitmq-server 

BOOT FAILED
2022-05-19 17:17:46.291570+08:00 [erro] <0.130.0> 
2022-05-19 17:17:46.291570+08:00 [erro] <0.130.0> BOOT FAILED
2022-05-19 17:17:46.291570+08:00 [erro] <0.130.0> ===========
2022-05-19 17:17:46.291570+08:00 [erro] <0.130.0> ERROR: epmd error for host 237: badarg (unknown POSIX error)
2022-05-19 17:17:46.291570+08:00 [erro] <0.130.0> 
===========
ERROR: epmd error for host 237: badarg (unknown POSIX error)

2. 根据错误信息查询问题关闭

 不少博主说要关掉SELINUX，最终实践不需要关闭SELINUX

有效的操作：

vi /etc/rabbitmq/rabbitmq-env.conf

添加配置，rabbitmq-env.conf是不存在的，需要新建。而且rabbitmq.conf不能代替rabbitmq-env.conf，把这个配置添加到rabbitmq.conf，不生效。

NODENAME=rabbit@localhost