I am tasked with installing a rabbit cluster on RHEL (release 5.7
Tikanga) w/SE-Linux (actually the DoDIIS build 2.1.5). I can
successfully install a single node rabbit instance using the rabbitmq-
server-2.7.1-1.noarch.rpm after installing erlang R15B from source.
However when I attempt to cluster my rabbit2 server with my rabbit1
server, I am unable so successfully execute the rabbitmqctl app_stop
command on rabbit2. Rather I get the below output. Thereafter
running rabbitmqctl status shows that the node is still up and
running. Any ideas?

sh-3.2# rabbitmqctl app_stop
Error: {'EXIT',
{function_clause,
[{rabbit_control,action,
[app_stop,rabbit at rabbit2,[],
[{"-p","/"},{"-n","rabbit at rabbit2"},{"-
q",false}],
#Fun<rabbit_control.1.115240681>],
[]},
{rabbit_control,start,0,[]},
{init,start_it,1,[]},
{init,start_em,1,[]}]}}

Search Discussions

  • Simon MacMullen at Jan 18, 2012 at 10:18 am

    On 17/01/12 17:27, Ken Baltrinic wrote:
    sh-3.2# rabbitmqctl app_stop
    Error: {'EXIT',
    {function_clause,
    [{rabbit_control,action,
    [app_stop,rabbit at rabbit2,[],
    It's stop_app, not app_stop.

    Unfortunately the "invalid command" error message in rabbitmqctl is
    broken with Erlang R15B, leading to the error you saw...

    Cheers, Simon

    --
    Simon MacMullen
    RabbitMQ, VMware
  • Emile Joubert at Jan 18, 2012 at 10:20 am
    Hi Ken,
    On 17/01/12 17:27, Ken Baltrinic wrote:
    sh-3.2# rabbitmqctl app_stop
    The command should be "stop_app".


    -Emile
  • Ken Baltrinic at Jan 18, 2012 at 3:22 pm
    Doh! Okay I feel stupid. With all the obscure issues you can run
    into on DoDISS, I guess I forgot to look for the obvious. :)

    I now have clustering working but... if I try to uncluster the servers
    it looks like I am getting bitten by that broken "invalid command"
    that simon spoke of. Can anyone figure out what is going on in the
    below command transcript? This is not too important. I only need to
    uncluster for testing purposes and these are VMs and I have a pre-
    cluster snapshot I can roll back to, but still, it seems like
    something is amiss and thats a little worrisome.

    Starting with a successfully clustered server pair rabbit1 and rabbit2
    (both disk nodes):

    [root at rabbit1 usr]# rabbitmqctl stop_app
    Stopping node rabbit at rabbit1 ...
    ...done.
    [root at rabbit1 usr]# rabbitmqctl reset
    Resetting node rabbit at rabbit1 ...
    ...done.
    [root at rabbit1 usr]# rabbitmqctl start_app
    Starting node rabbit at rabbit1 ...
    Error: {cannot_start_application,rabbitmq_management,
    {bad_return,
    {{rabbit_mgmt_app,start,[normal,[]]},
    {'EXIT',
    {shutdown,
    {gen_server2,call,
    [<5135.22427.3>,
    {init,<5135.22425.3>},
    infinity]}}}}}}

    If it matters, the only plugins that are enabled are
    rabbitmq_management and its dependencies.

    On Jan 18, 5:20?am, Emile Joubert wrote:
    Hi Ken,
    On 17/01/12 17:27, Ken Baltrinic wrote:

    sh-3.2# rabbitmqctl app_stop
    The command should be "stop_app".

    -Emile
    _______________________________________________
    rabbitmq-discuss mailing list
    rabbitmq-disc... at lists.rabbitmq.comhttps://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouprabbitmq-discuss @
categoriesrabbitmq
postedJan 17, '12 at 5:27p
activeJan 18, '12 at 3:22p
posts4
users3
websiterabbitmq.com
irc#rabbitmq

People

Translate

site design / logo © 2021 Grokbase