`

rabbitmq安装及异常处理

rabbitmq 
阅读更多

        官网：

        https://www.rabbitmq.com/install-standalone-mac.html

 

       

安装erlang语言环境

安装依赖文件

yum install ncurses-devel
yum -y install openssl
yum -y install ssl
yum -y install xmlto
yum -y install python-simplejson
yum -y install python

进入 http://www.erlang.org/download.html 选择源文件下载

wget http://www.erlang.org/download/otp_src_17.5.tar.gz
tar zxvf otp_src_17.5.tar.gz
cd otp_src_17.5

阅读HOTO/INSTALL.md文件

./configure
make && make install

安装完成以后，执行erl看是否能打开eshell，用’halt().’退出，注意后面的点号，那是erlang的结束符。

[root@iZ113aowxo2Z ~]# erl
Erlang/OTP 17 [erts-6.4] [source] [64-bit] [async-threads:10] [hipe] [kernel-poll:false]
Eshell V6.4 (abort with ^G)
1> 9+1.
10
2> halt().

安装RabbitMQ

安装依赖

yum install xmlto

创建主文件夹

mkdir rabbitmq
cd rabbitmq

直接使用RPM

wget http://www.rabbitmq.com/releases/rabbitmq-server/v3.6.0/rabbitmq-server-3.6.0-1.noarch.rpm
rpm -ivh rabbitmq-server-3.6.0-1.noarch.rpm

编译安装包
进入http://www.rabbitmq.com/download.html选择最新的源码包

wget http://www.rabbitmq.com/releases/rabbitmq-server/v3.6.0/rabbitmq-server-3.6.0.tar.xz
xz -d rabbitmq-server-3.6.0.tar.xz
tar xvf rabbitmq-server-3.6.0.tar
cd rabbitmq-server-3.6.0
make
make install TARGET_DIR=/opt/rabbitmq SBIN_DIR=/opt/rabbitmq/sbin MAN_DIR=/opt/rabbitmq/man DOC_INSTALL_DIR=/opt/rabbitmq/doc

使用

启动MQ

rabbitmq-server -detached

查看状态

rabbitmqctl status

启用管理插件

mkdir /etc/rabbitmq/
rabbitmq-plugins enable rabbitmq_management

停止服务

rabbitmqctl stop

添加账号
PS：默认账号guest只能在localhost访问

rabbitmqctl add_user admin admin

设置管理员

rabbitmqctl set_user_tags admin administrator

设置读写权限
命令使用户admin具有/vhost1这个virtual host中所有资源的配置、写、读权限以便管理其中的资源

rabbitmqctl set_permissions -p /vhost1 admin ‘.‘ ‘.‘ ‘.*’

查看账号

rabbitmqctl list_users

加入账号到配置

vi /etc/rabbitmq/rabbitmq.config
[
{rabbit, [{loopback_users, [“admin”]}]}
].

重启后 http://ip:15672 登录管理界面了

 

 

        异常处理：

        

64位CentOS6.2安装erlang及rabbitmqServer

CentOS 6.2 64bit 安装erlang及RabbitMQ Server

1、操作系统环境(CentOS 6.2 64bit)

[root@leekwen ~]# cat /etc/issue
CentOS release 6.2 (Final)
Kernel \r on an \m
[root@leekwen ~]# cat /proc/cpuinfo grep "clflush size"
clflush size    : 64
clflush size    : 64
clflush size    : 64
clflush size    : 64
clflush size    : 64
clflush size    : 64
clflush size    : 64
clflush size    : 64
2、安装erlang依赖的基本环境 
[root@leekwen ~]# yum -y install make gcc gcc-c++ kernel-devel m4 ncurses-devel openssl-devel
3、导入erlang源，并安装erlang 
[root@leekwen ~]# rpm --import http://binaries.erlang-solutions.com/debian/erlang_solutions.asc
[root@leekwen ~]# wget -O /etc/yum.repos.d/erlang_solutions.repo  http://binaries.erlang-solutions.com/rpm/centos/erlang_solutions.repo
--2014-04-09 22:29:49--  http://binaries.erlang-solutions.com/rpm/centos/erlang_solutions.repo
Resolving binaries.erlang-solutions.com... 46.235.224.136
Connecting to binaries.erlang-solutions.com46.235.224.136:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://packages.erlang-solutions.com//rpm/centos/erlang_solutions.repo [following]
--2014-04-09 22:29:56--  http://packages.erlang-solutions.com//rpm/centos/erlang_solutions.repo
Resolving packages.erlang-solutions.com... 31.172.186.53
Connecting to packages.erlang-solutions.com31.172.186.53:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 245
Saving to: /etc/yum.repos.d/erlang_solutions.repo

100%[=================================================================================>] 245         --.-K/s   in 0s

2014-04-09 22:30:09 (34.0 MB/s) - /etc/yum.repos.d/erlang_solutions.repo
[root@leekwen ~]# wget http://apt.sw.be/redhat/el6/en/x86_64/rpmforge/RPMS/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm
Resolving tree.repoforge.org... 78.46.17.228
Connecting to tree.repoforge.org78.46.17.228:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://apt.sw.be/redhat/el6/en/x86_64/rpmforge/RPMS/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm [following]
--2014-04-09 22:30:54--  http://apt.sw.be/redhat/el6/en/x86_64/rpmforge/RPMS/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm
Resolving apt.sw.be... 193.1.193.67
Connecting to apt.sw.be193.1.193.67:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 12700 (12K) [application/x-redhat-package-manager]
Saving to: rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm

100%[=================================================================================>] 12,700      4.80K/s   in 2.6s

2014-04-09 22:31:07 (4.80 KB/s) - rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm

[root@leekwen ~]# rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt
[root@leekwen ~]# rpm -i rpmforge-release-0.5.2-2.el6.rf.*.rpm
[root@leekwen ~]# yum update
[root@leekwen ~]# yum update --skip-broken
[root@leekwen ~]# yum install erlang
4、测试erlang环境 
[root@leekwen ~]# erl
Erlang R16B03 (erts-5.10.4) [source] [64-bit] [smp:8:8] [async-threads:10] [kernel-poll:false]

Eshell V5.10.4  (abort with ^G)
1> A=12.
12
2> A.
12
3>
BREAK: (a)bort (c)ontinue (p)roc info (i)nfo (l)oaded
       (v)ersion (k)ill (D)b-tables (d)istribution
^C[root@leekwen ~]#
5、下载并安装rabbitmq-server   
[root@leekwen ~]# wget -c http://www.rabbitmq.com/releases/rabbitmq-server/v3.3.0/rabbitmq-server-3.3.0-1.noarch.rpm
--2014-04-10 16:44:24--  
http://www.rabbitmq.com/releases/rabbitmq-server/v3.3.0/rabbitmq-server-3.3.0-1.noarch.rpm
Resolving www.rabbitmq.com... 192.240.153.117
Connecting to www.rabbitmq.com192.240.153.117:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3869384 (3.7M) [application/x-redhat-package-manager]
Saving to: “rabbitmq-server-3.3.0-1.noarch.rpm”

100%[======================================>] 3,869,384   11.9K/s   in 5m 37s

2014-04-10 16:50:10 (11.2 KB/s) - “rabbitmq-server-3.3.0-1.noarch.rpm” saved [3869384/3869384]

[root@leekwen ~]#  yum install rabbitmq-server-3.3.0-1.noarch.rpm
Loaded plugins: fastestmirror, security
Loading mirror speeds from cached hostfile
 * base: centos.ustc.edu.cn
 * extras: centos.ustc.edu.cn
 * rpmforge: ftp.riken.jp
 * updates: centos.ustc.edu.cn
Setting up Install Process
Examining rabbitmq-server-3.3.0-1.noarch.rpm: rabbitmq-server-3.3.0-1.noarch
Marking rabbitmq-server-3.3.0-1.noarch.rpm to be installed
Resolving Dependencies
--> Running transaction check
> Package rabbitmq-server.noarch 0:3.3.0-1 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package           Arch     Version     Repository                         Size
================================================================================
Installing:
 rabbitmq-server   noarch   3.3.0-1     /rabbitmq-server-3.3.0-1.noarch   4.3 M

Transaction Summary
================================================================================
Install       1 Package(s)

Total size: 4.3 M
Installed size: 4.3 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : rabbitmq-server-3.3.0-1.noarch                               1/1

Installed:
  rabbitmq-server.noarch 0:3.3.0-1

Complete!
6、启动rabbitmq-server 
[root@leekwen ~]# /etc/init.d/rabbitmq-server start
Starting rabbitmq-server:
FAILED - check /var/log/rabbitmq/startup_{log, _err}
rabbitmq-server.
[root@leekwen ~]# cat /var/log/rabbitmq/startup_err
[root@leekwen ~]# cat /var/log/rabbitmq/startup_log
ERROR: epmd error for host leekwen: address (cannot connect to host/port)
[root@leekwen ~]# hostname
leekwen
[root@leekwen ~]# vi /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=leekwen
[root@leekwen ~]# cat /etc/hosts
127.0.0.1       localhost
127.0.0.1       leekwen
::1             localhost
7、以上操作排除了因为主机名不同导致RabbitMQ-Server启动报错的问题，请修改主机名（参见上述步骤），再次启动RabbitMQ-Server 
[root@leekwen ~]# /etc/init.d/rabbitmq-server restart
Restarting rabbitmq-server: RabbitMQ is not running
FAILED - check /var/log/rabbitmq/startup_{log, _err}
rabbitmq-server.
8、结果同样报错，查看错误的日志： 
[root@leekwen ~]# cat /var/log/rabbitmq/startup_log
              RabbitMQ 3.3.0. Copyright (C) 2007-2013 GoPivotal, Inc.
  ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
  ##  ##
  ##########  Logs: /var/log/rabbitmq/rabbit@leekwen.log
  ######  ##        /var/log/rabbitmq/rabbit@leekwen-sasl.log
  ##########
              Starting broker...

BOOT FAILED
===========

Error description:
   {case_clause,
       {error,
           {{shutdown,
                {failed_to_start_child,tcp_listener,
                    {cannot_listen,{0,0,0,0,0,0,0,0},5672,eaddrinuse}}},
            {child,undefined,'rabbit_tcp_listener_sup_:::5672',
                {tcp_listener_sup,start_link,
                    [{0,0,0,0,0,0,0,0},
                     5672,
                     [inet6,binary,
                      {packet,raw},
                      {reuseaddr,true},
                      {backlog,128},
                      {nodelay,true},
                      {linger,{true,0}},
                      {exit_on_close,false}],
                     {rabbit_networking,tcp_listener_started,[amqp]},
                     {rabbit_networking,tcp_listener_stopped,[amqp]},
                     {rabbit_networking,start_client,[]},
                     "TCP Listener"]},
                transient,infinity,supervisor,
                [tcp_listener_sup]}}}}

Log files (may contain more information):
   /var/log/rabbitmq/rabbit@leekwen.log
   /var/log/rabbitmq/rabbit@leekwen-sasl.log

Stack trace:
   [{rabbit_networking,start_listener0,4,[]},
    {rabbit_networking,'-start_listener/4-lc$^0/1-0-',4,[]},
    {rabbit_networking,start_listener,4,[]},
    {rabbit_networking,'-boot_tcp/0-lc$^0/1-0-',1,[]},
    {rabbit_networking,boot_tcp,0,[]},
    {rabbit_networking,boot,0,[]},
    {rabbit,'-run_boot_step/1-lc$^1/1-1-',1,[]},
    {rabbit,run_boot_step,1,[]}]

BOOT FAILED
===========

Error description:
   {could_not_start,rabbit,
    {bad_return,
     {{rabbit,start,[normal,[]]},
      {'EXIT',
       {rabbit,failure_during_boot,
        {case_clause,
         {error,
          {{shutdown,
            {failed_to_start_child,tcp_listener,
             {cannot_listen,{0,0,0,0,0,0,0,0},5672,eaddrinuse}}},
           {child,undefined,'rabbit_tcp_listener_sup_:::5672',
            {tcp_listener_sup,start_link,
             [{0,0,0,0,0,0,0,0},
              5672,
              [inet6,binary,
               {packet,raw},
               {reuseaddr,true},
               {backlog,128},
               {nodelay,true},
               {linger,{true,0}},
               {exit_on_close,false}],
              {rabbit_networking,tcp_listener_started,[amqp]},
              {rabbit_networking,tcp_listener_stopped,[amqp]},
              {rabbit_networking,start_client,[]},
              "TCP Listener"]},
            transient,infinity,supervisor,
            [tcp_listener_sup]}}}}}}}}}

Log files (may contain more information):
   /var/log/rabbitmq/rabbit@leekwen.log
   /var/log/rabbitmq/rabbit@leekwen-sasl.log

{"init terminating in do_boot",{rabbit,failure_during_boot,{could_not_start,rabb                                                                                        use,{error,{{shutdown,{failed_to_start_child,tcp_listener,{cannot_listen,{0,0,0,                                                                                        stener_sup,start_link,[{0,0,0,0,0,0,0,0},5672,[inet6,binary,{packet,raw},{reusea                                                                                        networking,tcp_listener_started,[amqp]},{rabbit_networking,tcp_listener_stopped,                                                                                        or,[tcp_listener_sup]}}}}}}}}}}}
tail: /var/log/rabbitmq/startup_log: file truncated        [FAILED]

[root@leekwen ~]# cat /var/log/rabbitmq/startup_err

Crash dump was written to: erl_crash.dump
init terminating in do_boot ()
9、出现如上的错误，可能是因为5672端口已经被占用的原因。
查看5672端口的情况，如果有进程占用此端口，请将它关闭后，重新启动RabbitMQ-Server； 
[root@leekwen ~]# netstat -atn grep 5672
tcp        0      0 0.0.0.0:5672                0.0.0.0:*                   LISTEN
[root@leekwen ~]# lsof -i:5672
COMMAND  PID  USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
qpidd   1901 qpidd   10u  IPv4  13941      0t0  TCP *:amqp (LISTEN)
[root@leekwen ~]# chkconfig qpidd off
[root@leekwen ~]# netstat -atn grep 5672
tcp        0      0 0.0.0.0:5672                0.0.0.0:*                   LISTEN
[root@leekwen ~]# chkconfig qpidd --list
qpidd           0:off   1:off   2:off   3:off   4:off   5:off   6:off
[root@leekwen ~]# /etc/init.d/qpidd stop
Stopping Qpid AMQP daemon:                                 [  OK  ]
[root@leekwen ~]# netstat -atn grep 5672
tcp        0      0 127.0.0.1:25672             127.0.0.1:60925             TIME_WAIT
[root@leekwen ~]# lsof -i:5672
[root@leekwen ~]# /etc/init.d/rabbitmq-server start
Starting rabbitmq-server: SUCCESS
rabbitmq-server.
10、查看RabbitMQ服务启动的状态，并开启RabbitMQ的相应管理插件： 
[root@leekwen ~]# rabbitmqctl status
Status of node rabbit@leekwen ...
[{pid,716},
 {running_applications,[{rabbit,"RabbitMQ","3.3.0"},
                        {os_mon,"CPO  CXC 138 46","2.2.14"},
                        {mnesia,"MNESIA  CXC 138 12","4.11"},
                        {xmerl,"XML parser","1.3.5"},
                        {sasl,"SASL  CXC 138 11","2.3.4"},
                        {stdlib,"ERTS  CXC 138 10","1.19.4"},
                        {kernel,"ERTS  CXC 138 10","2.16.4"}]},
 {os,{unix,linux}},
 {erlang_version,"Erlang R16B03 (erts-5.10.4) [source] [64-bit] [smp:8:8] [async-threads:30] [kernel-poll:true]\n"},
 {memory,[{total,36436456},
          {connection_procs,2704},
          {queue_procs,5408},
          {plugins,0},
          {other_proc,13704576},
          {mnesia,60240},
          {mgmt_db,0},
          {msg_index,24368},
          {other_ets,789624},
          {binary,13672},
          {code,16399491},
          {atom,594537},
          {other_system,4841836}]},
 {alarms,[]},
 {listeners,[{clustering,25672,"::"},{amqp,5672,"::"}]},
 {vm_memory_high_watermark,0.4},
 {vm_memory_limit,6690450636},
 {disk_free_limit,50000000},
 {disk_free,47402364928},
 {file_descriptors,[{total_limit,924},
                    {total_used,3},
                    {sockets_limit,829},
                    {sockets_used,1}]},
 {processes,[{limit,1048576},{used,131}]},
 {run_queue,0},
 {uptime,83}]
...done.

[root@leekwen ~]# netstat -atn grep 5672
tcp        0      0 0.0.0.0:25672               0.0.0.0:*                   LISTEN
tcp        0      0 :::5672                     :::*                        LISTEN
[root@leekwen ~]# lsof -i:5672
COMMAND  PID     USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
beam.smp 716 rabbitmq   15u  IPv6 1948888      0t0  TCP *:amqp (LISTEN)
[root@leekwen ~]# rabbitmq-plugins list
[ ] amqp_client                       3.3.0
[ ] cowboy                            0.5.0-rmq3.3.0-git4b93c2d
[ ] eldap                             3.3.0-gite309de4
[ ] mochiweb                          2.7.0-rmq3.3.0-git680dba8
[ ] rabbitmq_amqp1_0                  3.3.0
[ ] rabbitmq_auth_backend_ldap        3.3.0
[ ] rabbitmq_auth_mechanism_ssl       3.3.0
[ ] rabbitmq_consistent_hash_exchange 3.3.0
[ ] rabbitmq_federation               3.3.0
[ ] rabbitmq_federation_management    3.3.0
[ ] rabbitmq_management               3.3.0
[ ] rabbitmq_management_agent         3.3.0
[ ] rabbitmq_management_visualiser    3.3.0
[ ] rabbitmq_mqtt                     3.3.0
[ ] rabbitmq_shovel                   3.3.0
[ ] rabbitmq_shovel_management        3.3.0
[ ] rabbitmq_stomp                    3.3.0
[ ] rabbitmq_tracing                  3.3.0
[ ] rabbitmq_web_dispatch             3.3.0
[ ] rabbitmq_web_stomp                3.3.0
[ ] rabbitmq_web_stomp_examples       3.3.0
[ ] sockjs                            0.3.4-rmq3.3.0-git3132eb9
[ ] webmachine                        1.10.3-rmq3.3.0-gite9359c7
[root@leekwen ~]# rabbitmq-plugins enable rabbitmq_management
The following plugins have been enabled:
  mochiweb
  webmachine
  rabbitmq_web_dispatch
  amqp_client
  rabbitmq_management_agent
  rabbitmq_management
Plugin configuration has changed. Restart RabbitMQ for changes to take effect.
[root@leekwen ~]# rabbitmq-plugins enable mochiweb webmachine rabbitmq_web_dispatch amqp_client rabbitmq_m                                                             anagement_agent rabbitmq_management
Plugin configuration unchanged.
[root@leekwen ~]# rabbitmq-plugins list
[E] amqp_client                       3.3.0
[ ] cowboy                            0.5.0-rmq3.3.0-git4b93c2d
[ ] eldap                             3.3.0-gite309de4
[E] mochiweb                          2.7.0-rmq3.3.0-git680dba8
[ ] rabbitmq_amqp1_0                  3.3.0
[ ] rabbitmq_auth_backend_ldap        3.3.0
[ ] rabbitmq_auth_mechanism_ssl       3.3.0
[ ] rabbitmq_consistent_hash_exchange 3.3.0
[ ] rabbitmq_federation               3.3.0
[ ] rabbitmq_federation_management    3.3.0
[E] rabbitmq_management               3.3.0
[E] rabbitmq_management_agent         3.3.0
[ ] rabbitmq_management_visualiser    3.3.0
[ ] rabbitmq_mqtt                     3.3.0
[ ] rabbitmq_shovel                   3.3.0
[ ] rabbitmq_shovel_management        3.3.0
[ ] rabbitmq_stomp                    3.3.0
[ ] rabbitmq_tracing                  3.3.0
[E] rabbitmq_web_dispatch             3.3.0
[ ] rabbitmq_web_stomp                3.3.0
[ ] rabbitmq_web_stomp_examples       3.3.0
[ ] sockjs                            0.3.4-rmq3.3.0-git3132eb9
[E] webmachine                        1.10.3-rmq3.3.0-gite9359c7
[root@leekwen ~]# rabbitmq-plugins list
[E] amqp_client                       3.3.0
[ ] cowboy                            0.5.0-rmq3.3.0-git4b93c2d
[ ] eldap                             3.3.0-gite309de4
[E] mochiweb                          2.7.0-rmq3.3.0-git680dba8
[ ] rabbitmq_amqp1_0                  3.3.0
[ ] rabbitmq_auth_backend_ldap        3.3.0
[ ] rabbitmq_auth_mechanism_ssl       3.3.0
[ ] rabbitmq_consistent_hash_exchange 3.3.0
[ ] rabbitmq_federation               3.3.0
[ ] rabbitmq_federation_management    3.3.0
[E] rabbitmq_management               3.3.0
[E] rabbitmq_management_agent         3.3.0
[ ] rabbitmq_management_visualiser    3.3.0
[ ] rabbitmq_mqtt                     3.3.0
[ ] rabbitmq_shovel                   3.3.0
[ ] rabbitmq_shovel_management        3.3.0
[ ] rabbitmq_stomp                    3.3.0
[ ] rabbitmq_tracing                  3.3.0
[E] rabbitmq_web_dispatch             3.3.0
[ ] rabbitmq_web_stomp                3.3.0
[ ] rabbitmq_web_stomp_examples       3.3.0
[ ] sockjs                            0.3.4-rmq3.3.0-git3132eb9
[E] webmachine                        1.10.3-rmq3.3.0-gite9359c7
[root@leekwen ~]# netstat -atn grep 5672
tcp        0      0 0.0.0.0:25672               0.0.0.0:*                   LISTEN
tcp        0      0 :::5672                     :::*                        LISTEN
[root@leekwen ~]# netstat -atn grep 15672
[root@leekwen ~]# netstat -atn grep 55672
[root@leekwen ~]# /etc/init.d/rabbitmq-server restart
Restarting rabbitmq-server: SUCCESS
rabbitmq-server.
[root@leekwen ~]# netstat -atn grep 55672
[root@leekwen ~]# netstat -atn grep 5672
tcp        0      0 0.0.0.0:15672               0.0.0.0:*                   LISTEN
tcp        0      0 0.0.0.0:25672               0.0.0.0:*                   LISTEN
tcp        0      0 127.0.0.1:54463             127.0.0.1:25672             TIME_WAIT
tcp        0      0 127.0.0.1:60321             127.0.0.1:25672             TIME_WAIT
tcp        0      0 127.0.0.1:25672             127.0.0.1:56750             TIME_WAIT
tcp        0      0 :::5672                     :::*                        LISTEN

就可以用guest,guest登陆http://192.168.1.101:15672端口了。

注意：如果此时你从端口15672或55672登陆不了，请关闭CentOS6.2的防火墙，再次登陆,

如果仍然出现无法登陆的想象，查看日志后，显示：

=ERROR REPORT==== 20-Apr-2014::00:55:15 ===
webmachine error: path="api/whoami"
"Unauthorized"
那么请运行如下的命令，增加用户admin，密码admin即可。   
[root@leekwen ~]# rabbitmqctl add_user admin admin
Creating user "admin" ...
...done.
[root@leekwen ~]# rabbitmqctl list_users
Listing users ...
admin   []
guest   [administrator]
...done.
[root@leekwen ~]# rabbitmqctl set_user_tags admin administrator
Setting tags for user "admin" to [administrator] ...
...done.
[root@leekwen ~]# rabbitmqctl list_users
Listing users ...
admin   [administrator]
guest   [administrator]
...done.
到此，配置完成。 
分享到：
| django异步任务celery，分布式队列(redis/r ...
评论
发表评论

您还没有登录,请您登录后再发表评论

相关推荐

    rabbitmq安装.doc

    linux系统中安装rabbitmq安装，异常处理，启动停止等操作，用户管理密码设置等 1. 安装erlang20.3.7 2. 安装rabbitmq 3. 启动服务，并设置权限

    rabbitmq消费失败处理

    RabbitMQ 消费失败处理 RabbitMQ 是一种流行的消息队列系统，用于实现异步通信和解耦合应用程序。在使用 RabbitMQ 时，消费失败处理是非常重要的一环，本文将详细介绍 RabbitMQ 消费失败处理的处理流程和配置方法。...

    RabbitMQ安装.rar

    这些库提供了API来创建连接、发布和消费消息，以及处理各种异常情况。 9. **监控与日志**: 了解如何配置RabbitMQ的日志记录和性能监控。通过日志，可以跟踪和诊断任何运行时问题。RabbitMQ还提供了多种插件，用于...

    RabbitMQ安装配置.docx

    RabbitMQ 是一个开源的消息队列系统，广泛用于分布式系统中的异步处理、解耦以及负载均衡。它基于AMQP（Advanced Message ...此外，了解如何处理消息的死信、监控队列状态以及异常处理也是确保系统稳定运行的关键。

    tp6使用rabbitmq

    8. **异常处理与确认**：为了保证消息的可靠性，可以启用消费者确认机制。当消息被正确处理后，消费者需要发送一个确认信号给RabbitMQ，否则消息将被重新投递。同时，应妥善处理异常，避免因为错误导致消息丢失。 9...

    rabbitmq部署包及部署文档

    10. **异常处理与错误排查**：了解如何处理连接中断、消息丢失等问题，以及如何通过日志和监控工具进行问题排查。 通过"部署包"，你可以获取预先配置好的RabbitMQ环境，这对于快速搭建测试环境或演示示例非常有用。...

    RabbitMQ的简单介绍、安装及与SpringBoot整合构建高可用的消息传递方案

    6. **监控与报警**：结合Prometheus和Grafana可以对RabbitMQ进行性能监控，当出现异常情况时，可以通过Alertmanager发送报警。 通过以上介绍，我们了解了RabbitMQ的基本概念、安装方法、Java集成以及如何构建高可用...

    shell脚本监控rabbitmq异常发送邮件通知.rar

    标题"shell脚本监控rabbitmq异常发送邮件通知.rar"表明这个压缩包包含了一个用Shell编写的脚本，其主要功能是对RabbitMQ集群进行健康检查，并在发现异常时通过邮件通知管理员。这对于及时发现和解决问题至关重要，...

    RabbitMQ实战指南-rabbitmq-action.zip

    1. **死信队列**: 当消息无法路由、队列满或消费者拒绝消息时，可以设置死信队列来处理这些异常情况。 2. **优先级**: 队列可以设置消息优先级，优先级高的消息会被优先消费。 3. **持久化**: 通过设置消息和队列...

    RabbitMQ源码和客户端工具

    9. **异常处理与错误恢复** 通过源码，我们可以看到RabbitMQ客户端如何处理网络故障、服务器异常等错误情况，以及如何实现重连和自动恢复策略。 10. **性能优化** 分析源码还可以发现RabbitMQ如何优化内存管理、...

    C# RabbitMQ Helper 帮助类

    6. **异常处理**：内置异常处理机制，能够捕获并适当地处理RabbitMQ操作过程中可能出现的错误。 **三、使用方法** 1. **引入DLL**：将C# RabbitMQ Helper编译后的DLL文件引入到你的项目中，添加对它的引用。 2. *...

    java rabbitmq动态注册，监听实现

    综上所述，"java rabbitmq动态注册，监听实现"这个主题涵盖了Spring Boot与RabbitMQ的集成、动态注册消费者、消息监听、异常处理等多个核心知识点。通过合理地运用这些技术，可以构建一个灵活且可靠的分布式消息处理...

    RabbitMQ工具类封装实现

    4. **异常处理**：确保在可能出现异常的地方添加合适的异常捕获和处理机制，以保证服务的稳定性。 接下来，`MQPublishService.java`表示发布者服务，它负责发送消息到RabbitMQ。封装发布者线程涉及的主要知识点有：...

    RabbitMQ测试代码

    8. **异常处理与确认机制**：确保消息的可靠传输，代码可能包含异常处理逻辑，以及使用消息确认机制（publisher confirms或consumer acknowledges）来跟踪消息是否成功送达。 9. **队列持久化与消息持久性**：为了...

    rabbitmq-server-3.9.10.rar

    3. 错误恢复：通过消息持久化和死信队列，RabbitMQ可以保证消息在异常情况下不丢失，便于故障恢复。 4. 日志聚合：在日志收集系统中，RabbitMQ可接收来自各个节点的日志，再转发给日志分析系统。 总结，RabbitMQ ...

    Django+celery+rabbitmq配置文档

    ### Django+Celery+RabbitMQ配置文档 ...- **异常处理**: 对任务中的异常情况进行捕获和处理，确保系统的稳定性和健壮性。 通过以上步骤，可以实现基于Django框架的异步任务处理功能，提高系统的响应速度和处理能力。

    rabbitMQ_Demo_rabbitMQ_Demo_rabbitmq_boyyeu_DEMO_中间件_

    8. **异常处理**：理解如何处理消费消息时可能出现的异常，如重新入队、确认机制和重试策略。 9. **性能优化**：包括合理设置队列大小、减少网络延迟、优化消息格式等。 10. **监控与日志**：利用 RabbitMQ 提供的...

    RabbitMq技术文档

    4. **异常处理**：定义异常处理器，处理消息发送过程中可能出现的问题。 #### 六、总结 RabbitMQ 作为一种成熟的消息队列服务，在分布式系统中扮演着重要的角色。无论是实现微服务间的通信、异步处理还是日志收集...

    RabbitMQ客户端Qt项目工程

    - **异常处理**：捕获可能出现的异常，如网络错误，以提供良好的用户体验。 - **消息序列化和反序列化**：根据应用需求，可能需要将C++对象转换为AMQP消息格式，或反之。 通过这个RabbitMQ客户端工程，开发者不仅...

    beego环境下 rabbitmq封装以及使用

    同时，确保正确处理连接异常和关闭。 3. **声明交换机和队列**：根据业务需求，声明所需的交换机类型（如Direct、Fanout、Topic或Header）和队列。交换机决定了消息如何路由，而队列则存储待处理的消息。 4. **...

Magicbox
Global site tag (gtag.js) - Google Analytics