[rabbitmq-discuss] 'rabbitmqctl status' doesn't work in RabbitMQ 3.0.0

[Matthias Radestock]

On 05/12/12 07:42, Hongli Lai wrote:
> I cannot find a bug tracker so I'm posting this here. It appears that
> the 'rabbitmqctl status' command is broken. I'm on Debian 6 and I
> installed the Debian package as provided on rabbitmq.com. Here's what
> happens:
>
>     # /etc/init.d/rabbitmq-server start
>     Starting message broker: rabbitmq-server.
>
>
> To confirm that RabbitMQ is properly started:
>
>     # ps auxw | grep rabbitmq
>     rabbitmq 11278 29.4  7.4  64104 37124 ?        Sl   02:38   0:01
>     /usr/lib/erlang/erts-5.8/bin/beam ....
>
>
> But:
>
>     # rabbitmqctl status
>     Status of node rabbit at web1 ...
>     Error: {{case_clause,{unknown_request}},
>              [{rabbit_vm,'-sup_memory/1-lc$^0/1-0-',1},
>               {rabbit_vm,sup_memory,1},
>               {rabbit_vm,'-sup_memory/1-lc$^0/1-0-',1},
>               {rabbit_vm,sup_memory,1},
>               {rabbit_vm,'-plugin_memory/0-lc$^0/1-0-',1},
>               {rabbit_vm,plugin_memory,0},
>               {rabbit_vm,memory,0},
>               {rabbit,status,0}]}
>     # /etc/init.d/rabbitmq-server status
>     Status of node rabbit at web1 ...
>     Error: {{case_clause,{unknown_request}},
>              [{rabbit_vm,'-sup_memory/1-lc$^0/1-0-',1},
>               {rabbit_vm,sup_memory,1},
>               {rabbit_vm,'-sup_memory/1-lc$^0/1-0-',1},
>               {rabbit_vm,sup_memory,1},
>               {rabbit_vm,'-plugin_memory/0-lc$^0/1-0-',1},
>               {rabbit_vm,plugin_memory,0},
>               {rabbit_vm,memory,0},
>               {rabbit,status,0}]}
>
>
> This is a big problem because '/etc/init.d/rabbitmq-server stop' also
> doesn't work anymore. The init script uses 'rabbitmqctl status' to check
> whether the server needs to be stopped.

I suspect this might be an unintended version incompatibility. Looks 
like you are running Erlang R14A. It may be worth trying R15B-3. Before 
you do that though, please

a) post the rabbit at web1.log and rabbit at web1-sasl.log, and

b) post the output of
rabbitmqctl eval 'application:which_applications().'


Regards,

Matthias.