RabbitMQ 报错汇总

本文讲述了如何解决rabbitmq重装后加入原有cluster失败的问题,通过清理Mnesia残留信息(mv /var/lib/rabbitmq/mnesia/tmp)、停止并重启服务来修复认证错误,确保集群一致性。
摘要由CSDN通过智能技术生成

一、rabbitmq重装之后无法加入原有cluster

[root@compute1 ~]# rabbitmqctl join_cluster rabbit@controller
Clustering node rabbit@compute1 with rabbit@controller ...
Error: {cannot_start_mnesia,
           {{shutdown,{failed_to_start_child,mnesia_kernel_sup,killed}},
            {mnesia_sup,start,[normal,[]]}}}
                        
[root@compute1 ~]# rabbitmqctl start_app
Starting node rabbit@compute1 ...
BOOT FAILED
===========
Error description:
   {error,{inconsistent_cluster,"Node rabbit@compute1 thinks it‘s clustered with node rabbit@controller, but rabbit@controller disagrees"}}
Log files (may contain more information):
   /var/log/rabbitmq/rabbit@compute1.log
   /var/log/rabbitmq/rabbit@compute1-sasl.log
Stack trace:
   [{rabbit_mnesia,check_cluster_consistency,0,
                   [{file,"src/rabbit_mnesia.erl"},{line,598}]},
    {rabbit,‘-start/0-fun-0-‘,0,[{file,"src/rabbit.erl"},{line,260}]},
    {rabbit,start_it,1,[{file,"src/rabbit.erl"},{line,296}]},
    {rpc,‘-handle_call_call/6-fun-0-‘,5,[{file,"rpc.erl"},{line,206}]}]
Error: {error,{inconsistent_cluster,"Node rabbit@compute1 thinks it‘s clustered with node rabbit@controller, but rabbit@controller disagrees"}}

因为controller node是新安装,其icook信息也复制过去。compute1 node也执行stop_app,故应该推测应该是compute1 node之前残留的cluster信息,导致认证失败 在网上查询到因为mnesia的信息残留,故会认证失败。 其目录为/var/lib/rabbitmq/mnesia

mv /var/lib/rabbitmq/mnesia /tmp

重启rabbitmq之后再次尝试加入集群:

rabbitmqctl join_cluster rabbit@controller
评论 2
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值