[rabbitmq-discuss] Cloning RHEL VM's with pre-installed Rabbit.

Keith Davies keith.davies at trafigura.com
Fri May 21 09:09:29 BST 2010

Thanks very much Emile,  I'm not sure how it got in that state.  I think the best thing to do would be for us to try creating the template again.

-----Original Message-----
From: Emile Joubert [mailto:emile at rabbitmq.com]
Sent: 20 May 2010 17:29
To: Keith Davies
Cc: rabbitmq-discuss at lists.rabbitmq.com
Subject: Re: [rabbitmq-discuss] Cloning RHEL VM's with pre-installed Rabbit.

Hi Keith,

Keith Davies wrote:
> Hi Emile
> Thanks very much for the reply.  Just to let you know we are using
> rabbit 1.7.1.  Anyway in response to your questions if I run the
> following command on one of our VM's:-
> ./rabbitmqctl status
> I get the response:-
> Status of node rabbit at ttraflonrh320 ...
> [{running_applications,[{rabbitmq_bql,"RabbitMQ Broker Query
> Language","0.01"},
>                         {amqp_client,"RabbitMQ AMQP Client","0.0.0"},
>                         {rabbit,"RabbitMQ","1.7.1"},
>                         {os_mon,"CPO  CXC 138 46","2.1.8"},
>                         {sasl,"SASL  CXC 138 11",""},
>                         {rfc4627_jsonrpc,"JSON RPC Service","0.01"},
>                         {mnesia,"MNESIA  CXC 138 12","4.4.7"},
>                         {stdlib,"ERTS  CXC 138 10","1.15.5"},
>                         {kernel,"ERTS  CXC 138 10","2.12.5"}]},
>   {nodes,[rabbit at ttraflonrh320]},
>   {running_nodes,[rabbit at ttraflonrhtest,rabbit at ttraflonrh324,
>                  rabbit at ttraflonrh334,rabbit at ttraflonrh326,
>                  rabbit at ttraflonrh331,rabbit at ttraflonrh320]}]
> Which strikes me a slightly weird as the running nodes do not match up
> with the nodes.  Unfortunately I have not been able to determine from
> the documentation what this means.

This should never happen. The running nodes should always be a subset of
the nodes. We have never seen the state you reported. Is it possible
that the original machine was in a clustered configuration prior to
being cloned? When did the running_nodes come into existence?

A suggested recovery option is to run
"rabbitmqctl stop_app; rabbitmqctl reset; rabbitmqctl start_app"
for each of the running nodes.
This should leave you with a set of standalone rabbit brokers and both
"nodes" and "running_nodes" should contain a single entry.

The original template machine that the clones are created from should
have a blank mnesia database or preferably have no mnesia directory at all.


This email and any attachments are confidential and access to this email or attachment by anyone other than the addressee is unauthorised. If you are not the intended recipient please notify the sender and delete the email including any attachments. You must not disclose or distribute any of the contents to any other person. Personal views or opinions are solely those of the author and not of Trafigura. Trafigura does not guarantee that the integrity of this communication has been maintained nor that the communication is free of viruses, interceptions or interference. By communicating with anyone at Trafigura by email, you consent to the monitoring or interception of such email by Trafigura in accordance with its internal policies. Unless otherwise stated, any pricing information given in this message is indicative only, is subject to change and does not constitute an offer to deal at any price quoted.

More information about the rabbitmq-discuss mailing list