Rabbit-MQ version 3.2.1 command-line to unbind a queue from an exchange.

AMS

unread,

May 26, 2015, 4:56:56 PM5/26/15

to rabbitm...@googlegroups.com

I've inherited an active RMQ installation (ver 3.2.1) and am looking for some information on how to unbind a queue from an exchange.

One of the queues running is bound to an exchange, but it no longer is needed. It has no consumers of the data anymore, so this queue can be unbound and the data purged.

I've got two questions (semi-related) on this machine.

#1) Can I issue a command via the cli that will unbind and then purge the data in this queue?

Is there any command like:

> sudo rabbitmqctl ....

which can do this?

#2) I cannot any longer attach to the RMQ UI (rabbitmq_management). I'm trying to find a way to bring the UI back. My original thought was:

sudo rabbitmq-plugins disable rabbitmq_management

followed by

sudo rabbitmq-plugins enable rabbitmq_management

However since this is version 3.2.1, and I've read you cannot do that without a restart until 3.4.0. ...

Again, I've inherited the RMQ systems here, and the people that set-up managed these systems have move on, so I'm looking for resources to get up to speed on this system which keeping it running in a live environment.

Alan

Michael Klishin

unread,

May 26, 2015, 7:17:42 PM5/26/15

to rabbitm...@googlegroups.com, AMS

On 26 May 2015 at 23:56:58, AMS (dever...@gmail.com) wrote:
> #1) Can I issue a command via the cli that will unbind and then
> purge the data in this queue?
>
> Is there any command like:
>
> > sudo rabbitmqctl ....
>
> which can do this?

rabbitmqadmin is probably what you want (part of the mgmt plugin)

You can also purge a queue first using any client you want,
some are very easy to use from a REPL (e.g. Bunny or Python ones).

> #2) I cannot any longer attach to the RMQ UI (rabbitmq_management).
> I'm trying to find a way to bring the UI back.

That's not how you fix things. See what's going on in the log and
tools such as iostat and vmstat.
--
MK

Staff Software Engineer, Pivotal/RabbitMQ

AMS

unread,

May 27, 2015, 4:44:51 PM5/27/15

to rabbitm...@googlegroups.com, dever...@gmail.com

> #1) Can I issue a command via the cli that will unbind and then
> purge the data in this queue?
>
> Is there any command like:
>
> > sudo rabbitmqctl ....
>
> which can do this?

rabbitmqadmin is probably what you want (part of the mgmt plugin)

Thanks. I've been searching "rabbitmqadmin" commands and find something like:

sudo rabbitmqadmin -u {user} -p {password} -V / delete queue name={name}

but isn't that a moot point if rabbitmq_management plugin isn't running?

You can also purge a queue first using any client you want,
some are very easy to use from a REPL (e.g. Bunny or Python ones).

> #2) I cannot any longer attach to the RMQ UI (rabbitmq_management).
> I'm trying to find a way to bring the UI back.

That's not how you fix things. See what's going on in the log and
tools such as iostat and vmstat.

These machine have been running for over a year and it looks like (via netstat which I did earlier) that the UI has accumulated a bunch of CLOSE_WAIT TCP connections. I'm new to RMQ, so am open to suggestions on how to diagnose and fix this. If we can get the rabbitmq_management UI back the CLI command won't be needed, since I would unbind via the interface.

Since this is 3.2.1 the disable/enable by itself doesn't seem to be enough. Can you restart the server without disrupting the queues?

Michael Klishin

unread,

May 27, 2015, 7:49:49 PM5/27/15

to AMS, rabbitm...@googlegroups.com

> On 27/5/2015, at 23:44, AMS <dever...@gmail.com> wrote:
>
> These machine have been running for over a year and it looks like (via netstat which I did earlier) that the UI has accumulated a bunch of CLOSE_WAIT TCP connections. I'm new to RMQ, so am open to suggestions on how to diagnose and fix this. If we can get the rabbitmq_management UI back the CLI command won't be needed, since I would unbind via the interface.

"Expired" connections should go away after a period of time (in minutes), until something opens new ones all the time, of course.

> Since this is 3.2.1 the disable/enable by itself doesn't seem to be enough. Can you restart the server without disrupting the queues?

Depends on how you define "disrupted". Client connections will be dropped but persistent messages in durable queues will still be around.

AMS

unread,

May 29, 2015, 4:53:14 PM5/29/15

to rabbitm...@googlegroups.com, dever...@gmail.com

> Depends on how you define "disrupted". Client connections will be dropped but persistent messages in durable queues will still be around.

Below is "rabbitmqctl report" with IPs obscured. This system needs to keep running and the admin UI isn't accessible, but I need to unbind and purge the "dynamo-history-2" queue which no longer has any consumers. What is the best course of action?

----

Reporting server status on {{2015,5,29},{20,19,25}}

...

Status of node 'rabbit@ip-10-..—..53' ...

[{pid,1251},

{running_applications,

[{rabbitmq_management,"RabbitMQ Management Console","3.2.1"},

{rabbitmq_web_dispatch,"RabbitMQ Web Dispatcher","3.2.1"},

{webmachine,"webmachine","1.10.3-rmq3.2.1-gite9359c7"},

{mochiweb,"MochiMedia Web Server","2.7.0-rmq3.2.1-git680dba8"},

{rabbitmq_management_agent,"RabbitMQ Management Agent","3.2.1"},

{rabbit,"RabbitMQ","3.2.1"},

{os_mon,"CPO CXC 138 46","2.2.12"},

{inets,"INETS CXC 138 49","5.9.5"},

{mnesia,"MNESIA CXC 138 12","4.9"},

{amqp_client,"RabbitMQ AMQP Client","3.2.1"},

{xmerl,"XML parser","1.3.3"},

{ssl,"Erlang/OTP SSL application","5.3.1"},

{public_key,"Public key infrastructure","0.19"},

{crypto,"CRYPTO version 2","3.0"},

{asn1,"The Erlang ASN1 compiler version 2.0.2","2.0.2"},

{sasl,"SASL CXC 138 11","2.3.2"},

{stdlib,"ERTS CXC 138 10","1.19.3"},

{kernel,"ERTS CXC 138 10","2.16.3"}]},

{os,{unix,linux}},

{erlang_version,

"Erlang R16B02 (erts-5.10.3) [source-b44b726] [64-bit] [smp:4:4] [async-threads:30] [hipe] [kernel-poll:true]\n"},

{memory,

[{total,3966550384},

{connection_procs,1780488},

{queue_procs,16394008},

{plugins,428024},

{other_proc,13787272},

{mnesia,74528},

{mgmt_db,875152},

{msg_index,3459759840},

{other_ets,434386224},

{binary,8134976},

{code,21850359},

{atom,2328889},

{other_system,6750624}]},

{vm_memory_high_watermark,0.4},

{vm_memory_limit,6283106713},

{disk_free_limit,50000000},

{disk_free,63282221056},

{file_descriptors,

[{total_limit,924},

{total_used,16},

{sockets_limit,829},

{sockets_used,12}]},

{processes,[{limit,1048576},{used,322}]},

{run_queue,0},

{uptime,30921791}]

Cluster status of node 'rabbit@ip-10-..-..-53' ...

[{nodes,[{disc,['rabbit@ip-10-..-..-53','rabbit@ip-10-..-..-186']}]},

{running_nodes,['rabbit@ip-10-..-..-53']},

{partitions,[]}]

Application environment of node 'rabbit@ip-10-..-..-53' ...

[{auth_backends,[rabbit_auth_backend_internal]},

{auth_mechanisms,['PLAIN','AMQPLAIN']},

{backing_queue_module,rabbit_variable_queue},

{cluster_nodes,{[],disc}},

{cluster_partition_handling,ignore},

{collect_statistics,fine},

{collect_statistics_interval,5000},

{default_permissions,[<<".*">>,<<".*">>,<<".*">>]},

{default_user,<<"guest">>},

{default_user_tags,[administrator]},

{default_vhost,<<"/">>},

{delegate_count,16},

{disk_free_limit,50000000},

{enabled_plugins_file,"/etc/rabbitmq/enabled_plugins"},

{error_logger,{file,"/var/log/rabbitmq/rabbit@ip-10-..-..-53.log"}},

{frame_max,131072},

{heartbeat,580},

{hipe_compile,false},

{hipe_modules,[rabbit_reader,rabbit_channel,gen_server2,rabbit_exchange,

rabbit_command_assembler,rabbit_framing_amqp_0_9_1,

rabbit_basic,rabbit_event,lists,queue,priority_queue,

rabbit_router,rabbit_trace,rabbit_misc,rabbit_binary_parser,

rabbit_exchange_type_direct,rabbit_guid,rabbit_net,

rabbit_amqqueue_process,rabbit_variable_queue,

rabbit_binary_generator,rabbit_writer,delegate,gb_sets,lqueue,

sets,orddict,rabbit_amqqueue,rabbit_limiter,gb_trees,

rabbit_queue_index,rabbit_exchange_decorator,gen,dict,ordsets,

file_handle_cache,rabbit_msg_store,array,

rabbit_msg_store_ets_index,rabbit_msg_file,

rabbit_exchange_type_fanout,rabbit_exchange_type_topic,mnesia,

mnesia_lib,rpc,mnesia_tm,qlc,sofs,proplists,credit_flow,pmon,

ssl_connection,tls_connection,ssl_record,tls_record,gen_fsm,

ssl]},

{included_applications,[]},

{log_levels,[{connection,info}]},

{msg_store_file_size_limit,16777216},

{msg_store_index_module,rabbit_msg_store_ets_index},

{plugins_dir,"/usr/lib/rabbitmq/lib/rabbitmq_server-3.2.1/sbin/../plugins"},

{plugins_expand_dir,"/rabbitmq/rabbit@ip-10-..-..-53-plugins-expand"},

{queue_index_max_journal_entries,65536},

{reverse_dns_lookups,false},

{sasl_error_logger,{file,"/var/log/rabbitmq/rabbit@ip-10-..-..-53-sasl.log"}},

{server_properties,[]},

{ssl_apps,[asn1,crypto,public_key,ssl]},

{ssl_cert_login_from,distinguished_name},

{ssl_listeners,[5671]},

{ssl_options,[{cacertfile,"/home/ubuntu/certstuff/testca/cacert.pem"},

{certfile,"/home/ubuntu/certstuff/server/cert.pem"},

{keyfile,"/home/ubuntu/certstuff/server/key.pem"},

{verify,verify_peer},

{fail_if_no_peer_cert,false}]},

{tcp_listen_options,[binary,

{packet,raw},

{reuseaddr,true},

{backlog,128},

{nodelay,true},

{linger,{true,0}},

{exit_on_close,false}]},

{tcp_listeners,[]},

{trace_vhosts,[]},

{vm_memory_high_watermark,0.4},

{vm_memory_high_watermark_paging_ratio,0.5}]

Connections:

pid name port peer_port host peer_host ssl peer_cert_subject peer_cert_issuer peer_cert_validity auth_mechanism ssl_protocol ssl_key_excha

nge ssl_cipher ssl_hash protocol user vhost timeout frame_max client_properties recv_oct recv_cnt send_oct send_cnt send_

pend state last_blocked_by last_blocked_age channels

<'rabbit@ip-10-..-..-53'.3.14152.3614> 10.-.-.194:38766 -> 10.-.-.53:5671 5671 38766 10.-.-.53 10.-.-.194 true PLAIN tlsv1 rsa aes_128_cbc sha {0,9,1} rmqguy / 580 131072 [{"product","RabbitMQ"},{"information","Licensed under the MPL. See http://www.rabbitmq.com/"},{"platform","Java"},{"capabili