[rabbitmq-discuss] init terminating in do_boot

[Robert Raschke]

On Thu, Apr 29, 2010 at 1:57 PM, Andreas Jung <lists at zopyx.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> What does the following error during the startup mean?
>
> RabbitMQ 1.7.2 on Snow Leopard, 64 bit
>
> Andreas
> - ----------
>
> +---+   +---+
> |   |   |   |
> |   |   |   |
> |   |   |   |
> |   +---+   +-------+
> |                   |
> | RabbitMQ  +---+   |
> |           |   |   |
> |   v1.7.2  +---+   |
> |                   |
> +-------------------+
> AMQP 8-0
> Copyright (C) 2007-2010 LShift Ltd., Cohesive Financial Technologies
> LLC., and Rabbit Technologies Ltd.
> Licensed under the MPL.  See http://www.rabbitmq.com/
>
> node          : rabbit at suxmac2.fritz.box
> app descriptor: /Users/ajung/sandboxes/occ/parts/rabbitmq/ebin/rabbit.app
> home dir      : /Users/ajung
> cookie hash   : YdPtx/uDiT0CjSe1lC1Gig==
> log           : /Users/ajung/sandboxes/occ/var/log/rabbitmq/rabbit.log
> sasl log      : /Users/ajung/sandboxes/occ/var/log/rabbitmq/rabbit-sasl.log
> database dir  : /Users/ajung/sandboxes/occ/var/rabbit
>
> starting internal event notification system
> ...done
> starting logging server
> ...done
> starting database
> ...{"init terminating in
>
> do_boot",{{nocatch,{error,{cannot_start_application,rabbit,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{{case_clause,{error,{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,'-run_boot_step/1-lc$^1/1-1-',1},{rabbit,run_boot_step,1},{rabbit,'-start/2-lc$^0/1-0-',1},{rabbit,start,2},{application_master,start_it_old,4}]}}}}}}},[{init,start_it,1},{init,start_em,1}]}}
>
>
The 'timeout_waiting_for_tables' error usually means that you previously had
an mnesia DB set up under a particular named node and hostname, but now the
system is starting up with a different nodename or hostname and cannot
attach itself to your old DB.

If you're wanting to start from scratch, then just nuke the database files
and the next start will rebuild the schema.

If you need to retain the DB, then either try and re-establish your previous
name, or with more work using Erlang, rename your schema (see
http://www.erlang.org/doc/apps/mnesia/Mnesia_chap7.html#id2277864 for an
example of code to rename the node in the schema).

Hope this helps,
Robby
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100429/9e90e3c0/attachment.htm