[rabbitmq-discuss] Cluster upgrade failed

[Tracy Dalzell]

That file does not currently exist.  Just create it?

-----Original Message-----
From: Simon MacMullen [mailto:simon at rabbitmq.com] 
Sent: Thursday, May 09, 2013 11:07 AM
To: Tracy Dalzell
Cc: Discussions about RabbitMQ; Daniel Buchko
Subject: Re: [rabbitmq-discuss] Cluster upgrade failed

On 09/05/13 15:52, Tracy Dalzell wrote:
<snip>
> The upgrade apparently created a new rabbitmq-env file and a new 
> symbolic link /usr/lib/rabbitmq/bin/rabbitmq-env -> 
> ../lib/rabbitmq_server-3.1.0/sbin/rabbitmq-env.  Our 3.0.4 
> configuration had the following entries in rabbitmq-env:
>
> RABBITMQ_MNESIA_BASE=/mnt/data/rabbitmq/mnesia
> export RABBITMQ_MNESIA_BASE
>
> Those two entries were not in the new rabbitmq-env file so when rabbit

> started after the upgrade the mnesia database was reinitialized in the

> default location.  I took down all the servers, edited the file on 
> each server, brought them back up and then I had a big phat rabbit, 
> just the way I like it.

Ah! Glad you sorted this out.

However, you might want to put this customisation into
/etc/rabbitmq/rabbitmq-env.conf instead (in a slightly different form):

MNESIA_BASE=/mnt/data/rabbitmq/mnesia

See:

http://www.rabbitmq.com/man/rabbitmq-env.conf.5.man.html
http://www.rabbitmq.com/relocate.html

The reason is that the rabbitmq-env file you edited is part of the
installation - so the next time you upgrade it will get overwritten
again and things will break again...

Cheers, Simon

--
Simon MacMullen
RabbitMQ, Pivotal