Queue status was "down" and then RabbitMQ became non-interactive

2,759 views

Skip to first unread message

Alexey Mamontov

unread,

Jul 11, 2017, 1:57:45 PM7/11/17

to rabbitmq-users

I had the chance to see this State in the Management console, tried to switch to Overview and ever since I get this error:

Got response code 500 with body {"error":"Internal Server Error","reason":"{error,{error,badarg,\n [{ets,match,[rabbit_registry,{{exchange,'$1'},'$2'}],[]},\n {rabbit_registry,lookup_all,1,[]},\n {rabbit_mgmt_external_stats,list_registry_plugins,2,[]},\n {rabbit_mgmt_wm_overview,to_json,2,[]},\n {webmachine_resource,resource_call,3,[]},\n {webmachine_resource,do,3,[]},\n {webmachine_decision_core,resource_call,1,[]},\n {webmachine_decision_core,decision,1,[]}]}}\n"}

rabbitmqctl status returns:

{running_applications,
[{rabbitmq_shovel_management,"Shovel Status","3.5.3"},
{rabbitmq_management,"RabbitMQ Management Console","3.5.3"},
{rabbitmq_web_dispatch,"RabbitMQ Web Dispatcher","3.5.3"},
{webmachine,"webmachine","1.10.3-rmq3.5.3-gite9359c7"},
{mochiweb,"MochiMedia Web Server","2.7.0-rmq3.5.3-git680dba8"},
{rabbitmq_packing_message_exchange,"RabbitMQ Packing Exchange","3.6.5"},
{os_mon,"CPO CXC 138 46","2.2.14"},
{sasl,"SASL CXC 138 11","2.3.4"},
{inets,"INETS CXC 138 49","5.9.7"},
{mnesia,"MNESIA CXC 138 12","4.11"},
{amqp_client,"RabbitMQ AMQP Client","3.5.3"},
{xmerl,"XML parser","1.3.5"},
{stdlib,"ERTS CXC 138 10","1.19.4"},
{kernel,"ERTS CXC 138 10","2.16.4"}]},
{os,{win32,nt}},
{erlang_version,
"Erlang R16B03 (erts-5.10.4) [64-bit] [smp:12:12] [async-threads:30]\n"},
{memory,
[{total,605042976},
{connection_readers,0},
{connection_writers,0},
{connection_channels,0},
{connection_other,8728},
{queue_procs,0},
{queue_slave_procs,0},
{plugins,1016840},
{other_proc,517712872},
{mnesia,215360},
{mgmt_db,1164968},
{msg_index,0},
{other_ets,1318016},
{binary,57565904},
{code,20188363},
{atom,703377},
{other_system,5148548}]},
{alarms,[]},
{listeners,[]},
{processes,[{limit,1048576},{used,116}]},
{run_queue,0},
{uptime,38178}]

There are many error details in RMQ log file we can't read.

My the question is, if we have encountered with some Bug in RabbitMQ Server or there anything possible to send to Rabbit from the client (we use c-client) to cause such condition? There is enough memory on that machine.
Thanks!

Michael Klishin

unread,

Jul 11, 2017, 2:23:27 PM7/11/17

to rabbitm...@googlegroups.com

It is very unlikely that a client can cause this.

Your version does not report open file handle limit (and count) in `rabbitmqctl status` but according

to the error, one of the tables "does not exist". One fairly common scenario for this

is when a node runs out of file descriptors. In such case it wouldn't be able to accept

any client connections either, including over HTTP API.

See http://www.rabbitmq.com/networking.html to learn more.

3.5.x is out of support, so consider upgrading ASAP:

http://www.rabbitmq.com/changelog.html.

--
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.