[rabbitmq-discuss] Upgrading windows bundle?

Matthew Sackman matthew at rabbitmq.com
Thu Apr 28 13:06:19 BST 2011


On Thu, Apr 21, 2011 at 05:50:48PM -0500, Derek Chen-Becker wrote:
>     We're looking at deploying a RabbitMQ broker on Windows at
> potentially several thousand sites and our QA group has come up with a
> few questions. First, the windows bundle is essentially a zip file that
> we unpack to a specific directory for the install. When we want to
> upgrade can we just stop the service, unpack the new files to the same
> location and then start the service, or do we need to additionally
> deregister the service, remove all of the old files, and then unpack and
> re-register the service?

The latter is likely the safest route. The minimum you'll need to do is
unpack, reinstall the service, and then start the service.

>     They were also wondering if the permissions are stored in a file
> somewhere that we could push out if we decide we want to add users,
> perms, etc, or if we'll need to run a script against rabbitmqctl on each
> box (slightly more work but not a big deal). I know RabbitMQ stores that
> data somewhere, we're just not sure if it's the same name on each box
> and if it's safe to copy that file to a different host (each host is
> going to have a unique node name based on the computer name).

The permissions and most other meta-data are stored in an mnesia
database that Rabbit uses. The only way of modifying permissions is
through the rabbitmqctl command, so yes, I'm afraid you will need to
script that.

It's not safe to copy the mnesia files from computer to computer
because, for one, mnesia stores the host name in those files, and will
refuse to start if it finds the stored host name does not match the
machine's host name. The important implication of this is that if you
change the host name of a machine, you'll need to wipe out any data
Rabbit has stored on that machine and restart Rabbit.


More information about the rabbitmq-discuss mailing list