[rabbitmq-discuss] Trouble starting rabbitmq (new user)

Matt Calder mvcalder at gmail.com
Fri May 7 13:11:02 BST 2010

 Thanks for the replies. I went through a lot of old emails from the
archives (again). I found my problems were almost, but not quite, the
same. Presumably there is some underlying cause. What I eventually did
that seems to work is this. First, I purged rabbitmq-server and

sudo apt-get purge rabbitmq-server
sudo apt-get purge erlang
sudo apt-get autoremove

Then, I installed erlang independently of (and before) rabbitmq-server:

sudo apt-get install erlang-base
sudo apt-get install erlang-dev   # Not sure this is necessary
sudo apt-get install rabbitmq-server

This has been working, that is, I have had no issues with rabbitmqctl,
nor have I had problems starting and stopping the server from
/etc/init.d, and this good behaviour continued after rebooting. Given
that, I am declaring victory.

I thought it might be helpful to post these breadcrumbs for any other
Ubuntu or AWS cloud users out there. I mention that this is an EC2
installation because I have installed the rabbitmq-server package
(without the pre-install of erlang) on my home network (also Ubuntu
machines) without any issues.

Thanks again for the helpful replies,


On Fri, May 7, 2010 at 1:54 AM, Alvaro Videla <videlalvaro at gmail.com> wrote:
> To monitor RabbitMQ using the rabbitctl you have to the same user that rabbitmq is running. This is because they have to share the same erlang cookie.
> On May 7, 2010, at 5:53 AM, Matt Calder wrote:
>> Hi,
>> I've had persistent problems running rabbit mq under Ubuntu.
>>> uname -a
>> Linux domU-12-31-39-01-B1-21 2.6.31-302-ec2 #7-Ubuntu SMP Tue Oct 13
>> 19:06:04 UTC 2009 i686 GNU/Linux
>> After an initial install things seem fine. However after use, not
>> particularly heavy, it falls into a bad state and nothing seems to
>> help.
>> ubuntu at domU-12-31-39-01-B1-21:~/celerytest$ sudo rabbitmqctl status
>> Status of node 'rabbit at domU-12-31-39-01-B1-21' ...
>> {badrpc,nodedown}
>> ...done.
>> If I restart,
>> I get a timeout,
>> ubuntu at domU-12-31-39-01-B1-21:~/celerytest$ cat /var/log/rabbitmq/startup_log
>> Starting all nodes...
>> Starting node rabbit at domU-12-31-39-01-B1-21...
>> RabbitMQ 1.6.0 (AMQP 8-0)
>> Copyright (C) 2007-2009 LShift Ltd., Cohesive Financial Technologies
>> LLC., and Rabbit Technologies Ltd.
>> Licensed under the MPL.  See http://www.rabbitmq.com/
>> node        : rabbit at domU-12-31-39-01-B1-21
>> log         : /var/log/rabbitmq/rabbit.log
>> sasl log    : /var/log/rabbitmq/rabbit-sasl.log
>> database dir: /var/lib/rabbitmq/mnesia/rabbit
>> starting database             ...timeout
>> {"init terminating in
>> do_boot",{{nocatch,{error,{cannot_start_application,rabbit,{{timeout_waiting_for_tables,[rabbit_user,rabbit_user_permission,rabbit_vhost,rabbit_config,rabbit_listener,rabbit_durable_route,rabbit_route,rabbit_reverse_route,rabbit_durable_exchange,rabbit_exchange,rabbit_durable_queue,rabbit_queue]},{rabbit,start,[normal,[]]}}}}},[{init,start_it,1},{init,start_em,1}]}}
>> Since I am a new user I suspect I am doing something obviously wrong.
>> If anyone knows what that is I would greatly appreciate a pointer.
>> Uninstalling and reinstalling doesn't seem like a workable plan going
>> forward.
>> Matt
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list