[rabbitmq-discuss] Rabbitmq boot failure with "tables_not_present"
jerryk at rbcon.com
Thu Jan 17 00:45:43 GMT 2013
> I think during the time the error logs are generated, the cluster may not
> be successfully formed. As part of the deployment scripts, I deleted all
> content in /var/lib/rabbitmq/mnesia to recover from some scenario when
> cluster cannot be formed. Here is the relevant part of the deployment
> sudo("bash -c 'echo XXXXXXXXXXXXXXXX > /var/lib/rabbitmq/.erlang.cookie'")
> sudo("chown rabbitmq /var/lib/rabbitmq/.erlang.cookie")****
> sudo("chmod 600 /var/lib/rabbitmq/.erlang.cookie")****
> sudo("rm -fr /var/lib/rabbitmq/mnesia")
That is indeed a fine way to get rid of your Mnesia contents including
clustering info and any metadata that needs to be shared amongst the nodes
(queue, exchange, binding, user, vhost, etc. definitions).
On the other hand, after you've done it, you've got no really good reason
to expect your nodes to act as clustered.
> What I want to achieve after redeployment is to erase previous states
> completely and let the cluster starts with a clean state, that’s why I
> erased the /mnesia folder (is there a better way to do that?). The problem
> is sometimes the error messages show up for a few minutes then everything
> works fine after that, but other times I saw the error message being logged
> for 80 minutes before the cluster works correctly. Do you have any
Are you establishing your clusters using the rabbitmq command line tools or
by statically encoding their properties in your rabbitmq.config files?
You're going to have to repeat whichever you did when you bring a newly
redeployed cluster, having gone through the cleansing you outline above,
You might consider setting up scripts to execute the appropriate commands,
as per our clustering guide, on the appropriate nodes after you've done the
scripted clean-up you describe.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss