"rabbitmq-server.service" Service still in 'activating' state, bailing out

2,783 views
Skip to first unread message

po...@platform9.com

unread,
Mar 23, 2018, 4:10:08 PM3/23/18
to rabbitmq-users
Hi, 

I am having trouble getting the rabbitmq service to start with latest rabbitmq-server and erlang packages on a Centos7.4 VM.
Looks like the service is running fine, but systemd unit gets stuck in 'activating' state.

Can someone please help me understand if this is a configuration issue or some dependency is missing?

# rpm -qa | grep rabbitmq
rabbitmq-server-3.7.4-1.el7.noarch

# rpm -qa | grep erlang
erlang-20.3-1.el7.centos.x86_64

# Log snippet:

2018-03-23 20:02:32.338 [info] <0.368.0> started TCP Listener on [::]:5672

2018-03-23 20:02:32.345 [info] <0.263.0> Setting up a table for connection tracking on this node: tracked_connection_on_node_rabbit@localhost

2018-03-23 20:02:32.346 [info] <0.263.0> Setting up a table for per-vhost connection counting on this node: tracked_connection_per_vhost_on_node_rabbit@localhost

2018-03-23 20:02:32.348 [info] <0.33.0> Application rabbit started on node rabbit@localhost

2018-03-23 20:02:42.961 [notice] <0.85.0> Changed loghwm of /var/log/rabbitmq/rab...@localhost.log to 50

2018-03-23 20:02:44.107 [info] <0.5.0> Server startup complete; 0 plugins started.


# service rabbitmq-server status
Redirecting to /bin/systemctl status rabbitmq-server.service
● rabbitmq-server.service - RabbitMQ broker
   Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; disabled; vendor preset: disabled)
   Active: activating (start) since Fri 2018-03-23 20:02:12 UTC; 32s ago
  Process: 996 ExecStop=/usr/sbin/rabbitmqctl shutdown (code=exited, status=69)
 Main PID: 2880 (beam.smp)
   CGroup: /system.slice/rabbitmq-server.service
           ├─2880 /usr/lib64/erlang/erts-9.3/bin/beam.smp -W w -A 64 -P 1048576 -t 5000000 -stbt db -zdbbl 1280000 -K true -- -root /usr/lib64/erlang -progname erl -- -home /v...
           ├─3195 erl_child_setup 1024
           ├─3348 inet_gethost 4
           └─3349 inet_gethost 4

Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: ##  ##      RabbitMQ 3.7.4. Copyright (C) 2007-2018 Pivotal Software, Inc.
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: ##########  Licensed under the MPL.  See http://www.rabbitmq.com/
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: ######  ##
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: ##########  Logs: /var/log/rabbitmq/rab...@localhost.log
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: /var/log/rabbitmq/rabbit@localhost_upgrade.log
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: Starting broker...
Mar 23 20:02:32 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: systemd unit for activation check: "rabbitmq-server.service"
Mar 23 20:02:42 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: Service still in 'activating' state, bailing out
Mar 23 20:02:42 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: systemd READY notification failed, beware of timeouts
Mar 23 20:02:44 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: completed with 0 plugins.


Based on some post in this forum, I ran the below diagnostics command:

# rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().' 
2018-03-23 20:05:04 There are 202 processes.
2018-03-23 20:05:09 Found 1 suspicious processes.
2018-03-23 20:05:09 [{pid,<9193.1.0>},
                     {registered_name,erts_code_purger},
                     {current_stacktrace,
                         [{erts_code_purger,wait_for_request,0,[]}]},
                     {initial_call,{erts_code_purger,start,0}},
                     {message_queue_len,0},
                     {links,[]},
                     {monitors,[]},
                     {monitored_by,[]},
                     {heap_size,233}]
ok


Thanks,
Pooja

Michael Klishin

unread,
Mar 23, 2018, 4:21:36 PM3/23/18
to rabbitm...@googlegroups.com
Can you please post server logs?

Note that in 3.7.x you can enable debug logging: http://www.rabbitmq.com/logging.html, http://www.rabbitmq.com/configure.html.

On Fri, Mar 23, 2018 at 11:10 PM, <po...@platform9.com> wrote:
Hi, 

I am having trouble getting the rabbitmq service to start with latest rabbitmq-server and erlang packages on a Centos7.4 VM.
Looks like the service is running fine, but systemd unit gets stuck in 'activating' state.

Can someone please help me understand if this is a configuration issue or some dependency is missing?

# rpm -qa | grep rabbitmq
rabbitmq-server-3.7.4-1.el7.noarch

# rpm -qa | grep erlang
erlang-20.3-1.el7.centos.x86_64

# Log snippet:

2018-03-23 20:02:32.338 [info] <0.368.0> started TCP Listener on [::]:5672

2018-03-23 20:02:32.345 [info] <0.263.0> Setting up a table for connection tracking on this node: tracked_connection_on_node_rabbit@localhost

2018-03-23 20:02:32.346 [info] <0.263.0> Setting up a table for per-vhost connection counting on this node: tracked_connection_per_vhost_on_node_rabbit@localhost

2018-03-23 20:02:32.348 [info] <0.33.0> Application rabbit started on node rabbit@localhost

2018-03-23 20:02:42.961 [notice] <0.85.0> Changed loghwm of /var/log/rabbitmq/rabbit@localhost.log to 50

2018-03-23 20:02:44.107 [info] <0.5.0> Server startup complete; 0 plugins started.


# service rabbitmq-server status
Redirecting to /bin/systemctl status rabbitmq-server.service
● rabbitmq-server.service - RabbitMQ broker
   Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; disabled; vendor preset: disabled)
   Active: activating (start) since Fri 2018-03-23 20:02:12 UTC; 32s ago
  Process: 996 ExecStop=/usr/sbin/rabbitmqctl shutdown (code=exited, status=69)
 Main PID: 2880 (beam.smp)
   CGroup: /system.slice/rabbitmq-server.service
           ├─2880 /usr/lib64/erlang/erts-9.3/bin/beam.smp -W w -A 64 -P 1048576 -t 5000000 -stbt db -zdbbl 1280000 -K true -- -root /usr/lib64/erlang -progname erl -- -home /v...
           ├─3195 erl_child_setup 1024
           ├─3348 inet_gethost 4
           └─3349 inet_gethost 4

Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: ##  ##      RabbitMQ 3.7.4. Copyright (C) 2007-2018 Pivotal Software, Inc.
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: ##########  Licensed under the MPL.  See http://www.rabbitmq.com/
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: ######  ##
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: ##########  Logs: /var/log/rabbitmq/rabbit@localhost.log
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: /var/log/rabbitmq/rabbit@localhost_upgrade.log
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: Starting broker...
Mar 23 20:02:32 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: systemd unit for activation check: "rabbitmq-server.service"
Mar 23 20:02:42 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: Service still in 'activating' state, bailing out
Mar 23 20:02:42 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: systemd READY notification failed, beware of timeouts
Mar 23 20:02:44 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: completed with 0 plugins.


Based on some post in this forum, I ran the below diagnostics command:

# rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().' 
2018-03-23 20:05:04 There are 202 processes.
2018-03-23 20:05:09 Found 1 suspicious processes.
2018-03-23 20:05:09 [{pid,<9193.1.0>},
                     {registered_name,erts_code_purger},
                     {current_stacktrace,
                         [{erts_code_purger,wait_for_request,0,[]}]},
                     {initial_call,{erts_code_purger,start,0}},
                     {message_queue_len,0},
                     {links,[]},
                     {monitors,[]},
                     {monitored_by,[]},
                     {heap_size,233}]
ok


Thanks,
Pooja

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
MK

Staff Software Engineer, Pivotal/RabbitMQ

Michael Klishin

unread,
Mar 23, 2018, 4:25:25 PM3/23/18
to rabbitm...@googlegroups.com
the output of `rabbit_diagnostics:maybe_stuck/0` reveals nothing interesting. There's one
process that always waits for requests to purge some outdated code modules (during a hot code swapping upgrade, a feature RabbitMQ
currently does not use).

The node reports that it's started successfully with no plugins enabled (so plugin startup cannot possibly fail, for example).

Most likely the problem comes down to sending a notification to systemd which in 3.7.x happens via a shellout to `socat`:


and `socat` is a program that usually comes in a package with the same name. At least on Debian socat is an explicit package dependency.

On Fri, Mar 23, 2018 at 11:10 PM, <po...@platform9.com> wrote:
Hi, 

I am having trouble getting the rabbitmq service to start with latest rabbitmq-server and erlang packages on a Centos7.4 VM.
Looks like the service is running fine, but systemd unit gets stuck in 'activating' state.

Can someone please help me understand if this is a configuration issue or some dependency is missing?

# rpm -qa | grep rabbitmq
rabbitmq-server-3.7.4-1.el7.noarch

# rpm -qa | grep erlang
erlang-20.3-1.el7.centos.x86_64

# Log snippet:

2018-03-23 20:02:32.338 [info] <0.368.0> started TCP Listener on [::]:5672

2018-03-23 20:02:32.345 [info] <0.263.0> Setting up a table for connection tracking on this node: tracked_connection_on_node_rabbit@localhost

2018-03-23 20:02:32.346 [info] <0.263.0> Setting up a table for per-vhost connection counting on this node: tracked_connection_per_vhost_on_node_rabbit@localhost

2018-03-23 20:02:32.348 [info] <0.33.0> Application rabbit started on node rabbit@localhost

2018-03-23 20:02:42.961 [notice] <0.85.0> Changed loghwm of /var/log/rabbitmq/rabbit@localhost.log to 50

2018-03-23 20:02:44.107 [info] <0.5.0> Server startup complete; 0 plugins started.


# service rabbitmq-server status
Redirecting to /bin/systemctl status rabbitmq-server.service
● rabbitmq-server.service - RabbitMQ broker
   Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; disabled; vendor preset: disabled)
   Active: activating (start) since Fri 2018-03-23 20:02:12 UTC; 32s ago
  Process: 996 ExecStop=/usr/sbin/rabbitmqctl shutdown (code=exited, status=69)
 Main PID: 2880 (beam.smp)
   CGroup: /system.slice/rabbitmq-server.service
           ├─2880 /usr/lib64/erlang/erts-9.3/bin/beam.smp -W w -A 64 -P 1048576 -t 5000000 -stbt db -zdbbl 1280000 -K true -- -root /usr/lib64/erlang -progname erl -- -home /v...
           ├─3195 erl_child_setup 1024
           ├─3348 inet_gethost 4
           └─3349 inet_gethost 4

Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: ##  ##      RabbitMQ 3.7.4. Copyright (C) 2007-2018 Pivotal Software, Inc.
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: ##########  Licensed under the MPL.  See http://www.rabbitmq.com/
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: ######  ##
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: ##########  Logs: /var/log/rabbitmq/rabbit@localhost.log
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: /var/log/rabbitmq/rabbit@localhost_upgrade.log
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: Starting broker...
Mar 23 20:02:32 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: systemd unit for activation check: "rabbitmq-server.service"
Mar 23 20:02:42 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: Service still in 'activating' state, bailing out
Mar 23 20:02:42 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: systemd READY notification failed, beware of timeouts
Mar 23 20:02:44 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: completed with 0 plugins.


Based on some post in this forum, I ran the below diagnostics command:

# rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().' 
2018-03-23 20:05:04 There are 202 processes.
2018-03-23 20:05:09 Found 1 suspicious processes.
2018-03-23 20:05:09 [{pid,<9193.1.0>},
                     {registered_name,erts_code_purger},
                     {current_stacktrace,
                         [{erts_code_purger,wait_for_request,0,[]}]},
                     {initial_call,{erts_code_purger,start,0}},
                     {message_queue_len,0},
                     {links,[]},
                     {monitors,[]},
                     {monitored_by,[]},
                     {heap_size,233}]
ok


Thanks,
Pooja

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Luke Bakken

unread,
Mar 23, 2018, 4:55:03 PM3/23/18
to rabbitmq-users
Hi Pooja,

Could you please check that the socat package is installed? It is available via EPEL.

RabbitMQ uses the socat program to communicate its status back to systemd. If you installed those two rpm packages using yum, it should have warned you about a missing dependency.

Thanks,
Luke

po...@platform9.com

unread,
Mar 23, 2018, 5:01:31 PM3/23/18
to rabbitmq-users
Hi Michael,

I am attaching the server log with debug level turned on here.

Logs from /var/log/messages:
Mar 23 20:52:12 test-pf9-du-install-1898-2018-03-22-192546 systemd: Starting RabbitMQ broker...
Mar 23 20:52:24 test-pf9-du-install-1898-2018-03-22-192546 rabbitmq-server: ##  ##
Mar 23 20:52:24 test-pf9-du-install-1898-2018-03-22-192546 rabbitmq-server: ##  ##      RabbitMQ 3.7.4. Copyright (C) 2007-2018 Pivotal Software, Inc.
Mar 23 20:52:24 test-pf9-du-install-1898-2018-03-22-192546 rabbitmq-server: ##########  Licensed under the MPL.  See http://www.rabbitmq.com/
Mar 23 20:52:24 test-pf9-du-install-1898-2018-03-22-192546 rabbitmq-server: ######  ##
Mar 23 20:52:24 test-pf9-du-install-1898-2018-03-22-192546 rabbitmq-server: ##########  Logs: /var/log/rabbitmq/file.log
Mar 23 20:52:24 test-pf9-du-install-1898-2018-03-22-192546 rabbitmq-server: /var/log/rabbitmq/rabbit@localhost_upgrade.log
Mar 23 20:52:24 test-pf9-du-install-1898-2018-03-22-192546 rabbitmq-server: Starting broker...
Mar 23 20:52:32 test-pf9-du-install-1898-2018-03-22-192546 rabbitmq-server: systemd unit for activation check: "rabbitmq-server.service"
Mar 23 20:52:42 test-pf9-du-install-1898-2018-03-22-192546 rabbitmq-server: Service still in 'activating' state, bailing out
Mar 23 20:52:42 test-pf9-du-install-1898-2018-03-22-192546 rabbitmq-server: systemd READY notification failed, beware of timeouts
Mar 23 20:52:44 test-pf9-du-install-1898-2018-03-22-192546 rabbitmq-server: completed with 0 plugins.
~                                                                                                         


Thanks,
Pooja


On Friday, March 23, 2018 at 1:10:08 PM UTC-7, po...@platform9.com wrote:
Hi, 

I am having trouble getting the rabbitmq service to start with latest rabbitmq-server and erlang packages on a Centos7.4 VM.
Looks like the service is running fine, but systemd unit gets stuck in 'activating' state.

Can someone please help me understand if this is a configuration issue or some dependency is missing?

# rpm -qa | grep rabbitmq
rabbitmq-server-3.7.4-1.el7.noarch

# rpm -qa | grep erlang
erlang-20.3-1.el7.centos.x86_64

# Log snippet:

2018-03-23 20:02:32.338 [info] <0.368.0> started TCP Listener on [::]:5672

2018-03-23 20:02:32.345 [info] <0.263.0> Setting up a table for connection tracking on this node: tracked_connection_on_node_rabbit@localhost

2018-03-23 20:02:32.346 [info] <0.263.0> Setting up a table for per-vhost connection counting on this node: tracked_connection_per_vhost_on_node_rabbit@localhost

2018-03-23 20:02:32.348 [info] <0.33.0> Application rabbit started on node rabbit@localhost

2018-03-23 20:02:42.961 [notice] <0.85.0> Changed loghwm of /var/log/rabbitmq/rabbit@localhost.log to 50

2018-03-23 20:02:44.107 [info] <0.5.0> Server startup complete; 0 plugins started.


# service rabbitmq-server status
Redirecting to /bin/systemctl status rabbitmq-server.service
● rabbitmq-server.service - RabbitMQ broker
   Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; disabled; vendor preset: disabled)
   Active: activating (start) since Fri 2018-03-23 20:02:12 UTC; 32s ago
  Process: 996 ExecStop=/usr/sbin/rabbitmqctl shutdown (code=exited, status=69)
 Main PID: 2880 (beam.smp)
   CGroup: /system.slice/rabbitmq-server.service
           ├─2880 /usr/lib64/erlang/erts-9.3/bin/beam.smp -W w -A 64 -P 1048576 -t 5000000 -stbt db -zdbbl 1280000 -K true -- -root /usr/lib64/erlang -progname erl -- -home /v...
           ├─3195 erl_child_setup 1024
           ├─3348 inet_gethost 4
           └─3349 inet_gethost 4

Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: ##  ##      RabbitMQ 3.7.4. Copyright (C) 2007-2018 Pivotal Software, Inc.
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: ##########  Licensed under the MPL.  See http://www.rabbitmq.com/
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: ######  ##
Mar 23 20:02:24 test-pf9-du-install-1898-2018-03-22-192546.novalocal rabbitmq-server[2880]: ##########  Logs: /var/log/rabbitmq/rabbit@localhost.log
rabbitmq.rtf

po...@platform9.com

unread,
Mar 23, 2018, 5:03:26 PM3/23/18
to rabbitmq-users
Hi Luke,

I just verified that the socat package is installed on my machine.
Does it need a specific version?

# rpm -qa | grep socat

socat-1.7.3.2-2.el7.x86_64



Thanks,
Pooja

Michael Klishin

unread,
Mar 23, 2018, 5:19:26 PM3/23/18
to rabbitm...@googlegroups.com
No, any version should do. However it should be in PATH for the rabbitmq user
and it needs to have the permissions to execute it.

If the NOTIFY_SOCKET env variable is set, RabbitMQ will use it to communicate
with socat.

Then RabbitMQ will use systemctl to wait for service activation.

The logs suggest the node starts without any issues. Take a look at the systemd or other logs
that might log any security violations that might prevent socat invocations.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Message has been deleted

po...@platform9.com

unread,
Mar 23, 2018, 6:54:46 PM3/23/18
to rabbitmq-users
Thanks Michael and Luke!

I just reinstalled the latest socat package and rabbitmq-server was able to start fine. Something must have been messed up with the VM image I was using which had socat preinstalled.

Regards,
Pooja


To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Michael Klishin

unread,
Mar 25, 2018, 4:54:08 PM3/25/18
to rabbitm...@googlegroups.com
You cannot disable it and if you do, you must have a binary sd_notify package + its Erlang wrapper, or else systemd won't
know that RabbitMQ has started.

On Sat, Mar 24, 2018 at 1:06 AM, <po...@platform9.com> wrote:
Thanks Michael!

All I see is this in the audit.log on my centos machine:

type=SERVICE_START msg=audit(1521841984.042:2269): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=rabbitmq-server comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'


Is this socat notify something I should disable? My rabbitmq-env file does not explicitly enable it:

# cat /etc/rabbitmq/rabbitmq-env.conf 
NODENAME=rabbit@localhost
RABBITMQ_LOG_BASE=/var/log/rabbitmq
RABBITMQ_PID_FILE=/var/run/rabbitmq/pid

Also I am using the systemd unit file that was part of the github package.

Thanks,
Pooja


On Friday, March 23, 2018 at 2:19:26 PM UTC-7, Michael Klishin wrote:
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
MK

Staff Software Engineer, Pivotal/RabbitMQ

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages