rabbitmq服务重启操作实例

于 2022-04-22 09:40:04 发布
阅读量2.9k 收藏 1
点赞数
分类专栏： java 文章标签： java 后端
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/web15286201346/article/details/124337957
版权

实际运维中需要对Rabbitmq集群业务进行业务重启操作，操作遵循的要求如下

关闭顺序：内存节点 => 磁盘节点

启动顺序：磁盘节点 => 内存节点

【检查rabbitmq集群运行状态】

[root@test1 ~]# rabbitmqctl cluster_status
Cluster status of node rabbit@test1 …
[{nodes,[{disc,[rabbit@test1]}, ------磁盘节点
{ram,[rabbit@test2,rabbit@test3]}]}, ----内存节点
{running_nodes,[rabbit@test2,rabbit@test3,
rabbit@test1]},
{cluster_name,<<“rabbit@test2”>>},
{partitions,[]},
{alarms,[{rabbit@test2,[]},
{rabbit@test3,[]},
{rabbit@test1,[]}]}]

【停止rabbitmq服务】

关闭顺序：内存节点 => 磁盘节点

[root@test3 ~]# systemctl status rabbitmq-server
● rabbitmq-server.service - RabbitMQ broker
Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2021-12-23 14:30:07 CST; 4s ago
Process: 60134 ExecStop=/usr/sbin/rabbitmqctl stop (code=exited, status=0/SUCCESS)
Process: 45961 ExecStart=/usr/sbin/rabbitmq-server (code=exited, status=1/FAILURE)
Main PID: 45961 (code=exited, status=1/FAILURE)
Status: “Initialized”

Oct 18 17:14:47 test3 rabbitmq-server[45961]: completed with 6 plugins.
Dec 23 14:30:04 test3 systemd[1]: Stopping RabbitMQ broker…
Dec 23 14:30:04 test3 rabbitmqctl[60134]: Stopping and halting node rabbit@test3 …
Dec 23 14:30:05 test3 rabbitmq-server[45961]: Gracefully halting Erlang VM
Dec 23 14:30:05 test3 rabbitmq-server[45961]: erl_child_setup closed
Dec 23 14:30:07 test3 rabbitmq-server[45961]: Crash dump is being written to: erl_crash.dump…done
Dec 23 14:30:07 test3 systemd[1]: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Dec 23 14:30:07 test3 systemd[1]: Stopped RabbitMQ broker.
Dec 23 14:30:07 test3 systemd[1]: Unit rabbitmq-server.service entered failed state.
Dec 23 14:30:07 test3 systemd[1]: rabbitmq-server.service failed.
[root@test3 ~]#

[root@test2 ~]# systemctl stop rabbitmq-server
[root@test2 ~]# systemctl status rabbitmq-server
● rabbitmq-server.service - RabbitMQ broker
Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2021-12-23 14:30:57 CST; 1s ago
Process: 43128 ExecStop=/usr/sbin/rabbitmqctl stop (code=exited, status=0/SUCCESS)
Process: 44337 ExecStart=/usr/sbin/rabbitmq-server (code=exited, status=1/FAILURE)
Main PID: 44337 (code=exited, status=1/FAILURE)
Status: “Initialized”

Dec 02 11:54:35 test2 rabbitmq-server[44337]: completed with 6 plugins.
Dec 23 14:30:54 test2 systemd[1]: Stopping RabbitMQ broker…
Dec 23 14:30:54 test2 rabbitmqctl[43128]: Stopping and halting node rabbit@test2 …
Dec 23 14:30:55 test2 rabbitmq-server[44337]: Gracefully halting Erlang VM
Dec 23 14:30:55 test2 rabbitmq-server[44337]: erl_child_setup closed
Dec 23 14:30:57 test2 rabbitmq-server[44337]: Crash dump is being written to: erl_crash.dump…done
Dec 23 14:30:57 test2 systemd[1]: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Dec 23 14:30:57 test2 systemd[1]: Stopped RabbitMQ broker.
Dec 23 14:30:57 test2 systemd[1]: Unit rabbitmq-server.service entered failed state.
Dec 23 14:30:57 test2 systemd[1]: rabbitmq-server.service failed.
[root@test2 ~]#

[root@test1 ~]# systemctl stop rabbitmq-server
[root@test1 ~]# systemctl status rabbitmq-server
● rabbitmq-server.service - RabbitMQ broker
Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2021-12-23 14:33:06 CST; 1s ago
Process: 69435 ExecStop=/usr/sbin/rabbitmqctl stop (code=exited, status=0/SUCCESS)
Process: 46654 ExecStart=/usr/sbin/rabbitmq-server (code=exited, status=1/FAILURE)
Main PID: 46654 (code=exited, status=1/FAILURE)
Status: “Initialized”

Oct 18 17:14:27 test1 rabbitmq-server[46654]: completed with 6 plugins.
Dec 23 14:33:03 test1 systemd[1]: Stopping RabbitMQ broker…
Dec 23 14:33:03 test1 rabbitmqctl[69435]: Stopping and halting node rabbit@test1 …
Dec 23 14:33:04 test1 rabbitmq-server[46654]: Gracefully halting Erlang VM
Dec 23 14:33:04 test1 rabbitmq-server[46654]: erl_child_setup closed
Dec 23 14:33:06 test1 rabbitmq-server[46654]: Crash dump is being written to: erl_crash.dump…done
Dec 23 14:33:06 test1 systemd[1]: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Dec 23 14:33:06 test1 systemd[1]: Stopped RabbitMQ broker.
Dec 23 14:33:06 test1 systemd[1]: Unit rabbitmq-server.service entered failed state.
Dec 23 14:33:06 test1 systemd[1]: rabbitmq-server.service failed.
[root@test1 ~]#

再次查询集群状态

[root@test1 ~]# rabbitmqctl cluster_status
Cluster status of node rabbit@test1 …
Error: unable to connect to node rabbit@test1: nodedown

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

attempted to contact: [rabbit@test1]

rabbit@test1:
* connected to epmd (port 18891) on test1
* epmd reports: node ‘rabbit’ not running at all
no other nodes on test1
* suggestion: start the node

current node details:
- node name: ‘rabbitmq-cli-36@test1’
- home dir: /var/lib/rabbitmq

【启动rabbitmq服务】

启动顺序：磁盘节点 => 内存节点

先启动磁盘节点disk
[root@test1 ~]# systemctl start rabbitmq-server
[root@test1 ~]#
[root@test1 ~]#
[root@test1 ~]#
[root@test1 ~]# systemctl status rabbitmq-server
● rabbitmq-server.service - RabbitMQ broker
Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2021-12-23 14:42:35 CST; 2s ago
Process: 69435 ExecStop=/usr/sbin/rabbitmqctl stop (code=exited, status=0/SUCCESS)
Main PID: 72610 (beam.smp)
Status: “Initialized”
CGroup: /system.slice/rabbitmq-server.service
├─72610 /usr/lib64/erlang/erts-8.3.5.3/bin/beam.smp -W w -A 1024 -P 1048576 -t 5000000 -stbt db -zdbbl 32000 -K true – -root /usr/lib64/erl…
├─74017 erl_child_setup 10240
├─74101 inet_gethost 4
├─74102 inet_gethost 4
└─74107 inet_gethost 4

Dec 23 14:42:34 test1 rabbitmq-server[72610]: RabbitMQ 3.6.6. Copyright © 2007-2016 Pivotal Software, Inc.
Dec 23 14:42:34 test1 rabbitmq-server[72610]: ## ## Licensed under the MPL. See http://www.rabbitmq.com/
Dec 23 14:42:34 test1 rabbitmq-server[72610]: ## ##
Dec 23 14:42:34 test1 rabbitmq-server[72610]: ########## Logs: /var/log/rabbitmq/rabbit@test1.log
Dec 23 14:42:34 test1 rabbitmq-server[72610]: ###### ## /var/log/rabbitmq/rabbit@test1-sasl.log
Dec 23 14:42:34 test1 rabbitmq-server[72610]: ##########
Dec 23 14:42:34 test1 rabbitmq-server[72610]: Starting broker…
Dec 23 14:42:35 test1 rabbitmq-server[72610]: systemd unit for activation check: “rabbitmq-server.service”
Dec 23 14:42:35 test1 systemd[1]: Started RabbitMQ broker.
Dec 23 14:42:35 test1 rabbitmq-server[72610]: completed with 6 plugins.
[root@test1 ~]#

依次启动内存节点
[root@test3 ~]# systemctl start rabbitmq-server
[root@test3 ~]#
[root@test3 ~]#
[root@test3 ~]#
[root@test3 ~]# systemctl status rabbitmq-server
● rabbitmq-server.service - RabbitMQ broker
Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2021-12-23 14:43:19 CST; 1s ago
Process: 63524 ExecStop=/usr/sbin/rabbitmqctl stop (code=exited, status=0/SUCCESS)
Main PID: 66693 (beam.smp)
Status: “Initialized”
CGroup: /system.slice/rabbitmq-server.service
├─66693 /usr/lib64/erlang/erts-8.3.5.3/bin/beam.smp -W w -A 1024 -P 1048576 -t 5000000 -stbt db -zdbbl 32000 -K true – -root /usr/lib64/erl…
├─68101 erl_child_setup 10240
├─68186 inet_gethost 4
└─68187 inet_gethost 4

Dec 23 14:43:18 test3 rabbitmq-server[66693]: RabbitMQ 3.6.6. Copyright © 2007-2016 Pivotal Software, Inc.
Dec 23 14:43:18 test3 rabbitmq-server[66693]: ## ## Licensed under the MPL. See http://www.rabbitmq.com/
Dec 23 14:43:18 test3 rabbitmq-server[66693]: ## ##
Dec 23 14:43:18 test3 rabbitmq-server[66693]: ########## Logs: /var/log/rabbitmq/rabbit@test3.log
Dec 23 14:43:18 test3 rabbitmq-server[66693]: ###### ## /var/log/rabbitmq/rabbit@test3-sasl.log
Dec 23 14:43:18 test3 rabbitmq-server[66693]: ##########
Dec 23 14:43:18 test3 rabbitmq-server[66693]: Starting broker…
Dec 23 14:43:19 test3 rabbitmq-server[66693]: systemd unit for activation check: “rabbitmq-server.service”
Dec 23 14:43:19 test3 systemd[1]: Started RabbitMQ broker.
Dec 23 14:43:19 test3 rabbitmq-server[66693]: completed with 6 plugins.
[root@test3 ~]#
[root@test2 ~]# systemctl start rabbitmq-server
[root@test2 ~]# systemctl status rabbitmq-server
● rabbitmq-server.service - RabbitMQ broker
Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2021-12-23 14:43:32 CST; 1s ago
Process: 43128 ExecStop=/usr/sbin/rabbitmqctl stop (code=exited, status=0/SUCCESS)
Main PID: 46302 (beam.smp)
Status: “Initialized”
CGroup: /system.slice/rabbitmq-server.service
├─46302 /usr/lib64/erlang/erts-8.3.5.3/bin/beam.smp -W w -A 1024 -P 1048576 -t 5000000 -stbt db -zdbbl 32000 -K true – -root /usr/lib64/erl…
├─46477 /usr/lib64/erlang/erts-8.3.5.3/bin/epmd -daemon
├─47712 erl_child_setup 10240
├─47796 inet_gethost 4
└─47797 inet_gethost 4

Dec 23 14:43:30 test2 rabbitmq-server[46302]: RabbitMQ 3.6.6. Copyright © 2007-2016 Pivotal Software, Inc.
Dec 23 14:43:30 test2 rabbitmq-server[46302]: ## ## Licensed under the MPL. See http://www.rabbitmq.com/
Dec 23 14:43:30 test2 rabbitmq-server[46302]: ## ##
Dec 23 14:43:30 test2 rabbitmq-server[46302]: ########## Logs: /var/log/rabbitmq/rabbit@test2.log
Dec 23 14:43:30 test2 rabbitmq-server[46302]: ###### ## /var/log/rabbitmq/rabbit@test2-sasl.log
Dec 23 14:43:30 test2 rabbitmq-server[46302]: ##########
Dec 23 14:43:30 test2 rabbitmq-server[46302]: Starting broker…
Dec 23 14:43:32 test2 rabbitmq-server[46302]: systemd unit for activation check: “rabbitmq-server.service”
Dec 23 14:43:32 test2 systemd[1]: Started RabbitMQ broker.
Dec 23 14:43:32 test2 rabbitmq-server[46302]: completed with 6 plugins.
集群状态
[root@test1 ~]# rabbitmqctl cluster_status
Cluster status of node rabbit@test1 …
[{nodes,[{disc,[rabbit@test1]},
{ram,[rabbit@test2,rabbit@test3]}]},
{running_nodes,[rabbit@test2,rabbit@test3,
rabbit@test1]},
{cluster_name,<<“rabbit@test2”>>},
{partitions,[]},
{alarms,[{rabbit@test2,[]},
{rabbit@test3,[]},
{rabbit@test1,[]}]}]

web15286201346
关注
专栏目录
Linux(CentOS8)服务器安装RabbitMQ
//Case
09-11 670
我安装了很久都没有成功, 各种问题, 每次的异常都不一样, 现将成功安装过程做个总结。
解决RabbitMQ启动报错：Job for rabbitmq-server.service failed because the control process exited with error
最新发布
qq_45839663的博客
04-04 3020
解决RabbitMQ启动报错：Job for rabbitmq-server.service failed because the control process exited with error
解决RabbitMQ报错问题
weixin_47436247的博客
07-16 3583
解决RabbitMQ报错问题 ● rabbitmq-server.service - RabbitMQ broker Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; disabled; vendor preset: disabled) Active: activating (auto-restart) (Result: exit-code) since Fri 2021-07-16 12:03:35 CST; 4s ago P
rabbitmq-server
09-28
是一个在AMQP基础上完成的，可复用的企业消息系统。他遵循Mozilla Public License开源协议.
CentOS 7 部署RabbitMQ 服务
热门推荐
静静是我女朋友
11-11 1万+
RabbitMQ 简介 MQ全称为Message Queue, 消息队列（MQ）是一种应用程序对应用程序的通信方法。应用程序通过读写出入队列的消息（针对应用程序的数据）来通信，而无需专用连接来链接它们。消息传递指的是程序之间通过在消息中发送数据进行通信，而不是通过直接调用彼此来通信，直接调用通常是用于诸如远程过程调用的技术。排队指的是应用程序通过 队列来通信。队列的使用除去了接收和发送应用程序同时执
rabbitmq-server相关命令
m0_51682616的博客
02-24 1278
#第一步，为防止依赖冲突，先下载aptitude依赖包管理工具 sudo apt-get install aptitude #第二步，下载erlang语言环境 sudo aptitude install erlang-nox #第三步，下载 rabbitmq 服务 sudo
rabbitmq server
帅的没拼音
12-07 2815
服务启动与停止 service rabbitmq-server start #启动服务 service rabbitmq-server stop #停止服务 service rabbitmq-server status #查看状态 开通STOMP通道 rabbitmq-plugins enable rabbitmq_web_stomp rabbitmq-plugins enable rabbitmq_web_stomp_examples #重启 service rabbitmq-se...
RabbitMQ命令
Make
11-20 563
Usage: rabbitmqctl [-n <node>] [-q] <command> [<command options>] Options: -n node -q Default node is "rabbit@server", where server is the local host. On a host named "server.example.com", 默认节点是“ rabbit @ server”，其中server是本地主机。...
CentOs 7.3中搭建RabbitMQ 3.6单机多实例服务的步骤与使用
09-15
在CentOS 7.3操作系统中，搭建RabbitMQ 3.6的单机多实例服务是一项关键任务，尤其对于需要高效消息传递和处理的分布式系统。RabbitMQ是一个广泛使用的开源消息代理，它基于AMQP（Advanced Message Queuing Protocol...
RabbitMq与Spring整合实例
01-17
5. **持久化**：通过设置队列和交换机的持久化属性，即使RabbitMQ重启，消息也不会丢失。 **总结** 整合RabbitMQ和Spring，能让你在Spring应用中轻松地实现消息队列功能，提高系统的灵活性和稳定性。通过理解并...
rabbitMQ 源代码实例
12-11
在这个源代码实例中，我们可以深入理解RabbitMQ的工作原理、核心组件以及如何在实际项目中应用。 首先，我们需要了解RabbitMQ的基本架构。它由Broker（消息代理）、Exchanges（交换器）、Queues（队列）和Bindings...
python队列通信:rabbitMQ的使用(实例讲解)
09-20
在Python中操作RabbitMQ，首先需要安装`pika`模块，这是一个Python客户端库，可以直接通过`pip`命令进行安装： ```bash pip install pika ``` 接下来，我们来看一个简单的RabbitMQ生产者（Producer）和消费者...
RabbitMQ快速入门及实例演示
BaiKnow的博客
02-05 1742
RabbitMQ 先做起来，再去想其他。 1.MQ 消息队列概念 MQ（message queue）消息队列，FIFO先入先出。对服务器的请求先加入到消息队列中，再由消息队列来进行请求的分发。 还是一种跨进程的通信机制，用于上下游传递消息。在互联网架构中，MQ是一种非常常见的上下游“逻辑解耦 + 物理解耦”的消息通信服务。 使用MQ以后，上游只需要将消息发送给MQ，无需关注是否下游接收，MQ会监督消息的接收，不再需要依赖其他服务。 1.1 用处 1.1.1 流量消峰 举个例子，如果订单系统最多能处理一万
RabbitMQ-Server 前台访问异常
Burgess_Lee的博客
07-11 179
今天Windows下配置安装了RabbitMQ，然后访问127.0.0.1:15672，发现访问不了。 安装过程不再赘述，直接上解决方案。 打开RabbitMQ Server的开始菜单安装目录 选择RabbitMQ Command Prompt 命令行并打开，输入 rabbitmq-plugins enable rabbitmq_managem...
rabbitMq启动出错
m0_67400972的博客
04-22 804
rabbitMq启动出错 Job for rabbitmq-server.service failed because the control process exited with error code. See “systemctl status rabbitmq-server.service” and “journalctl -xe” for details. ● rabbitmq-server.service - RabbitMQ broker Loaded: loaded (/usr/lib
【消息中间件RabbitMQ 】：RabbitMQ Server 的搭建
悦.L的博客
11-29 1125
文章目录1、 1、
rabbitmq启动service rabbitmq-server restart报错
zhaijunliang2009的博客
03-19 3928
rabbitmq启动service rabbitmq-server restart报如下错误： 根据错误提示信息 输入journalctl -xe 查出报如红框中的错误，通过度娘参考如下这篇文章：https://yq.aliyun.com/articles/342269解决。 /etc/rabbitmq/rabbitmq-env.conf 文件中输入 NODENAME=...
RabbitMQ常用命令
08-25 206
Linux中RabbitMQ的安装 1）下载rabbitmq及其依赖 2）重新克隆一个虚拟机 3）分别对应着执行相应命令进行安装（这里安装包和依赖我都放在了自己在linuxh上建的RabbitMQ文件夹里） [root@localhost opt]# cd RabbitMQ/ #将下好的安装包和依赖拖到linux某个位置中 [root@localhost RabbitMQ]# ll total 33616 -rw-r--r--. 1 root root 18850824 Jun 15 02:03
CentOS 7.3中搭建RabbitMQ 3.6多实例教程
"本文主要介绍了如何在CentOS 7.3上搭建RabbitMQ 3.6的单机多实例服务，以及RabbitMQ的基本概念和相关准备工作，包括关闭或配置防火墙，安装Erlang环境，以及安装RabbitMQ的步骤。" RabbitMQ是一个基于AMQP...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值