This article uses the version: rabbitmq-server-3.8.3-1.el7.noarch.rpm Centos7 erlang 22.3.1
Install online
yum install esl-erlang_22.3-1~centos~7_amd64.rpm
yum install esl-erlang-compat-21.2.6-1.noarch.rpm
Offline installation
Upload installation package to centos7
Run the commands in sequence:
--force: Forced security
Install --nodeps: do not check dependencies
-ivh i (install): (install) v (view): display the installation process h (human): human-readable display
-ivh erlang- RPM 22.3 - 1 .el8.x86_64.rpm --force - nodeps Download: https://packagecloud.io/rabbitmq/erlang/
rpm -ivh esl-erlang_22.3-1~centos~7_amd64.rpm --force --nodeps
rpm -ivh esl-erlang-compat-21.2.6-1.noarch.rpm --force --nodeps
Install RabbitMQ
-ivh rabbitmq-server-3.8.3-1.el7.noarch.rpm --force --nodeps
Socat will be needed when installing rabbit
yum install socat
Install rabbitmq again
Setting up the configuration file
cd /usr/lib/rabbitmq/lib/rabbitmq_server-3.8.3/ebin
Set up remote login
we rabbitmq.app
before fixing
After modification
Start, stop, restart
systemctl start rabbitmq-server.service systemctl stop rabbitmq-server.service
systemctl restart rabbitmq-server.service
Start the web interface tool
rabbitmq-plugins enable rabbitmq_management
重新启动rabbitmq
systemctl restart rabbitmq-server
Set boot from boot
chkconfig rabbitmq-server on
Open firewall port 15672
firewall-cmd --zone = public --add-port = 15672 / tcp --permanent # open port 15672
firewall-cmd --reload #Configuration takes effect immediately
View all open ports on the firewall
firewall-cmd --zone=public --list-ports
Turn off the firewall
If there are too many ports to be opened and it is too troublesome, you can turn off the firewall and evaluate the security yourself
systemctl stop firewalld.service
View firewall status
firewall-cmd --state
Remote login to RabbitMQ for operation
Local browser access: virtual machine ip: 15672
After logging in
Parameter explanation
connections: Both producers and consumers need to establish a connection with RabbitMQ to complete the production and consumption of messages. Here you can view the connection channels. Channels: After the connection is established, a channel will be formed, and the delivery of messages depends on the channel. Exchanges: switches, used to implement message routing Queues: queues, that is, message queues, messages are stored in the queue, waiting for consumption, and the queue is removed after consumption. Port: 5672: rabbitMq programming language client connection port 15672: rabbitMq management interface port 25672: rabbitMq cluster port
Add user
If you do not use guest, you can create a user yourself
1. Super administrator (administrator)
You can log in to the management console, you can view all the information, and you can operate on users and policies.
2. Monitoring
You can log in to the management console, at the same time you can view the relevant information of rabbitmq node (number of processes, memory usage, disk usage, etc.)
3. Policy maker
You can log in to the management console and manage policies at the same time. However, it is impossible to view the relevant information of the node (the part marked by the red box in the above figure).
4. Ordinary management (management)
You can only log in to the management console, you cannot see the node information, and you cannot manage the strategy.
5. Others
Cannot log in to the management console, usually ordinary producers and consumers.
Virtual host: similar to the database in mysql. They all start with "/"
Setting permissions
