[rabbitmq-discuss] Generic server rabbit_mgmt_db terminating
Simon MacMullen
simon at rabbitmq.com
Thu Sep 1 09:28:20 BST 2011
On 31/08/2011 1:19PM, Conor Glynn wrote:
> =ERROR REPORT==== 30-Aug-2011::20:46:01 ===
> ** Generic server rabbit_mgmt_db terminating
> ** Last message in was {get_overview,all}
> ** When Server state == {state,[{channel_exchange_stats,2599211068},
> {channel_queue_exchange_stats,2599215165},
> {channel_queue_stats,2599206971},
> {channel_stats,2599202874},
> {connection_stats,2599198777},
> {queue_stats,2599194675}]}
> ** Reason for termination ==
> ** {{badmatch,[]},
> [{rabbit_mgmt_db,augment_queue_pid,2},
> {rabbit_mgmt_db,augment,4},
> {rabbit_mgmt_db,'-augment/3-lc$^0/1-0-',3},
> {rabbit_mgmt_db,'-augment/3-lc$^0/1-0-',3},
> {rabbit_mgmt_db,augment,3},
> {rabbit_mgmt_db,'-handle_call/3-lc$^4/1-4-',4},
> {rabbit_mgmt_db,'-handle_call/3-lc$^4/1-4-',4},
> {rabbit_mgmt_db,'-handle_call/3-fun-2-',4}]}
Quick drive-by holiday posting: Yes, Matthew is right. This is a bug
caused by the mgmt plugin looking up details for a queue which has since
disappeared, so you're likely to see it when queues are churning. It was
fixed in 2.3.0, but really you should upgrade to 2.6.0 :)
Cheers, Simon
More information about the rabbitmq-discuss
mailing list