[rabbitmq-discuss] Management plugin issues

[Mark J. Reed]

I'm having a couple problems with the management plugin on
2.2.0/Erlang 13B/Ubuntu 10.04.

First, I have several independent rabbitmq clusters, but they all seem
to wind up reporting back to the same stats database.  I assume this
is some Erlang network service advertising feature, but I'd much
rather have each cluster use its own separate stats db.  How can I
force that?

Second, it keeps dying.  That is, the nodes are running, but the
statistics database goes down, and I have to restart the node that
contains it to get the management API back.  I'm seeing messages like
this in the log:

=CRASH REPORT==== 18-Jan-2011::17:12:02 ===
  crasher:
    initial call: rabbit_mgmt_db:init/1
    pid: <0.289.0>
    registered_name: []
    exception exit: {{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-fun-2-',4},
                      {rabbit_mgmt_db,handle_call,3}]}
      in function  gen_server:terminate/6
    ancestors: [<0.288.0>,rabbit_sup,<0.122.0>]
    messages: []
    links: [<0.288.0>]
    dictionary: []
    trap_exit: false
    status: running
    heap_size: 377
    stack_size: 24
    reductions: 2235592
  neighbours:

Can anyone advise as to next steps in troubleshooting?



-- 
Mark J. Reed <markjreed at gmail.com>